คู่มือเริ่มต้นใช้งาน Guide Cisco Aironet 1700 Series Access Points
This entry was posted on 30 July 2016
.สินค้าที่เกี่ยวข้อง
บทความที่เกี่ยวข้อง
About this Guide
This Guide provides instructions on how to install and configure your Cisco Aironet 1700 Series Access Point. This guide also provides mounting instructions and limited troubleshooting procedures.
The 1700 Series Access Point is referred to as the access point in this document.
Introduction to the Access Point
The 1700 series supports high-performing Spectrum Intelligence which sustains two spatial stream rates over a deployable distance with high reliability when serving clients. The 1700 series provides high reliability and overall wireless performance.
The 1700 series offers dual-band radios (2.4 GHz and 5 GHz) with integrated antennas. The access points support full interoperability with leading 802.11ac clients, and support a mixed deployment with other access points and controllers.
The 1700 series access point is available in both controller-based (Unified) and standalone (Autonomous) configurations, and supports:
Note The ‘x’ in the model numbers represents the regulatory domain. Refer to “Regulatory Domains” section for a list of supported regulatory domains.
The features of the 1700 series are:
– CleanAir—Automatic detection, classification, location and mitigation of RF interference, with limited number of IDRs (Interference Device Reports) generated.
– Radio Resource Management (RRM)
– Management Frame Protection (MFP)
– Throughput, forwarding, and filtering performance scaled to meet 2 spatial streams, 1.3-Gbps data-rates
- 64 MB flash size
- 802.3af/802.3at compatible via CDP (Cisco Discovery Protocol) or LLDP (Link Layer Discovery Protocol)
- 2.4 GHz and 5 GHz 802.11n radios with the following features:
– 3TX x 3RX for 2.4 GHz and 5 GHz
– DPD (Digital Pre-Distortion) technology
– Cisco Vector Beamforming—Implicit Co-phase beamforming for.11ag clients and 1x1 11n clients
– Radio hardware is capable of explicit compressed beamforming (ECBF) per 802.11n standard
Safety Instructions
Translated versions of the following safety warnings are provided in the translated safety warnings document that is shipped with your access point. The translated warnings are also in the Translated Safety Warnings for Cisco Aironet Access Points, which is available on Cisco.com.
Warning IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071
SAVE THESE INSTRUCTIONS
Warning Read the installation instructions before you connect the system to its power source. Statement 1004
Warning Installation of the equipment must comply with local and national electrical codes. Statement 1074
Warning This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that the protective device is rated not greater than:
20A. Statement 1005
Warning Do not operate your wireless network device near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use. Statement 245B
Note The access point is suitable for use in environmental air space in accordance with section 300.22.C of the National Electrical Code and sections 2-128, 12-010(3), and 12-100 of the Canadian Electrical Code, Part 1, C22.1. You should not install the power supply or power injector in air handling spaces.
Note Use only with listed Information Technology Equipment (ITE) equipment. For more information on ITE equipment, refer to article 645 of the latest National Electrical Code (NEC).
Unpacking
To unpack the access point, follow these steps:
Step 1 Unpack and remove the access point and the accessory kit from the shipping box.
Step 2 Return any packing material to the shipping container and save it for future use.
Step 3 Verify that you have received the items listed below. If any item is missing or damaged, contact your Cisco representative or reseller for instructions.
– Mounting bracket (only if selected when you ordered the access point)
– Adjustable ceiling-rail clip (only if selected when you ordered the access point)
Configurations
The 1700 series access point contains two radios, a 2.4 GHz 802.11n MIMO radio and a 5 GHz 802.11ac MIMO radio, with integrated dual-band antennas.
For information on the regulatory domains (shown as “x” in the model numbers) see “Regulatory Domains” section.
Antennas
The 1702I model access point is configured with dual-band inverted-F antennas, and two 2.4-GHz/5-GHz dual-band radios.
There are antennas deployed inside the access point with one deployed on each corner of the 1702I access point top housing. Each antenna covers both the 2.4 GHz and the 5 GHz bands with a single feed line. The basic features are as follows:
Regulatory Domains
The 1700 series supports the following regulatory domains (shown as “x” in the model numbers):
Access Point Ports and Connectors
The 1702I model access point has integrated antennas and has an LED indicator on top of the unit, as shown in Figure 1.
Figure 1 Access Point LED Indicator (top)—1702I Model
The ports and connections on the bottom of the access point are shown in Figure 2.
Figure 2 Access Point Ports and Connections (bottom)-AIR1702I Model
Note The Auxiliary Ethernet port is disabled. Do not connect this port to a PoE switch. Connecting the primary and auxiliary ports to a PoE switch will not provide additional power.
Configuring the Access Point
This section describes how to connect the access point to a wireless LAN controller. Because the configuration process takes place on the controller, see the Cisco Wireless LAN Controller Configuration Guide for additional information. This guide is available on Cisco.com.
The Controller Discovery Process
The access point uses standard Control and Provisioning of Wireless Access Points Protocol (CAPWAP) to communicate between the controller and other wireless access points on the network. CAPWAP is a standard, inter-operable protocol which enables an access controller to manage a collection of wireless termination points. The discovery process using CAPWAP is identical to the Lightweight Access Point Protocol (LWAPP) used with previous Cisco Aironet access points. LWAPP-enabled access points are compatible with CAPWAP, and conversion to a CAPWAP controller is seamless. Deployments can combine CAPWAP and LWAPP software on the controllers.
The functionality provided by the controller does not change except for customers who have Layer 2 deployments, which CAPWAP does not support.
In a CAPWAP environment, a wireless access point discovers a controller by using CAPWAP discovery mechanisms and then sends it a CAPWAP join request. The controller sends the access point a CAPWAP join response allowing the access point to join the controller. When the access point joins the controller, the controller manages its configuration, firmware, control transactions, and data transactions.
Note For additional information about the discovery process and CAPWAP, see the Cisco Wireless LAN Controller Software Configuration Guide. This document is available on Cisco.com.
Note CAPWAP support is provided in controller software release 5.2 or later. However, your controller must be running release 8.0.x.x or later to support 1700 series access points.
Note You cannot edit or query any access point using the controller CLI if the name of the access point contains a space.
Note Make sure that the controller is set to the current time. If the controller is set to a time that has already occurred, the access point might not join the controller because its certificate may not be valid for that time.
Access points must be discovered by a controller before they can become an active part of the network. The access point supports these controller discovery processes:
- Layer 3 CAPWAP discovery—Can occur on different subnets than the access point and uses IP addresses and UDP packets rather than MAC addresses used by Layer 2 discovery.
- Locally stored controller IP address discovery—If the access point was previously joined to a controller, the IP addresses of the primary, secondary, and tertiary controllers are stored in the access point’s non-volatile memory. This process of storing controller IP addresses on an access point for later deployment is called priming the access point. For more information about priming, see the “Performing a Pre-Installation Configuration” section.
- DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses to the access points. Cisco switches support a DHCP server option that is typically used for this capability. For more information about DHCP option 43, see the “Configuring DHCP Option 43 and DHCP Option 60” section.
- DNS discovery—The access point can discover controllers through your domain name server (DNS). For the access point to do so, you must configure your DNS to return controller IP addresses in response to CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain is the access point domain name. Configuring the CISCO-CAPWAP-CONTROLLER provides backwards compatibility in an existing customer deployment. When an access point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the access point sends discovery requests to the controllers.
Preparing the Access Point
Before you mount and deploy your access point, we recommend that you perform a site survey (or use the site planning tool) to determine the best location to install your access point.
You should have the following information about your wireless network available:
- Access point locations.
- Access point mounting options: below a suspended ceiling, on a flat horizontal surface, or on a desktop.
Note You can mount the access point above a suspended ceiling but you must purchase additional mounting hardware: See “Mounting the Access Point” section for additional information.
- Access point power options: power supplied by the recommended external power supply (Cisco AIR-PWR-B), a DC power supply, PoE from a network device, or a PoE power injector/hub (usually located in a wiring closet).
Note Access points mounted in a building’s environmental airspace must be powered using PoE to comply with safety regulations.
Cisco recommends that you make a site map showing access point locations so that you can record the device MAC addresses from each location and return them to the person who is planning or managing your wireless network.
Performing a Pre-Installation Configuration
The following procedures ensure that your access point installation and initial operation go as expected. A pre-installation configuration is also known as priming the access point. This procedure is optional.
Note Performing a pre-installation configuration is an optional procedure. If your network controller is properly configured, you can install your access point in its final location and connect it to the network from there. See the “Deploying the Access Point on the Wireless Network” section for details.
Pre-Installation Configuration Setup
The pre-installation configuration setup is shown in Figure 3.
Figure 3 Pre-Installation Configuration Setup
To perform pre-installation configuration, perform the following steps:
Step 1 Make sure that the Cisco wireless LAN controller DS port is connected to the network. Use the CLI, web-browser interface, or Cisco Prime Infrastructure procedures as described in the appropriate Cisco wireless LAN controller guide.
a. Make sure that access points have Layer 3 connectivity to the Cisco wireless LAN controller Management and AP-Manager Interface.
b. Configure the switch to which your access point is to attach. See the Cisco Wireless LAN Controller Configuration Guide, Release x.x for additional information.
c. Set the Cisco wireless LAN controller as the master so that new access points always join with it.
d. Make sure DHCP is enabled on the network. The access point must receive its IP address through DHCP.
e. CAPWAP UDP ports must not be blocked in the network.
f. The access point must be able to find the IP address of the controller. This can be accomplished using DHCP, DNS, or IP subnet broadcast. This guide describes the DHCP method to convey the controller IP address. For other methods, refer to the product documentation. See also the “Using DHCP Option 43” section for more information.
Step 2 Apply power to the access point:
a. The access point is 802.3af (15.4 W) compliant and can be powered by any 802.3af-compliant device.
The recommended external power supply for the access point is the Cisco AIR-PWR-B power supply. The access point can also be powered by the following optional external power sources:
– Access point power injector (AIR-PWRINJ5)
– Any 802.3af compliant power injector
Note The 1702 series access point requires a gigabit Ethernet (GbE) link to prevent the Ethernet port from becoming a bottleneck for traffic because wireless traffic speeds exceed transmit speeds of a 10/100 Ethernet port.
b. As the access point attempts to connect to the controller, the LEDs cycle through a green, red, and amber sequence, which can take up to 5 minutes.
Note If the access point remains in this mode for more than five minutes, the access point is unable to find the Master Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN controller and be sure that they are on the same subnet.
c. If the access point shuts down, check the power source.
d. After the access point finds the Cisco wireless LAN controller, it attempts to download the new operating system code if the access point code version differs from the Cisco wireless LAN controller code version. While this is happening, the Status LED blinks amber.
e. If the operating system download is successful, the access point reboots.
Step 3 Configure the access point if required. Use the controller CLI, controller GUI, or Cisco Prime Infrastructure to customize the access-point-specific 802.11ac network settings.
Step 4 If the pre-installation configuration is successful, the Status LED is green indicating normal operation. Disconnect the access point and mount it at the location at which you intend to deploy it on the wireless network.
Step 5 If your access point does not indicate normal operation, turn it off and repeat the pre-installation configuration.
Note When you are installing a Layer 3 access point on a different subnet than the Cisco wireless LAN controller, be sure that a DHCP server is reachable from the subnet on which you will be installing the access point, and that the subnet has a route back to the Cisco wireless LAN controller. Also be sure that the route back to the Cisco wireless LAN controller has destination UDP ports 5246 and 5247 open for CAPWAP communications. Ensure that the route back to the primary, secondary, and tertiary wireless LAN controller allows IP packet fragments. Finally, be sure that if address translation is used, that the access point and the Cisco wireless LAN controller have a static 1-to-1 NAT to an outside address. (Port Address Translation is not supported.)
Mounting the Access Point
Cisco Aironet 1702 series access points can be mounted in several configurations, including on a suspended ceiling, on a hard ceiling or wall, on an electrical or network box, and above a suspended ceiling. Click this URL to browse to complete access point mounting instructions:
http://www.cisco.com/en/US/docs/wireless/access_point/mounting/guide/apmount.html
Deploying the Access Point on the Wireless Network
After you have mounted the access point, follow these steps to deploy it on the wireless network:
Step 1 Connect and power up the access point.
Step 2 Observe the access point LED (for LED descriptions, see “Checking the Access Point LED” section).
a. When you power up the access point, it begins a power-up sequence that you can verify by observing the access point LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks sequentially green, red, and off. When the access point has joined a controller, the LED is chirping green if no clients are associated or green if one or more clients are associated.
b. If the LED is not on, the access point is most likely not receiving power.
c. (Only for APs in Unified configuration) If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary, secondary, and tertiary Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN controller, and be sure the access point and the Cisco wireless LAN controller are either on the same subnet or that the access point has a route back to its primary, secondary, and tertiary Cisco wireless LAN controller. Also, if the access point is not on the same subnet as the Cisco wireless LAN controller, be sure that there is a properly configured DHCP server on the same subnet as the access point. See the “Configuring DHCP Option 43 and DHCP Option 60” section for additional information.
Step 3 Reconfigure the Cisco wireless LAN controller so that it is not the Master.
Note A Master Cisco wireless LAN controller should be used only for configuring access points and not in a working network.
Troubleshooting
If you experience difficulty getting your access point installed and running, look for a solution to your problem in this guide or in additional access point documentation. These, and other documents, are available on Cisco.com.
Guidelines for Using Cisco Aironet Lightweight Access Points
Keep these guidelines in mind when you use 1702 series lightweight access points:
- The access point can only communicate with Cisco wireless LAN controllers.
- The access point does not support Wireless Domain Services (WDS) and cannot communicate with WDS devices. However, the controller provides functionality equivalent to WDS when the access point joins it.
- CAPWAP does not support Layer 2. The access point must get an IP address and discover the controller using Layer 3, DHCP, DNS, or IP subnet broadcast.
- The access point console port is enabled for monitoring and debug purposes. All configuration commands are disabled when the access point is connected to a controller.
Using DHCP Option 43
You can use DHCP Option 43 to provide a list of controller IP addresses to the access points, enabling them to find and join a controller. For additional information, refer to the “Configuring DHCP Option 43 and DHCP Option 60” section.
Checking the Access Point LED
The location of the access point status LED is shown in Figure 1.
Note Regarding LED status colors, it is expected that there will be small variations in color intensity and hue from unit to unit. This is within the normal range of the LED manufacturer’s specifications and is not a defect.
The access point status LED indicates various conditions and are described in Table 1.
Troubleshooting the Access Point Join Process
Note The controller must be running Cisco IOS Software Release 8.0.x.x or later to support 1700 series access points.
A detailed explanation of the join process is on Cisco.com at the following URL:
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html
Access points can fail to join a controller for many reasons: a RADIUS authorization is pending; self-signed certificates are not enabled on the controller; the access point’s and controller’s regulatory domains don’t match, and so on.
Controller software enables you to configure the access points to send all CAPWAP-related errors to a syslog server. You do not need to enable any debug commands on the controller because all of the CAPWAP error messages can be viewed from the syslog server itself.
The state of the access point is not maintained on the controller until it receives a CAPWAP join request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery request from a certain access point was rejected. In order to troubleshoot such joining problems without enabling CAPWAP debug commands on the controller, the controller collects information for all access points that send a discovery message to it and maintains information for any access points that have successfully joined it.
The controller collects all join-related information for each access point that sends a CAPWAP discovery request to the controller. Collection begins with the first discovery message received from the access point and ends with the last configuration payload sent from the controller to the access point.
You can view join-related information for up to three times the maximum number of access points supported by the platform for the 2500 series controllers and the Controller Network Module within the Cisco 28/37/38xx Series Integrated Services Routers.
Note The maximum number of access points varies for the Cisco WiSM2, depending on which controller software release is being used.
When the controller is maintaining join-related information for the maximum number of access points, it does not collect information for any more access points.
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the following conditions are met:
- An access point running software release 8.0.x.x or later has been newly deployed.
- An existing access point running software release 8.0.x.x or later has been reset after clearing the configuration.
If any of these conditions are met and the access point has not yet joined a controller, you can also configure a DHCP server to return a syslog server IP address to the access point using option 7 on the server. The access point then starts sending all syslog messages to this IP address.
When the access point joins a controller for the first time, the controller sends the global syslog server IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all syslog messages to this IP address until it is overridden by one of the following scenarios:
- The access point is still connected to the same controller, and the global syslog server IP address configuration on the controller has been changed using the config ap syslog host global syslog_server_IP_address command. In this case, the controller sends the new global syslog server IP address to the access point.
- The access point is still connected to the same controller, and a specific syslog server IP address has been configured for the access point on the controller using the config ap syslog host specific Cisco_AP syslog_server_IP_address command. In this case, the controller sends the new specific syslog server IP address to the access point.
- The access point is disconnected from the controller and joins another controller. In this case, the new controller sends its global syslog server IP address to the access point.
- Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address is erased from persistent storage, and the new address is stored in its place. The access point also starts sending all syslog messages to the new IP address provided the access point can reach the syslog server IP address.
You can configure the syslog server for access points and view the access point join information only from the controller CLI.
Declarations of Conformity and Regulatory Information
This section provides declarations of conformity and regulatory information for the Cisco Aironet 1700 Series Access Points. You can find additional information at this URL:
www.cisco.com/go/aironet/compliance
Manufacturers Federal Communication Commission Declaration of Conformity Statement
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
This device complies with Part 15 rules. Operation is subject to the following two conditions:
1. This device may not cause harmful interference, and
2. This device must accept any interference received, including interference that may cause undesired operation.
This device operates in the 5150-5250MHz and 5470-5725MHz bands and is therefore restricted to indoor operation only per FCC guidance.
This equipment has been tested and found to comply with the limits of a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a residential environment. This equipment generates, uses, and radiates radio frequency energy, and if not installed and used in accordance with the instructions, may cause harmful interference. However, there is no guarantee that interference will not occur. If this equipment does cause interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to correct the interference by one of the following measures: