Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.6.120.0
Cisco Wireless LAN Controller and Access Point Platforms
Supported Cisco Wireless LAN Controller Platforms
Supported Access Point Platforms
Unsupported Cisco Wireless LAN Controller Platforms
Cisco WLAN Express Setup for Cisco 2500 Series Wireless Controller
Setting up Cisco 2500 Series Wireless Controller Using Cisco WLAN Express Setup
New Dashboard of Cisco 2500 Series Wireless Controller Using Cisco WLAN Express Setup
Default Configurations of Cisco 2500 Series Wireless Controller Using Cisco WLAN Express Setup
Software Release Support for Access Points
Software Release Types and Recommendations
Software Release Recommendations
Upgrading to Cisco WLC Software Release 7.6.120.0
Upgrading to Cisco WLC Software Release 7.6.120.0 (GUI)
Special Notes for Licensed Data Payload Encryption on Cisco Wireless LAN Controllers
Downloading and Installing a DTLS License for an LDPE Cisco WLC
Upgrading from an LDPE to a Non-LDPE Cisco WLC
Interoperability With Other Clients in Release 7.6.120.0
Features Not Supported on Cisco WLC Platforms
Features Not Supported on Cisco 2500 Series WLCs
Features Not Supported on WiSM2 and Cisco 5500 Series WLCs
Features Not Supported on Cisco Flex 7500 WLCs
Features Not Supported on Cisco 8500 WLCs
Features Not Supported on Cisco Virtual WLCs
Features Not Supported on Mesh Networks
FCC Safety Compliance Statement
Obtaining Documentation and Submitting a Service Request
These release notes describe what is new in this release, instructions to upgrade to this release, and open and resolved caveats for this release. Unless otherwise noted, all Cisco Wireless LAN Controllers are referred to as Cisco WLCs, and all Cisco lightweight access points are referred to as access points or Cisco APs.
These release notes contain the following sections:
The section contains the following subsections:
The following Cisco WLC platforms are supported in this release:
The following access point platforms are supported in this release:
http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78_461543.html
http://www.cisco.com/c/en/us/products/collateral/routers/887-integrated-services-router-isr/data_sheet_c78_459542.html
http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78-613481.html
http://www.cisco.com/c/en/us/products/collateral/routers/880-3g-integrated-services-router-isr/data_sheet_c78_498096.html
http://www.cisco.com/c/en/us/products/collateral/routers/880g-integrated-services-router-isr/data_sheet_c78-682548.html
http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78-519930.html
Note AP802 is an integrated access point on the next generation Cisco 880 Series ISRs.
Note Before you use an AP802 series lightweight access point with Cisco WLC software release 7.6.120.0, you must upgrade the software in the Next Generation Cisco 880 Series ISRs to Cisco IOS 15.1(4)M or later releases.
The following Cisco WLC platforms are not supported:
This section provides a brief description of what is new in Release 7.6.120.0:
– Cisco Aironet 2700 Series Access Points. For more information see, http://www.cisco.com/c/en/us/products/wireless/aironet-2700-series-access-point/index.html.
– Cisco Aironet 700W Series Access Point. For more information see, http://www.cisco.com/c/en/us/products/wireless/aironet-700w-series/index.html.
Initially, the Ethernet ports of the 700W Series access points are disabled.
Use the config ap lan < port_id > < enable/disable > < AP_name > command to enable the Ethernet ports.
Use the show ap lan < port_id > < AP_name > and show ap lan port-summary < AP_name > commands to view the port details of the access point.
7.6.120.0 introduces Cisco WLAN Express Setup on Cisco 2500 Series Wireless Controller. It includes easy to use GUI Configuration Wizard, an intuitive monitoring dashboard and several Cisco Wireless LAN best practices enabled by default.
1. Connect and power on the controller.
2. Connect a computer to port 2 of the controller using an Ethernet cable. The controller uses auto-sense. You can use a straight-through Ethernet cable.
Note AutoInstall starts on port 1. If port 1 is connected to network and if AutoInstall gets a configuration file from the TFTP server, it interrupts the configuration process and disables the GUI Configuration Wizard on port 2.
a. The port LED will be green if both the machines are properly connected.
b. The controller might take some time to be fully powered on and the GUI to be available on the computer. The LEDs on the front panel of the controller indicate the system status:
– The controller is not ready if the LEDs are blinking or are amber in color.
– The controller is ready if the SYS LED is green and ALM LED is off.
– When you connect the computer to port 2, the machine gets an IP address 192.168.1.x (100 and above).
3. Open a client web browser at http://192.168.1.1 from the computer connected to port 2 to access the controller GUI configuration.
Turn off the computer's other network connections (for examples, WiFi) if there is an IP conflict.
6. In Step 1—You setup your controller and configure the parameters.
7. In Step 2—You create your wireless network.
By default, you must create your Employee network.
– Security Method—The default security method is WPA2 Personal. If you choose WPA2 Personal, you must configure the passphrase. If you choose WPA2 Enterprise, you must configure the RADIUS IP address and shared secret.
– Security Method—The default security method is Web Consent. Choose Web Consent if you do not want any preconfigured password. A guest user has to acknowledge an Accept Use Policy (AUP) policy. Select WPA Personal if you want guest users to be authenticated using a password to gain access to the guest network.
8. Verify the configured parameters and click Apply and OK. The controller reboots.
9. Disconnect the computer from port 2 of the controller.
10. Connect port 1 of the controller to the network switch trunk port.
11. Connect access points to the network switch.
12. Access points will join the controller and the configured wireless network is available.
13. Connect wireless clients to the wireless network.
14. Connect the computer to the network and access the controller GUI.
15. After you login, you can view the new dashboard. For more details, see New Dashboard of Cisco 2500 Series Wireless Controller Using Cisco WLAN Express Setup. Click Advanced to view the legacy Monitor Summary page. From the Monitor Summary page, click the Home icon to view the new dashboard.
The new dashboard of the Cisco 2500 Series Wireless Controller with Cisco WLAN Express Setup provides a summary of the configured wireless networks, access points, active client devices, rogues, and interferers. You can also view details of top access points, applications, operating systems, and clients as a table or as a pie chart.
When you click the elements that appear on top of the dashboard, you can view the details in the corresponding pages:
Click the Dashboard Settings icon on the top right corner of the GUI to configure the dashboard options. You can change the data format to rate or volume.
You can also choose the default landing page of the controller GUI in the options page as the new dashboard or the legacy Monitor Summary page by changing the Landing Page option.
When you configure your Cisco 2500 Series Controller using the Cisco WLAN Express Setup, the following parameters are enabled or disabled. These settings are different from the default settings obtained when you configure the controller using the CLI wizard, and different from the default settings on other controller platforms.
Table 1 lists the Cisco WLC software releases that support specific Cisco access points. The First Support column lists the earliest Cisco WLC software release that supports the access point. For access points that are not supported in ongoing releases, the Last Support column lists the last release that supports the access point.
Note Third-party antennas are not supported with Cisco indoor access points.
Note The Cisco 3600 Access Point was introduced in Release 7.1.91.0. If your network deployment uses Cisco 3600 Access Points with Release 7.1.91.0, we highly recommend that you upgrade to Release 7.2.103.0 or a later release. |
|||
-A and N: 4.1.190.1 or 5.2 or later1 |
|||
This section contains the following topics:
Software releases that provide bug-fix support and ongoing software maintenance. These releases are categorized as Maintenance Deployment (MD) and may be part of the AssureWave program.2 These are long-lived releases with ongoing software maintenance. |
Provides you with a software release that offers stability and long support duration with periodic maintenance releases (MRs). |
|
Software releases that provide new features and new hardware platform support in addition to bug fixes. These releases are categorized as Early Deployment (ED). These are short-lived releases. |
Allows you to deploy the latest features and new hardware platforms or modules. |
For detailed release recommendations, see the software release bulletin:
http://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/bulletin-c25-730741.pdf
For more information about the Cisco Wireless solution compatibility matrix, see http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html.
1. Downgrade the Cisco WLC to 7.4.121.0.
LAP would still not join the Cisco WLC as it is running the 7.6 image in it, which it once downloaded.
2. Delete the 7.6 image from LAP CLI, so it boots from the rcvk image.
Booting from the rcvk image lets it form DTLS with out-of-order packet situation.
The rcvk image should not be 7.6 image. If it fails on rcvk image too, then probably we have 7.6 based rcvk image in it.
3. Download the 7.4 rcvk image in the AP, via archive download-sw /force /overwrite commands.
LAP downloads the 7.4 code and boots using it. Using 7.4 code on both the ends, will get the DTLS session up, with out-of-order packets.
Key point is to not use 7.6 image at either ends, LAP or WLC.
Further Problem Description : LAP with MTU 1400 is unable to set up DTLS with Cisco WLC. The cert present by the AP, arrive on the Cisco WLC properly fragmented but out of order. According to Cisco WLC debug dtls, it fails with the following “debug dtls all enable” logs on Cisco WLC:
a. Enter the following commands:
b. After the reboot, press Esc on the console, and use the boot menu to select Release 7.6.
c. After booting on Release 7.6, set back the primary boot, and save the configuration by entering the following command:
Note The epings are not available in Cisco 5500 Series WLC when New Mobility is enabled.
Note If you downgrade from a Cisco WLC release that supports new mobility to a Cisco WLC release that does not support new mobility (for example, Release 7.6 to Release 7.3.x) and you download the 7.6 configuration file with new mobility in enabled state, the release that does not support new mobility will have the new mobility feature in enabled state.
Note The FUS image installation process reboots the Cisco WLC several times and reboots the runtime image. The entire process takes approximately 30 minutes. We recommend that you install the FUS image in a planned outage window.
Note If you are using a Cisco 2500 Series controller and you intend to use the Application Visibility and Control (AVC) and NetFlow protocol features, you must install Release 1.9.0.0 of Cisco Wireless LAN Controller Field Upgrade Software (FUS). This is not required if you are using other controller hardware models.
Note Bootloader upgrade is not required if FIPS is disabled.
For the Cisco WLAN Express Setup for Cisco 2500 Series Wireless Controller feature, we recommend the following browsers:
– Microsoft Internet Explorer 10 or a later version
– Mozilla Firefox 26 or a later version
– Apple Safari 6 or a later version
– Ensure that your TFTP server supports files that are larger than the size of Cisco WLC software Release 7.6.120.0. Some TFTP servers that support files of this size are tftpd32 and the TFTP server within the Prime Infrastructure. If you attempt to download the 7.6.120.0 Cisco WLC software and your TFTP server does not support files of this size, the following error message appears:
“TFTP failure while storing in flash.”
– If you are upgrading through the distribution system network port, the TFTP or FTP server can be on the same subnet or a different subnet because the distribution system port is routable.
Bootloader menu for Cisco 5500 Series WLC:
Bootloader menu for other Cisco WLC platforms:
Enter 1 to run the current software, enter 2 to run the previous software, enter 4 (on a 5500 series Cisco WLC), or enter 5 (on another Cisco WLC platform) to run the current software and set the Cisco WLC configuration to factory defaults. Do not choose the other options unless directed to do so.
Note See the Installation Guide or the Quick Start Guide pertaining to your Cisco WLC platform for more details on running the bootup script and power-on self test.
With the backup image stored before rebooting, choose Option 2: Run Backup Image from the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot the Cisco WLC.
config network ap-discovery nat-ip-only { enable | disable }
– enable — Enables use of NAT IP only in a discovery response. This is the default. Use this command if all the APs are outside the NAT gateway.
– disable —Enables use of both NAT IP and non-NAT IP in a discovery response. Use this command if APs are on the inside and outside the NAT gateway; for example, Local Mode and OfficeExtend APs are on the same Cisco WLC.
Note To avoid stranding APs, you must disable AP link latency (if enabled) before you use the disable option for the config network ap-discovery nat-ip-only command. To disable AP link latency, use the config ap link-latency disable all command.
– You can predownload the AP image.
– For FlexConnect access points, use the FlexConnect AP upgrade feature to reduce traffic between the Cisco WLC and the AP (main site and the branch). For more information about the FlexConnect AP upgrade feature, see the Cisco Wireless LAN Controller FlexConnect Configuration Guide.
Note Predownloading Release 7.6.120.0 on a Cisco Aironet 1240 access point is not supported when upgrading from a previous Cisco WLC release. If predownloading is attempted on a Cisco Aironet 1240 access point, an AP disconnect will occur momentarily.
– Delete all the WLANs that are mapped to interface groups, and create new ones.
– Ensure that all the WLANs are mapped to interfaces rather than interface groups.
– Enable or disable link aggregation (LAG)
– Enable a feature that is dependent on certificates (such as HTTPS and web authentication)
– Add a new license or modify an existing license
– Increase the priority for a license
– Install the vendor-device certificate
– Upload the configuration file
– Install the Web Authentication certificate
– Make changes to the management interface or the virtual interface
Step 1 Upload your Cisco WLC configuration files to a server to back them up.
Note We highly recommend that you back up your Cisco WLC configuration files prior to upgrading the Cisco WLC software.
Step 2 Follow these steps to obtain the 7.6.120.0 Cisco WLC software:
a. Click this URL to go to the Software Center:
https://software.cisco.com/download/navigator.html
b. Choose Wireless from the center selection window.
c. Click Wireless LAN Controllers.
The following options are available:
– Integrated Controllers and Controller Modules
d. Depending on your Cisco WLC platform, select one of these options.
e. Click the Cisco WLC model number or name.
The Download Software page is displayed.
f. Click a Cisco WLC software release number. The software releases are labeled as follows to help you determine which release to download:
g. Click a software release number.
h. Click the filename ( filename.aes).
j. Read the Cisco End User Software License Agreement and click Agree.
k. Save the file to your hard drive.
l. Repeat steps a. through k. to download the remaining file.
Step 3 Copy the Cisco WLC software file ( filename.aes) to the default directory on your TFTP, FTP, or SFTP server.
Step 4 (Optional) Disable the Cisco WLC 802.11a/n and 802.11b/g/n networks.
Note For busy networks, Cisco WLCs on high utilization, or small Cisco WLC platforms, we recommend that you disable the 802.11a/n and 802.11b/g/n networks as a precautionary measure.
Step 5 Choose Commands > Download File to open the Download File to Controller page.
Step 6 From the File Type drop-down list, choose Code.
Step 7 From the Transfer Mode drop-down list, choose TFTP, FTP, or SFTP.
Step 8 In the IP Address text box, enter the IP address of the TFTP, FTP, or SFTP server.
Step 9 If you are using a TFTP server, the default values of 10 retries for the Maximum Retries text field, and 6 seconds for the Timeout text field should work correctly without any adjustment. However, you can change these values if desired. To do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries text box and the amount of time (in seconds) that the TFTP server attempts to download the software, in the Timeout text box.
Step 10 In the File Path text box, enter the directory path of the software.
Step 11 In the File Name text box, enter the name of the software file ( filename.aes).
Step 12 If you are using an FTP server, follow these steps:
a. In the Server Login Username text box, enter the username to log on to the FTP server.
b. In the Server Login Password text box, enter the password to log on to the FTP server.
c. In the Server Port Number text box, enter the port number on the FTP server through which the download occurs. The default value is 21.
Step 13 Click Download to download the software to the Cisco WLC.
A message appears indicating the status of the download.
Step 14 After the download is complete, click Reboot.
Step 15 If you are prompted to save your changes, click Save and Reboot.
Step 16 Click OK to confirm your decision to reboot the Cisco WLC.
Step 18 For Cisco WiSM2 on the Catalyst switch, check the port channel and re-enable the port channel if necessary.
Step 19 If you have disabled the 802.11a/n and 802.11b/g/n networks in (Optional) Disable the Cisco WLC 802.11a/n and 802.11b/g/n networks., re-enable them.
Step 20 To verify that the 7.6.120.0 Cisco WLC software is installed on your Cisco WLC, click Monitor on the Cisco WLC GUI and view the Software Version field under Controller Summary.
Datagram Transport Layer Security (DTLS) is required for all Cisco 600 Series OfficeExtend Access Point deployments to encrypt data plane traffic between the APs and the Cisco WLC. You can purchase Cisco Wireless LAN Controllers with either DTLS that is enabled (non-LDPE) or disabled (LDPE). If DTLS is disabled, you must install a DTLS license to enable DTLS encryption. The DTLS license is available for download on Cisco.com.
Important Note for Customers in Russia
If you plan to install a Cisco Wireless LAN Controller in Russia, you must get a Paper PAK, and not download the license from Cisco.com. The DTLS Paper PAK license is for customers who purchase a Cisco WLC with DTLS that is disabled due to import restrictions, but have authorization from local regulators to add DTLS support after the initial purchase. Refer to your local government regulations to ensure that DTLS encryption is permitted.
Note Paper PAKs and electronic licenses that are available are outlined in the respective Cisco WLC platform data sheets.
Step 1 Download the Cisco DTLS license.
a. Go to the Cisco Software Center at this URL:
https://tools.cisco.com/SWIFT/LicensingUI/Home
b. On the Product License Registration page, choose Get New > IPS, Crypto, Other Licenses.
c. Under Wireless, choose Cisco Wireless Controllers (2500/5500/7500/8500/WiSM2) DTLS License.
d. Complete the remaining steps to generate the license file. The license file information will be sent to you in an e-mail.
Step 2 Copy the license file to your TFTP server.
Step 3 Install the DTLS license. You can install the license either by using the Cisco WLC web GUI interface or the CLI:
Management > Software Activation > Commands > Action : Install License
license install tftp ://ipaddress /path /extracted-file
After the installation of the DTLS license, reboot the system. Ensure that the DTLS license that is installed is active.
Step 1 Download the non-LDPE software release:
a. Go to the Cisco Software Center at this URL:
http://www.cisco.com/cisco/software/navigator.html?mdfid=282585015&i=rm
b. Choose the Cisco WLC model.
c. Click Wireless LAN Controller Software.
d. In the left navigation pane, click the software release number for which you want to install the non-LDPE software.
e. Choose the non-LDPE software release: AIR-X-K9-X-X.X.aes
g. Read the Cisco End User Software License Agreement and then click Agree.
h. Save the file to your hard drive.
Step 2 Copy the Cisco WLC software file ( filename.aes) to the default directory on your TFTP server or FTP server.
Step 3 Upgrade the Cisco WLC with this version by performing Copy the Cisco WLC software file ( filename.aes) to the default directory on your TFTP, FTP, or SFTP server. through To verify that the 7.6.120.0 Cisco WLC software is installed on your Cisco WLC, click Monitor on the Cisco WLC GUI and view the Software Version field under Controller Summary. detailed in the “Upgrading to Cisco WLC Software Release 7.6.120.0” section.
This section describes the interoperability of Release 7.6.120.0 of the Cisco WLC software with other client devices.
Table 6 describes the configuration used for testing the clients.
Table 7 lists the client types on which the tests were conducted. The clients included laptops, handheld devices, phones, and printers.
This section lists the features that are not supported on the different Cisco WLC platforms:
Note The features that are not supported on Cisco WiSM2 and Cisco 5500 Series WLCs are not supported on Cisco 2500 Series WLCs too.
Note Directly connected APs are supported only in the Local mode.
Note You can replicate this functionality on a Cisco 5500 Series WLC by creating an open WLAN using an ACL.
Note For Cisco Flex 7500 Series WLCs, it is not necessary to configure an AP-manager interface. The management interface acts like an AP-manager interface by default, and the access points can join on this interface.
Note IPv6 client bridging and Router Advertisement Guard are supported.
Note An AP associated with the Cisco WLC in the local mode should be converted to the FlexConnect mode or Monitor mode, either manually or by enabling the autoconvert feature. On the Cisco Flex 7500 WLC CLI, enable the autoconvert feature by entering the config ap autoconvert enable command.
Note FlexConnect local-switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect access points do not limit traffic based on IGMP or MLD snooping.
Note FlexConnect local-switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect access points do not limit traffic based on IGMP or MLD snooping.
Note Outdoor APs in the FlexConnect mode are supported.
The following sections lists Open Caveats and Resolved Caveats for Cisco WLCs and lightweight access points for Release 7.6.120.0. To enable you to locate caveats in the Cisco Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
https://tools.cisco.com/bugsearch/search
Note If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.
Table 8 lists the open caveats in the 7.6.120.0 Cisco WLC software release.
Symptom : Cisco lightweight access point (LAP) is unable to set up DTLS with Cisco WLC. Conditions : LAP trying to join Cisco WLC using ap3g1-k9w8-tar.152-4.JB4.tar image. 1. Downgrade the Cisco WLC to 7.4.121.0. LAP would still not join the Cisco WLC as it is running the 7.6 image in it, which it once downloaded. 2. Delete the 7.6 image from LAP CLI, so it boots from the rcvk image. Booting from the rcvk image lets it form DTLS with out-of-order packet situation. The rcvk image should not be 7.6 image. If it fails on rcvk image too, then probably we have 7.6 based rcvk image in it. 3. Download the 7.4 rcvk image in the AP, via archive download-sw /force /overwrite commands. LAP downloads the 7.4 code and boots using it. Using 7.4 code on both the ends, will get the DTLS session up, with out-of-order packets. Key point is to not use 7.6 image at either ends, LAP or WLC. Further Problem Description : LAP with MTU 1400 is unable to set up DTLS with Cisco WLC. The cert present by the AP, arrive on the Cisco WLC properly fragmented but out of order. According to Cisco WLC debug dtls, it fails with the following “debug dtls all enable” logs on Cisco WLC:
*spamApTask4: Apr 17 16:54:15.551: openssl_shim_info_callback: SSL state = 0x2181; where = 0x2002; ret = 0x0
|
|
Symptom : Wireless clients cannot receive broadcast packets after broadcast key rotation. Conditions : Dynamic WEP; Release 7.0.235.0, 7.2.110.0, and 7.3.101.0. Workaround : Enter the config advanced eap bcast-key-interval 86400 command in the middle of the night and then change security setting to WPA2. |
|
Symptom : Client entry is seen on multiple Cisco WLCs even when it is not anchored to a Cisco WLC or part of its mobility group. |
|
Symptom : The FT and LT detection time for an alarm is ahead or later than the AP clock. This causes a delay in Cisco NCS to detect the alarm. In Cisco NCS, the alarm is not seen until the actual AP time matches the time reported in the FT. |
|
Symptom : Rogue containment fails on a 5-GHz radio. |
|
Symptom : Disabled SSID is broadcast by a 2.4-GHz radio. Conditions : SSID was created and disabled previously. This is a very rare occurrence, and only seen once; never reproduced in the lab, |
|
Symptom : Consecutive SNMP ‘set’ commands for same MIB variable on Cisco WLC fails. Conditions : When we set a MIB object on Cisco WLC using SNMP ‘set’ command, it works at the first attempt. However, if you repeat the same command, the following error message is displayed: |
|
Symptom : Client gets IPv6 address from a different VLAN. Conditions : This is a combination of the following factors:
|
|
Symptom : Client with static IP address loses connectivity on session timeouts. Conditions : This occurs only if the following conditions are met: Interface that the client would get from an interface group does not match the interface corresponding to the static IP address. Client gets VLAN overridden and the following message is displayed:
apfReceiveTask: May 28 12:48:28.066: 00:1a:70:a5:2f:bd Overriding interface of client from 'vlan20' to 'vlan30' within interface group 'vlan20-30'
*apfReceiveTask: May 28 12:48:28.066: 00:1a:70:a5:2f:bd Applying Interface policy on Mobile, role Local. Ms NAC State 2 Quarantine Vlan 0 Access Vlan 20
This overriding is lost when PMK expires, and a new authentication occurs. This occurs even if the client continuously sends traffic. Workaround : Either disable interface groups or enable DHCP required. |
|
Symptom : The show redundancy summary command shows the following line regardless of its real SKU: Conditions : Enter the show redundancy summary command on the following: Secondary Cisco WLC which is converted from the primary Cisco WLC. |
|
Symptom : Cisco WLC sends incorrect information for Rogue AP detection through traps. |
|
Symptom : Cisco lightweight access point displays %CAPWAP-3-ERRORLOG messages when AP associates with the Cisco WLC: |
|
Symptom : This issue is to track and discuss default QoS values for L2 and L3 QoS priority markings. Workaround : You can map each priority on its switch/router between Cisco WLC and AP. In Release 7.5, the default value of DSCP is 18 (010 010), which is IP Precedence 2 and it belongs to Class 2. |
|
Symptom : FT roam fails between FlexConnect APs. Conditions : FT client and FlexConnect APs advertising 802.11r FT PSK WLAN. Workaround : Use FT-802.1x or use 11i fast roam methods like OKC because normal roam occurs because FT roam fails. |
|
Symptom : The foreign Cisco WLC does not respond to ARP from foreign export client to a local client being on the same VLAN. |
|
Symptom : Cisco WLC uses 0.0.0.0 as source IP for mDNS query or response when Cisco WLC has untagged interface. Conditions : WLAN attached with untagged interface; mDNS client associated with this WLAN client request for service using mDNS; when Cisco WLC responds, it uses 0.0.0.0 as source IP address so the service provider might or might not be seen on the client device. |
|
Symptom : 802.11r roaming failure. Conditions : Client sends retry packet for FT-AUTH request. Original packet and then following a retry, packet with same SN. Workaround : Use a non-802.11r SSID/clients. Further Problem Description : AP does not detect the second retry packet as a duplicate packet and forwards both packets to Cisco WLC. Therefore, there are two FT-Auth responses with different Announce numbers and (FT-AUTH responses from Cisco WLC). Client uses the Announce received in the first FT-AUTH but Cisco WLC has the last updated Announce (which is sent for retry packet). This results in MIC failure. |
|
Symptom : Cisco APs in FlexConnect local switching mode with VLAN mappings dissociate from Cisco WLC when an ACL is applied to one of the VLANs. Once ACL is pushed, CAPWAP UDP processing become sluggish and retransmissions of packets from Cisco WLC result in errors with duplicate sequence number errors. Eventually, this state causes a DTLS timeout and reassociation process on the AP, which fails over and over with same issue. It appears that the issue is related to corruption of the CAPWAP private configuration because the actual content of the ACL does not matter. The issue occurs immediately at the point the ACL is pushed. Conditions : FlexConnect mode APs with VLAN mappings and FlexConnect ACL. Workaround : Do not apply ACL to the AP; use another enforcement point if required. Perform a reimage of the AP with 15.2 recovery image. |
|
Symptom : Apple devices such as iPad, iPhone, and iPod are unable to switch transparently from a 802.1X WLAN to a WPA-WPA2(PSK) WLAN. Conditions : Cisco AP1142 is used with Cisco WLC using Release 7.5.102.0; FlexConnect local switching is used; two SSIDs are created—one with 802.1X authentication and the other with WPA-PSK. Switching from the 802.1X WLAN to the PSK one does not happen smoothly Workaround : Use another AP (tested with AP1262 and AP3501); or use a Cisco WLC release other than 7.5.102.0. |
|
Symptom : Cisco WLC accepts the SysRq Magic key on the console. This allows even an unauthenticated user who has access to the serial console to unconditionally reboot the Cisco WLC from the SysRq menu. Following is the SysRq menu that pops up when you enter the magic key:
SysRq : HELP : loglevel0-8 reBoot Crashdump tErm Full kIll Dump showMem Nice showPc show-all-timers(Q) Sync showTasks Unmount shoW-blocked-tasks
SysRq magic key given from the serial console Workaround : Return key exits from the SysRq menu and returns to the console. Cisco WLC will still function normally while in the SysRq menu or even after exiting. |
|
Symptom : Cisco WLC unresponsive. |
|
Symptom : 802.11r Roaming—AP might sometimes send deauthentication with reason code 7. Conditions : AP roam in a bad RF environment. Clients fail to hear ACK for reassociation request from AP and continues to send reassociation request and following a data packet. Workaround : After the deauthentication, complete roam occurs and the clients can join again. Further Problem Description : This issue is seen very rarely and only with Samsung I565 phones. |
|
Symptom : clmgmtLicenseUsageCountRemaining task does not return the remaining AP count. |
|
Symptom : lb._dns-sd._udp.<domain-name> service is not supported by Cisco WLC. Conditions : When clients query for services of the nature mdns:lb._dns-sd._udp.<domain-name>, the Cisco WLC does not process the request because it is not listed in the master service database. Therefore, the service provider might or might not see the service provider. Workaround : Remove the domain name setting in the DHCP and on the clients (iPads, iPhones, and so on) from the server setting. |
|
Symptom : AP secures CAC bandwidth for SIP phone in case of inter-Cisco WLC roaming even though the phone does not have any active SIP call. Conditions : SIP phone is roaming inter-Cisco WLC. Occurs only in case of a 32-byte call ID. |
|
Symptom : On an 802.1X WLAN that has local switching in enabled state and where P2P blocking is in enabled state, if two clients are associated with the same AP, P2P blocking between them does not work as designed. However, for SSID with OPEN authentication, it works as expected. |
|
Symptom : When the Cisco WLC gets a CoA (Change of Authorization) RADIUS message, for example from ISE, the Cisco WLC sends a deauthentication to the client and move the client to DHCP_REQ state. Unless “DHCP Required” is disabled on the WLAN, this means that the client will then be disconnected unless it performs a new DHCP request. With “debug client” in effect on the Cisco WLC, the following message will be seen: Conditions : Cisco WLC is using CoA from RADIUS and has DHCP Required on the WLAN. Client is one that does not reliably re-DHCP upon 802.11 deauthentication; some Windows 7 and Mac OS X systems have been seen to have this problem. Workaround : For a single VLAN system (same VLAN before and after CoA), disable DHCP Required. For some client types, you might be able to reconfigure them to make sure that they re-DHCP as needed. For example, on a Windows 7 system, perform the following: 1. In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces registry path, create a DWORD value named as ?UseNetworkHint? and set it to ?0?. 2. Restart the DHCP client service by executing the following commands from elevated command prompt: An alternative might be to use two VLANs, one a pre-CoA and the other a post-CoA. The DHCP leases for the pre-CoA scope might be set with very short lease durations such as 30 seconds. This should trigger a more timely DHCP lease renewal from the client so that it can regain access to the network after the CoA event. |
|
Symptom : config advanced statistics command cannot be applied in Cisco WLC. |
|
Symptom : Clients get disconnected from FlexConnect AP. 802.11 deauthentication with Reason Code 1 (Unspecified) WLC “debug client” output shows “Sent Deauthenticate to mobile on BSSID 00:3a:98:8a:70:a0 slot 0 (caller 1x_bcastkey.c:951)”. Conditions : Cisco Flex 7510 WLC using Release 7.4.110.0; Cisco AP 1602 in FlexConnect mode; WLAN = WPA2 AES PSK, Central Authentication, Local Switching. |
|
Symptom : SNMP get for Cisco WiSM2 reports that Cisco WiSM2 has secondary power supply. |
|
Symptom : A client roam between two Cisco WLCs can fail intermittently making the client to be part of the VLAN originally mapped to the WLAN; for example two Cisco WLC serving clients, WLAN mapped to VLAN x, RADIUS assigned to VLAN y; intermittently, client can be put on VLAN x during roams between WLC1 to WLC2. Conditions : When a client roams between two Cisco WLCs. Further Problem Description : Debug example:
pemReceiveTask: Oct 09 15:58:40.382: 60:fe:c5:69:ef:50 Set symmetric mobility tunnel for 60:fe:c5:69:ef:50 as in Foreign role *pemReceiveTask: Oct 09 15:58:40.382: 60:fe:c5:69:ef:50 167.73.161.198 Added NPU entry of type 1 dtlFlags 0x1 *pemReceiveTask: Oct 09 15:58:40.382: 60:fe:c5:69:ef:50 Skip Foreign / Export Foreign Client IP 167.73.161.198 plumbing in FP SCB *bcastReceiveTask: Oct 09 15:58:40.389: Sending MLD query First Time to 0C:85:25:C6:71:90 ap for mgid 15 *bcastReceiveTask: Oct 09 15:58:40.389: Entry for ap 0C:85:25:C6:71:90 MLD query packet not queued for mgid 15... Enquing the Query packet... *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP received op BOOTREQUEST (1) (len 308 vlan 0 port 13 encap 0xec03) *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP processing DHCP DISCOVER (1) *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP op: BOOTREQUEST htype: Ethernet hlen: 6 hops: 0 *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP xid: 0x75555ccb (1968528587) secs: 43 flags: 0 *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP chaddr: 60:fe:c5:69:ef:50 *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP ciaddr: 0.0.0.0 yiaddr: 0.0.0.0 *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP siaddr: 0.0.0.0 giaddr: 0.0.0.0 *DHCP Socket Task: Oct 09 15:58:41.520: 60:fe:c5:69:ef:50 DHCP successfully bridged packet to EoIP tunnel
|
|
Symptom : Trunk VLAN ID is not saved for Cisco AP1240. The VLAN ID is set in the Advanced tab. The Cisco AP reboots, but the VLAN ID is not displayed. http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01101110.html#task_43A307F686B3487F931FA496571987CA Issue is not seen on other AP platforms such as Cisco AP3600 or AP1140. |
|
Symptom : Following an HA failover, the service port on the active Cisco WLC that is configured to get its IP address through DHCP loses connectivity after the DHCP lease expires (or the DHCP renew is forced through the config interface dhcp service-port { enable | disable } command). In case of Cisco WiSM2, this connectivity issue might cause the Cisco WLC and Catalyst 6000 to fail to exchange WCP keep-alives. Thus, the show wism status command shows the active module to be not operational.
Workaround : Configure a static IP address for the service ports on both peers and force an HA switchover. From the active Cisco WLC, enter the following commands: config interface dhcp service-port disable config interface address service-port addr1 netmask config redundancy interface address peer-service-port addr2 netmask Forcing a switchover might disconnect all the clients and any mesh APs in Release 7.4.X. Therefore, we recommend that you perform this workaround during a maintenance window. |
|
Symptom : When a port in a LAG goes down and then comes back up, the Cisco WLC does not send ‘interface up’ message to syslog server. Conditions : This issue is seen when distribution ports are configured in a LAG, and syslog server is configured. |
|
Symptom : Cisco WLC stops responding when the show local-auth certificates commands is entered. |
|
Symptom : Cisco 5500 Series WLC lost some setting after restoring the configuration file. |
|
Symptom : Cisco WLC unresponsive on task name ‘emWeb’. Conditions : Cisco 5508 WLC using Release 7.3.112.0 with a mobility setup. |
|
Symptom : Cisco WLC unexpectedly reboots with Reaper Reset. System Stack indicates tsmClientStatsDataLock. |
|
Symptom : A CCKM client associated with a FlexConnect AP using Cisco WLC Release 7.4.110.0 (local switching/central authentication) might lose IP connectivity soon after a successful CCKM roaming while remaining associated with the AP. On Cisco WLAN phone, the symptom is often seen as a two-way voice outage, phone stuck in “requesting DHCP” state. On the AP side, a radio level debugging shows decryption errors. Conditions : Cisco WLC/AP using Release 7.4.110.0; FlexConnect local switching and central authentication; frequent CCKM roaming events including interband roaming. Workaround : The issue recovers soon after the client roams to another AP. Further Problem Description : This is not a persistent issue; normally, the client can then roam back to the AP without any issues. |
|
Symptom : Cisco APs disconnect from the Cisco WLC due to DTLS errors. |
|
Symptom : When you try to enable AP Management on dynamic interface, the “Failed to Add MDNS profile” message is displayed. |
|
Symptom : FlexConnect VLAN mode was changed to disabled after a power cycle. |
|
Symptom : Serial number of virtual controller changes when using DRS or Vmotion. Conditions : When you use DRS or vMotion for high availability on VMware, the UUID changes and invalidates the AP licenses. |
|
Symptom : Controller reports its MAC address in the duplicate IP message. |
|
Symptom : Problems with RADIUS server of the controller:
Conditions : When the primary RADIUS server fails, the secondary and tertiary servers fails within two seconds. |
|
Symptom : DHCP IPv6 address is detected as duplicate address on MAC and linux. Workaround : Use Stateless Address Autoconfiguration (SLAAC) address on MAC. |
|
Symptom : Running configuration uploaded to a TFTP/FTP server does not contain WLAN and Layer 2 ACL configurations. Conditions : When you upload the running configuration to a TFTP/FTP server. |
|
Symptom : RADIUS profiling fails for Windows XP and Windows 7 workstations. ISE reports the client endpoint profile endpoint policy as Unknown. |
|
Symptom : Controller does not include the virtual IP address in the redirect URL to the internal web engine. Conditions : Controller has 7.6.100.0 and WLAN is configured with 802.1X + conditional web redirect. |
|
Symptom : 1552c AP shows the BVI1 interface is up and Gig0 interface on the cable modem is also up. AP does not use the cable modem Ethernet and reverts to the radio interface. AP reboots and Gig0 interfaces are blocked. Conditions : When AP boots, BVI1 is created and cable modem’s Gig0 interface comes up. Ethernet connection between motherboard bvi1 interface and cm gig0 port is not used. |
|
Symptom : Connection of wired client breaks as it roams on a Flexconnect AP. The AP sends XID frames only to wired clients and not to the WGB to update the switch MAC address table.
Workaround : Reduce the MAC address aging time for the WGB and wired client VLAN on the switches. |
|
Symptom : Some ranges of multicast addresses multicast traffic do not work on 7500, 8500, and virtual controllers. |
|
Symptom : CAPWAP APs send deauthentication frames on new channel changed due to RRM DCA. |
|
Symptom : Wireless client connectivity problems on 802.1x-enabled SSIDs with release 7.6. |
|
Symptom : Controller crash at snmpApCurrChanChangedTrapSend. |
|
Symptom : Unable to compile CISCO-LWAPP-DOT11-CLIENT-MIB by MG-Soft 6.0. The following error appears: |
|
Symptom : Timestamp tolerance value changes from 1000 to 0 after restoring. This tolerance value does not appear in the output of the show guest-lan < wlan-id > command. |
|
Symptom : During high availability on 5508 controller, the active controller crashes with Task Name: rsyncmgrXferMain. Conditions : High availability on 5508 and release 7.6.101.7. |
|
Symptom : Mismatch of application traffic statistics with the Top Access Points and Top Client Devices data in the new dashboard on a 2500 controller with Cisco WLAN Express Setup. |
|
Symptom : Small mismatch of application traffic statistics with the Top Access Points and Top Client Devices data in the new dashboard on a 2500 controller with Cisco WLAN Express Setup. |
|
Symptom : Unable to enable AVC with bootloader older than 1.8.0.0. |
|
Symptom : Login window pops up twice in some instances for 2500 controller with Cisco WLAN Express Setup. None. Provide same login credentials for both login requests. |
|
Symptom : Cisco WLCs using Release 4.2.130.181M (mesh) stop responding with Task Name: reaperWatcher. Conditions : Multiple Cisco WiSMs using Release 4.2.130.181M with numerous Cisco AP1510s associated. Workaround : If such a behavior and subsequent issue occurs in any deployment, use the following command to disable the dynamic CAC tree updates: To return the CAC tree to normal behavior, use the following command: Further Problem Description : At present, the issue appears to be due to a problem with the dynamic building of the mesh CAC tree. The issue is present even when CAC is not enabled for voice or video. |
|
Symptom : CAPWAP data tunnel gets stuck when DTLS encryption enabled in Cisco Aironet 2600/3600. Conditions : Occurs in the following scenario:
Further Description: Data encryption is enabled to leverage data keep-alive and re-establish the CAPWAP tunnel in case the NAT/PAT translation expires, but in some cases the keep-alives are lost and the tunnel stays down which means there is no self-recovery; while the controller displays the CAPWAP control tunnel and access points in UP state and access points are connected FlexConnect. However, when clients try to connect they are de-authenticated while re-association due to a timeout. This happens because the AP does not receive a reassociation response from the controller. The following error is displayed in the access point logs every minute: |
|
Symptom : In Cisco Aironet Access Points 1130 series, FlexConnect VLAN mapping is corrupted when a change in VLAN mapping occurs. Conditions : This issue occurs when you use:
Workaround : Reload the access points to reinstall the new VLAN mapping configuration. |
|
Symptom : Access to the controller CLI and Web UI is lost when service port is disconnected. However, the client authentication and DHCP still works and both clients and access points are connected to the controller. Conditions : This issue occurs on a virtual Cisco Wireless LAN Controller with software release 7.6.100.0. |
|
Symptom : Flex AP bridge virtual interface (BVI) goes down while mapping to a VLAN. Conditions : This issue occurs because:
Workaround : You can tag the management VLAN in the controller with the VLAN identifier. |
|
Symptom : Access point sends deauthentication frames to new-channel after a channel change occurs due to Radar detection. Conditions : This issue occurs in Cisco Aironet Access Points Series 5508 with a software release 7.6.100.0 when: |
|
Symptom : Access points are unable to join the Cisco Wireless LAN Controller with software release 7.3 due to a stale entry on the controller. |
|
Symptom : Controller continuously displays messages of detected MFP anomaly. Conditions : This issue occurs in Cisco Flex Access Points Series 7500 with software release 7.6 or 7.5 when:
Workaround : You must use a software release prior to 7.6 or 7.5. |
|
Symptom : Unable to disable MFP traps when the clients are in power save mode or in busy environments. Hence, the logs are accumulated with trap entries. |
|
Symptom : After upgrade to controller software release 7.2.111.3, the accounting messages sent to the Radius server from the controller listed the clients as Remote, irrespective of where the clients were authenticated. |
|
Symptom : When a Change Of Authentication disconnect request is sent from the RADIUS server, the controller refuses to acknowledge attributes for user session disconnect request. |
|
Symptom : Issues in guest tunneling while working with Cisco WLC controller 5508 as mobility controller and guest controller. |
|
Symptom : CCKM roaming failing between a controller with software release 7.0 and a 7.4. |
|
Symptom : Rogue APs are mistaken as infrastructure devices. Thus, the wIPS alarms such sa deauthentication spoofed MAC address are falsely triggered later. Conditions : Rogue devices that are not associated with Cisco AP send data packet such as data null to Cisco AP. This causes wIPS to falsely recognize rogue devices as part of infrastructure devices. |
|
Symptom : Channel information is not displayed when the triggering frame contains channel 0 in radio header in access points for wIPS alarms. |
|
Symptom : Wireless clients on the controller (both in CLI and Web UI) interface indicates that the WMM is disabled and that no data rates are supported when Local Authentication is enabled. Conditions : FlexConnect Local Authentication is enabled. Workaround : Verify the actual client status using the show capwap reap association command. |
|
Symptom : Lightweight Cisco AP might not send out deauthentication messages to an existing client before 802.11 radio interface reset by RLDP although debug dot11 mgmt message command outputs indicate the messages are sent out. |
|
Symptom : A Cisco WLC might stop working, displaying a variety of symptoms such as the following:
pc = 0x122e7cec (license_xos_thread_create+2139596), ra = 0x122f630c (license_xos_thread_create+2139596)
Reaper Reset: Task "PMIPV6 Thread" taking too much cpu: 100%, (user 84%, system 15%) while SW Watchdog is disabled
Conditions : Cisco WLC is using Release 7.6.120.0; web-auth is in use. Workaround : None, other than disabling web-auth or anchoring to Cisco WLC that does not use Release 7.6.120.0. Further Problem Description : This issue is a regression caused by the commit of the fix for CSCuc68995 in Release 7.6.120.0. |
Table 9 lists the caveats that have been resolved in Release 7.6.120.0.
This section contains important information to keep in mind when installing Cisco WLCs and access points.
Warning This warning 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
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030
Warning Do not locate the antenna near overhead power lines or other electric light or power circuits, or where it can come into contact with such circuits. When installing the antenna, take extreme care not to come into contact with such circuits, as they may cause serious injury or death. For proper installation and grounding of the antenna, please refer to national and local codes (e.g. U.S.: NFPA 70, National Electrical Code, Article 810, Canada: Canadian Electrical Code, Section 54). Statement 280
Warning This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240 VAC, 10A international) is used on the phase conductors (all current-carrying conductors). Statement 13
Warning This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the absence of a suitably installed ground connector. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning Read the installation instructions before you connect the system to its power source. Statement 10
Warning Do not work on the system or connect or disconnect any cables (Ethernet, cable, or power) during periods of lightning activity. The possibility of serious physical injury exists if lightning should strike and travel through those cables. In addition, the equipment could be damaged by the higher levels of static electricity present in the atmosphere. Statement 276
Warning Do not operate the unit near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use. Statement 364
Warning In order to comply with radio frequency (RF) exposure limits, the antennas for this product should be positioned no less than 6.56 ft. (2 m) from your body or nearby persons. Statement 339
Warning This unit is intended for installation in restricted access areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security. Statement 1017
Follow the guidelines in this section to ensure proper operation and safe use of the Cisco WLCs and access points.
FCC Compliance with its action in ET Docket 96-8, has adopted a safety standard for human exposure to RF electromagnetic energy emitted by FCC-certified equipment. When used with approved Cisco Aironet antennas, Cisco Aironet products meet the uncontrolled environmental limits found in OET-65 and ANSI C95.1, 1991. Proper operation of this radio device according to the instructions in this publication results in user exposure substantially below the FCC recommended limits.
For your safety, and to help you achieve a good installation, read and follow these safety precautions. They might save your life!
1. If you are installing an antenna for the first time, for your own safety as well as others, seek professional assistance. Your Cisco sales representative can explain which mounting method to use for the size and type of antenna you are about to install.
2. Select your installation site with safety as well as performance in mind. Electric power lines and phone lines look alike. For your safety, assume that any overhead line can kill you.
3. Call your electric power company. Tell them your plans and ask them to come look at your proposed installation. This is a small inconvenience considering your life is at stake.
4. Plan your installation carefully and completely before you begin. Successfully raising a mast or tower is largely a matter of coordination. Each person should be assigned to a specific task and should know what to do and when to do it. One person should be in charge of the operation to issue instructions and watch for signs of trouble.
5. When installing an antenna, remember:
b. Do not work on a wet or windy day.
c. Do dress properly—shoes with rubber soles and heels, rubber gloves, long-sleeved shirt or jacket.
6. If the assembly starts to drop, get away from it and let it fall. Remember that the antenna, mast, cable, and metal guy wires are all excellent conductors of electrical current. Even the slightest touch of any of these parts to a power line completes an electrical path through the antenna and the installer: you!
7. If any part of an antenna system should come in contact with a power line, do not touch it or try to remove it yourself. Call your local power company. They will remove it safely.
8. If an accident should occur with the power lines, call for qualified emergency help immediately.
See the appropriate quick start guide or hardware installation guide for instructions on installing Cisco WLCs and access points.
Note To meet regulatory restrictions, all external antenna configurations must be installed by experts.
Personnel installing the Cisco WLCs and access points must understand wireless techniques and grounding methods. Access points with internal antennas can be installed by an experienced IT professional.
The Cisco WLC must be installed by a network administrator or qualified IT professional, and the proper country code must be selected. Following installation, access to the Cisco WLC should be password protected by the installer to maintain compliance with regulatory requirements and ensure proper unit functionality.
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at this URL:
http://www.cisco.com/c/en/us/support/index.html
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
For more information about the Cisco WLCs, lightweight access points, and mesh access points, see these documents:
You can access these documents at this URL: http://www.cisco.com/c/en/us/support/index.html
For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.