คู่มือเริ่มต้นใช้งาน Cisco Aironet 2800 Series Access Points
This entry was posted on 29/07/2016.
About this Guide
This guide provides instructions on how to install your Cisco Aironet 2800I and 2800E series access points and provides links to resources which can help you configure the access point. This guide provides mounting instructions and limited troubleshooting procedures.
The Cisco Aironet 2800 Series Wi-Fi access points provide 802.11ac Wave 2 with Multi User MIMO (MU MIMO). This AP series offers integrated and external antenna options, with a dedicated 5 GHz radio and a flexible radio that can be configured as a 2.4 GHz radio (default) or as an additional 5 GHz radio. This access point supports a greater overall High Density Experience (HDX) which provides mission-critical wireless to meet your performance needs. The access points support full interoperability with leading 802.11ac clients, and support a mixed deployment with other access points and controllers.
- Integrated antennas on the 2802I access point model (AIR-AP2802I-x-K9)
- External antennas on the 2802E access point models (AIR-AP2802E-x-K9)
Note The ‘x’ in the model numbers represents the regulatory domain. For information on supported regulatory domains, see the“AP Model Numbers and Regulatory Domains” section.
- Flexible Radio Assignment, allowing for either manual configuration or for the APs to intelligently determine the operating role of the integrated radios based on the available RF environment. The AP can operate in the following modes:
- Multiuser Multiple-Input Multiple-Output (MU-MIMO) technology with 3 spatial streams.
- Cross-AP Noise Reduction, a Cisco innovation that enables APs to intelligently collaborate in real time about RF conditions so that users connect with optimized signal quality and performance.
- Optimized AP Roaming for ensuring that client devices associate with the AP in their coverage range that offers the fastest data rate available.
- Cisco ClientLink 4.0 technology for improved downlink performance to all mobile devices, including one-, two-, and three-spatial-stream devices up to 802.11ac Wave 1 and Wave 2. The technology also improves battery life on mobile devices.
- Cisco CleanAir technology enhanced with 160MHz channel support. CleanAir delivers proactive, high-speed spectrum intelligence across 20-, 40-, and 80-, and 160-MHz-wide channels to combat performance problems arising from wireless interference.
- MIMO equalization capabilities, which optimize uplink performance and reliability by reducing the impact of signal fade.
You need to verify whether the AP model you have is approved for use in your country. To verify approval and to identify the regulatory domain that corresponds to a particular country, visithttp://www.cisco.com/go/aironet/compliance. Not all regulatory domains have been approved. As and when they are approved, this compliance list will be updated.
The 2800 series access point contains a dedicated 5 GHz radio and a flexible radio that can be configured as a 2.4 GHz radio (default) or as an additional 5 GHz radio. The 2800 series access point configurations are:
The 2802E model is configured with up to four external dual-band dipole antennas, and two 2.4 GHz/ 5 GHz dual-band radios. The radio and antennas support frequency bands 2400–2500 MHz and 5180–5865 MHz through a common dual-band RF interface. Features of the external dual-band dipole antennas are:
- 5 ft Low Loss RF cable with RP-TNC and N-type Connectors (AIR-CAB005LL-R-N/=). You will need four of these.
- 2 ft Smart Antenna Connector to RP-TNC Connectors (AIR-CAB002-DART-R=).
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.
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 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.
The ports and connections on the bottom of the access point are shown in Figure 3.
For more information on the Smart antenna connector, see the “What is a Smart Antenna connector?” section.
- 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 and Grounding the Access Point” section for additional information.
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.
Step 1 Performing a Pre-Installation Configuration (optional)
Step 3 Powering the Access Point
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.
The following Pre-Installation Configuration procedure given does not include configuring Link Aggregation. For information on configuring Link Aggregation, see the Cisco Wireless LAN Controller Configuration Guide, Release 8.2, at this URL:
The pre-installation configuration setup is illustrated in Figure 6.
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 WCS procedures as described in the appropriate Cisco wireless LAN controller guide.
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 “Configuring DHCP Option 43” section for more information.
Note The 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.
Step 2 Apply power to the access point. See Powering the Access Point.
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. 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.
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.
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.)
The standard mounting hardware supported by the AP is listed in Table 1 .
When mounting the AP in areas where there is a possibility of the AP being knocked off the mounting bracket, use the lock hasp on the back of the AP (see Figure 7) to lock it to the bracket.
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.
The information in this section does not include configuring Link Aggregation. For information on configuring Link Aggregation, see the Cisco Wireless LAN Controller Configuration Guide, Release 8.2, at the following URL:
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.
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 CAPWAP support is provided in controller software release 5.2 or later. However, your controller must be running the release that supports 2800 series access points, as specified in the access point data sheet.
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.
- 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 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” 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.
Step 2 Observe the access point LED (for LED descriptions, see “Checking the Access Point LEDs” 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.
c. 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” section for additional information.
The location of the access point status LED is shown in Figure 2.
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 2.
Using the Mode button (see Figure 3) you can:
- Reset the AP to the default factory-shipped configuration.
- Clear the AP internal storage, including all configuration files.
To use the mode button, press, and keep pressed, the mode button on the access point during the AP boot cycle. Wait until the AP status LED changes to Amber. During this, the AP console shows a seconds counter, counting the number of seconds the mode button is pressed. Then:
- To reset the AP to the default factory-shipped configuration, keep the mode button pressed for less than 20 seconds. The AP configuration files are cleared.
- To clear the AP internal storage, including all configuration files and the regulatory domain configuration, keep the mode button pressed for more than 20 seconds, but less than 60 seconds.
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 and the controller 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/28xx Series Integrated Services Routers.
- An access point running software release 220.127.116.11 or later has been newly deployed.
- An existing access point running software release 18.104.22.168 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.
- 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.
The following is a DHCP Option 43 configuration example on a Windows 2003 Enterprise DHCP server for use with Cisco Aironet lightweight access points. For other DHCP server implementations, consult product documentation for configuring DHCP Option 43. In Option 43, you should use the IP address of the controller management interface.
The 2800 series access point uses the type-length-value (TLV) format for DHCP Option 43. DHCP servers must be programmed to return the option based on the access point DHCP Vendor Class Identifier (VCI) string (DHCP Option 43). The VCI string for the 2800 series access point is:
- Type: 0xf1 (decimal 241)
- Length: Number of controller IP addresses * 4
- Value: List of WLC management interfaces
For example, suppose that there are two controllers with management interface IP addresses, 10.126.126.2 and 10.127.127.2. The type is f1(hex). The length is 2 * 4 = 8 = 08 (hex). The IP addresses translate to 0a7e7e02 and 0a7f7f02. Assembling the string then yields f1080a7e7e020a7f7f02. The resulting Cisco IOS command added to the DHCP scope is option 43 hex f1080a7e7e020a7f7f02.
The Flexible Radio Assignment (FRA) feature automatically detects when a high number of devices are connected to a network and changes the dual radios in the access point from 2.4 GHz/5 GHz to 5 GHz/5 GHz to serve more clients. The access point performs this function while still monitoring the network for security threats and RF Interference that may affect performance. Flexible Radio Assignment improves mobile user experience for high-density networks.
The 2802E model has a Smart antenna connector (see Figure 8), which is connected directly to the flexible radio. Without a supported external antenna connected to the Smart Antenna connector, the flexible radio can stay only in 2.4 GHz mode. If an external antenna is connected, the flexible radio can be used in the full Flexible Radio Assignment mode, allowing dual 5 GHz and Wireless Security Monitoring modes.
To connect to any supported RP-TNC connector-type external antenna to the Smart antenna connector, use the DART cable connector AIR-CAB002-DART-R= (see Figure 9), which is to be procured separately from Cisco.
Cisco ClientLink 4.0 is a beamforming capability built into Cisco Aironet wireless LAN access points. When the access point concentrates signals toward the receiving client, that client is better able to hear the AP’s transmission, and so throughput is greater. ClientLink also enhances performance in the uplink (client-to-AP) direction, so that the AP can also better hear the client communications. The result is improved performance in both directions, and doesn’t require any special capabilities in the client device to work.
ClientLink works with all client technologies. It makes sure each client type always operates at the best possible rate, as determined by the 802.11 access technology supported, network conditions, and the distance of the client from the Wi-Fi AP. ClientLink helps maintain maximum client rates.
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: