Table Of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.171.0
Contents
Cisco Unified Wireless Network Solution Components
Controller Requirements
Software Release Information
Finding the Software Release
Upgrading to a New Software Release
Special Rules for Upgrading to Controller Software Release 4.1.171.0
New and Changed Information
New Features
New Controller Module
New Controller Features
New CCXv4 and CCXv5 Features
New Location Features
New Mesh Features
GUI Enhancements
Other Changes
Installation Notes
Warnings
Safety Information
FCC Safety Compliance Statement
Safety Precautions
Installation Instructions
Important Notes
802.11n
CKIP Not Supported with Dynamic WEP
UNII-2 Channels Disabled on New 1000 Series Access Points for United States, Canada, and Philippines
FCC DFS Support on AP1130s
Pings Supported on the Controller
Access Point Radios Are Not Enabled After Upgrading to 4.1.171.0
Setting the Retransmit Timeout Value for TACACS+ Servers
Configuring an Access Point's Pre-Standard Power Setting
Using CCKM with CB21AG Client Adapters
DHCP Option 60 and 1500 Series Access Points
AP1000 and Radar Detection
Controller Functions that Require a Reboot
Multicast Queue Depth
2106 Controller LEDs
Resetting the Configuration on 2006 Controllers
Rate-Limiting on the Controller
IPSec Not Supported
4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel
Re-enable Broadcast after Upgrading to Release 4.0.206.0
Service Modules Supported in the Catalyst 6500 Series Switch
Connecting 1100 and 1300 Series Access Points
Joining Delay for 1500 Series Access Points
Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain
Preventing Clients from Accessing the Management Network on a Controller
Voice Wireless LAN Configuration
Operating Mesh Networks through Switches and Routers
Cisco 7920 Wireless IP Phone Support
Changing the IOS LWAPP Access Point Password
Exclusion List (Blacklist) Client Feature
RADIUS Servers and the Management VLAN
Cisco 1000 Series Access Points and WMM
Cisco Aironet 1030 Remote Edge Lightweight Access Points and WPA2-PSK
Lightweight Access Point Connection Limitations
RADIUS Servers
Management Usernames and Local Netuser Names
802.1x and Microsoft Wireless Configuration Manager
Using the Backup Image
Home Page Retains Web Authentication Login with IE 5.x
Rogue Location Discovery Protocol (RLDP)
Ad-Hoc Rogue Containment
Changing the Default Values of SNMP Community Strings
Changing the Default Values for SNMP v3 Users
Features Not Supported on 2000 and 2100 Series Controllers
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
Pinging from a Network Device to a Controller Dynamic Interface
2006 Image Not Supported for 3504 Controllers
Running a 3504 Image on a 2000 Series Controller
Upgrading External Web Authentication
Caveats
Open Caveats
Most Significant Open Caveats
Additional Open Caveats
Resolved Caveats
If You Need More Information
Troubleshooting
Documentation Updates
Omissions
Related Documentation
Obtaining Documentation, Support, and Security Guidelines
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.171.0
April 26, 2007
These release notes describe open and resolved caveats for software release 4.1.171.0 for Cisco 2000, 2100, and 4400 Series Wireless LAN Controllers; Cisco Wireless Services Modules (WiSM); Cisco Wireless LAN Controller Network Modules; Catalyst 3750G Integrated Wireless LAN Controller Switches; Cisco 3201 Wireless Mobile Interface Cards (WMICs); and Cisco Aironet 1000, 1100, 1130, 1200, 1240, 1300, and 1500 Series Lightweight Access Points, which comprise part of the Cisco Unified Wireless Network (UWN) Solution.
Note 
Unless otherwise noted, all of the Cisco wireless LAN controllers are hereafter referred to as controllers, and all of the Cisco lightweight access points are hereafter referred to as access points.
Contents
These release notes contain the following sections.
•Cisco Unified Wireless Network Solution Components
•Controller Requirements
•Software Release Information
•New and Changed Information
•Installation Notes
•Important Notes
•Caveats
•Troubleshooting
•Documentation Updates
•Related Documentation
•Obtaining Documentation, Support, and Security Guidelines
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•Software release 4.1.171.0 for all Cisco controllers and lightweight access points
•Cisco autonomous to lightweight mode upgrade tool release 2.01
•Cisco Wireless Control System (WCS) software release 4.1.83.0
•Cisco Wireless Control System (WCS) Navigator 1.0.83.0
•Location appliance software release 3.0.37.0
•Cisco 2700 Series Location Appliances
•Cisco 2000 Series Wireless LAN Controllers
•Cisco 2100 Series Wireless LAN Controllers
•Cisco 4400 Series Wireless LAN Controllers
•Cisco Wireless Services Module (WiSM) for Cisco Catalyst 6500 Series Switches
•Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers
•Catalyst 3750G Wireless LAN Controller Switches
•Cisco 3201 Wireless Mobile Interface Card (WMIC)
•Cisco Aironet 1000, 1100, 1130, 1200, 1240, 1300, and 1500 Series Lightweight Access Points
Controller Requirements
The controller graphical user interface (GUI) requires the following operating system and web browser:
•Windows XP SP1 or higher or Windows 2000 SP4 or higher
•Internet Explorer 6.0 SP1 or higher
Note Internet Explorer 6.0 SP1 or higher is the only browser supported for accessing the controller GUI and for using WebAuth.
Software Release Information
Software is factory installed on your controller and automatically downloaded to the access points after a release upgrade and whenever an access point joins a controller. As new releases become available for the controllers and their access points, consider upgrading.
Note The Cisco WiSM requires software release SWISMK9-32 or later. The Supervisor 720 12.2(18)SXF2 supports the Cisco WiSM software release 3.2.78.4 or above, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release 4.0.155.5 (with Cisco IOS Software Modularity).
Note The Cisco WiSM is supported on Cisco 7609 and 7613 Series Routers running only Cisco IOS Release 12.2(18)SXF5 or later.
Note The Cisco Wireless LAN Controller Network Module-Enhanced (WLCM-E) is supported on Cisco 28/37/38xx Series Integrated Services Routers running Cisco IOS Release 12.4(11)T2 or later.
Note To use the controller in the Catalyst 3750G Wireless LAN Controller Switch, the switch must be running Cisco IOS Release 12.2.25.FZ or 12.2(25)SEE.
Finding the Software Release
To find the software release running on your controller, look on the Monitor > Summary page of the controller GUI or enter show sysinfo on the controller command line interface (CLI).
Upgrading to a New Software Release
When you upgrade the controller's software, the software on the controller's associated access points is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.
Caution Do not power down the controller or any access point during this process; otherwise, you might corrupt the software image! Upgrading a controller with a large number of access points can take as long as 30 minutes, depending on the size of your network. However, with the increased number of concurrent access point upgrades supported in software release 4.0.206.0 and later, the upgrade time should be significantly reduced. The access points must remain powered, and the controller must not be reset during this time.
Special Rules for Upgrading to Controller Software Release 4.1.171.0
Caution Before upgrading your controller to software release 4.1.171.0, you must comply with the following rules.
•Controller software release 4.1.171.0 is greater than 32 MB; therefore, you must make sure that your TFTP server supports files that are larger than 32 MB. Some TFTP servers that support files of this size are tftpd and the TFTP server within the WCS. If you attempt to download the 4.1.171.0 controller software and your TFTP server does not support files of this size, the following error message appears: "TFTP failure while storing in flash."
•If your controller is running software release 3.2.195.10 or a later 3.2 release or 4.0.206.0 or a later 4.0 release, you can upgrade your controller directly to software release 4.1.171.0 If your controller is running an earlier 3.2 or 4.0 release, you must upgrade your controller to an intermediate release prior to upgrading to 4.1.171.0. Table 1 shows the upgrade path that you must follow prior to downloading software release 4.1.171.0.
Table 1 Upgrade Path to Controller Software Release 4.1.171.0
Current Software Release
|
Upgrade Path to 4.1.171.0 Software
|
3.2.78.0
|
Upgrade to 4.0.206.0 or a later 4.0 release before upgrading to 4.1.171.0.
|
3.2.116.21
|
3.2.150.10
|
3.2.171.6
|
3.2.193.5
|
If your controller is configured with the new J3 country code, upgrade to 3.2.195.10 or a later 3.2 release. If your controller is not configured for the new J3 country code, you can upgrade to 3.2.195.10 or a later 3.2 release or to 4.0.206.0 or a later 4.0 release.
|
3.2.195.10 or later 3.2 release
|
You can upgrade directly to 4.1.171.0.
|
4.0.155.5
|
Upgrade to 4.0.206.0 or a later 4.0 release before upgrading to 4.1.171.0.
|
4.0.179.11
|
4.0.206.0 or later 4.0 release
|
You can upgrade directly to 4.1.171.0.
|
Note When you upgrade the controller to an intermediate software release, wait until all of the access points joined to the controller are upgraded to the intermediate release before you install the 4.1.171.0 software. In large networks, it may take some time to download the software on each access point.
•Cisco recommends that you also install the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file on the controller. This file resolves bootloader defects and is necessary to ensure proper operation of the controller. The ER.aes file is required for the Cisco WiSM, Catalyst 3750G Wireless LAN Controller Switch, and 4400 series controllers.
Note The ER.aes files are independent from the controller software files. You can run any controller software file with any ER.aes file. However, installing the latest boot software file (4.1.171.0 ER.aes) ensures that the bootloader modifications in all of the previous and current boot software ER.aes files are installed.
Caution If you require a downgrade from one release to another, you may lose the configuration from your current release. The workaround is to reload the previous controller configuration files saved on the backup server or to reconfigure the controller.
Follow these steps to upgrade the controller software using the controller GUI.
Step 1 Upload your controller configuration files to a server to back them up.
Note Cisco highly recommends that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
Step 2 Disable the controller 802.11a and 802.11b/g networks.
Step 3 Disable any WLANs on the controller.
Step 4 Follow these steps to obtain the 4.1.171.0 controller software and the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file from the Software Center on Cisco.com:
a. Click this URL to go to the Software Center:
http://www.cisco.com/public/sw-center/sw-wireless.shtml
b. Click Wireless Software.
c. Click Wireless LAN Controllers.
d. Click Standalone Controllers, Wireless Integrated Routers, or Wireless Integrated Switches.
e. Click the name of a controller.
f. Click Wireless LAN Controller Software.
g. Click a controller software release.
h. Click the filename (filename.aes).
i. Click Download.
j. Read Cisco's End User Software License Agreement and then click Agree.
k. Save the file to your hard drive.
l. Repeat steps a. to k. to download the remaining file (either the 4.1.171.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file).
Step 5 Copy the controller software file (filename.aes) and the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file to the default directory on your TFTP server.
Step 6 Click Commands > Download File to open the Download File to Controller page.
Step 7 From the File Type drop-down box, choose Code.
Step 8 In the IP Address field, enter the IP address of the TFTP server.
Step 9 The default values of 10 retries and 6 seconds for the Maximum Retries and Timeout fields should work fine 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 field and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout field.
Step 10 In the File Path field, enter the directory path of the software.
Step 11 In the File Name field, enter the name of the software file (filename.aes).
Step 12 Click Download to download the software to the controller. A message appears indicating the status of the download.
Step 13 Repeat Step 6 to Step 12 to install the remaining file (either the 4.1.171.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file).
Step 14 After the download is complete, click Reboot.
Step 15 If prompted to save your changes, click Save and Reboot.
Step 16 Click OK to confirm your decision to reboot the controller.
Step 17 After the controller reboots, re-enable the WLANs.
Step 18 Re-enable your 802.11a and 802.11b/g networks.
Step 19 If desired, reload your latest configuration file to the controller.
Step 20 To verify that the 4.1.171.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.
Step 21 To verify that the Cisco Unified Wireless Network Controller Boot Software 4.1.171.0 ER.aes file is installed on your controller, enter the show sysinfo command on the controller CLI and look at the Bootloader Version field.
Note You can use this command to verify the boot software version on all controllers except the 2106. The Bootloader Version field remains at 4.0.190.0 for the 2106 controller, so you cannot tell which ER.aes file is installed.
New and Changed Information
New Features
The following new features are available in controller software release 4.1.171.0.
Note Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 4.1 for details and configuration instructions for each of these features.
New Controller Module
•Cisco Wireless LAN Controller Network Module-Enhanced (WLCM-E)—The enhanced controller network module within the Cisco 28/37/38xx Series Integrated Services Router can support up to 8 or 12 access points (and up to 256 or 350 clients, respectively). It supports these access points through a gigabit Ethernet distribution system port that connects the router and the integrated controller.
New Controller Features
•TACACS+ support—Terminal Access Controller Access Control System Plus (TACACS+) is a client/server protocol that provides centralized security for users attempting to gain management access to a controller. It provides authentication, authorization, and accounting (AAA) services.
•Local EAP—Local EAP is an authentication method that allows users and wireless clients to be authenticated locally. It is designed for use in remote offices that want to maintain connectivity to wireless clients when the backend system becomes disrupted or the external authentication server goes down. Local EAP retrieves user credentials from the local user database or the LDAP backend database to authenticate users. Local EAP supports LEAP, EAP-FAST with PACs, EAP-FAST with certificates, and EAP-TLS authentication between the controller and wireless clients.
Note Local EAP is designed as a backup authentication system. If any RADIUS servers are configured on the controller, the controller tries to authenticate the wireless clients using the RADIUS servers first. Local EAP is attempted only if no RADIUS servers are found, either because the RADIUS servers timed out or no RADIUS servers were configured.
•LDAP database support—You can configure a Lightweight Directory Access Protocol (LDAP) server as a backend database for use with local EAP. The controller queries the LDAP server for the credentials (username and password) of a particular user and uses them to authenticate the user.
Note The LDAP backend database supports only these local EAP methods: EAP-TLS and EAP-FAST with certificates. LEAP and EAP-FAST with protected access credentials (PACs) are not supported for use with the LDAP backend database.
•Access control list (ACL) enhancements—You can now apply an ACL to the controller central processing unit (CPU) or to a WLAN. An ACL is a set of rules used to limit access to a particular interface (for example, if you want to restrict a wireless client from pinging the management interface of the controller). After ACLs are configured on the controller, they can be applied to the management interface, the AP-manager interface, any of the dynamic interfaces, and now to a WLAN to control data traffic to and from wireless clients or to the controller CPU to control all traffic destined for the CPU.
•Load-based call admission control (CAC) for VoWLAN—This feature allows lightweight access points and controllers to consider three additional variables when deciding how many voice calls to allow on the network: the bandwidth used by all traffic types, co-channel access point loads, and co-located channel interference. The access point accounts for these three new variables when determining if there is sufficient bandwidth to support a new VoWLAN call. Previously, only bandwidth-based CAC was supported.
Note Load-based CAC is supported only on lightweight access points (except the Cisco Airespace 1000 series access points and the Cisco Aironet 1500 series access points, which support only bandwidth-based CAC). If you enable load-based CAC in a network that contains a mixture of AP1000s and other lightweight access points, the AP1000s use bandwidth-based CAC while the other lightweight access points used load-based CAC. If you disable load-based CAC, all of the access points start using bandwidth-based CAC.
•Symmetric mobility tunneling—Using this feature, a foreign controller now sends a Layer 3 roaming client's packet back to its anchor controller through EtherIP tunneling rather than through a dynamic interface. The source IP address of the packet then becomes the management IP address of the foreign controller, allowing upstream routers that have reverse path filtering (RPF) to forward packets rather than discard them because the source IP address of the non-tunneled packet does not match the router subnet.
•Guest N+1 redundancy and mobility failover—Mobility group members can now send ping requests to one another to check the data and control paths among them to find failed members and reroute clients. This functionality provides guest N+1 redundancy for guest tunneling and mobility failover for regular mobility. Guest N+1 redundancy allows detection of failed anchors. Once a failed anchor controller is detected, all of the clients anchored to this controller are deauthenticated so that they can quickly become anchored to another controller. This same functionality is also extended to regular mobility clients through mobility failover. This feature enables mobility group members to detect failed members and reroute clients.
•Workgroup bridge (WGB) support—Cisco Aironet autonomous access points operating in WGB mode can now associate to Cisco Aironet lightweight access points (except Cisco Airespace AP1000 series access points) to provide an 802.11 wireless connection to wired devices. The WGB is supported only in client mode and not in infrastructure mode and must run Cisco IOS Release 12.4(3g)JA or later (on 32-MB access points) or Cisco IOS Release 12.3(8)JEB or later (on 16-MB access points). WGB functionality is not supported for use with hybrid REAP.
The autonomous WGB access point learns the MAC address of the wired client and then informs the lightweight access point and controller that the device is operating on the wireless network. This scenario provides transparent bridging for wired clients and secure roaming.
•High-density networking—High-density networking is introduced in this software release through the exclusive Cisco and Intel Business Class Wireless Suite Version 2 collaboration. To optimize wireless LAN capacity and improve overall network performance in dense, multi-cell wireless networks, this release introduces high-density (or pico cell mode) parameters on the controller. Using these parameters, you can manually specify global values for receiver sensitivity threshold, clear channel assessment (CCA) sensitivity threshold, and transmit power values across all Cisco lightweight access points registered to a given controller. High-density networking is supported on all Cisco lightweight access points (except the wireless mesh access points) and on notebooks using the Intel PRO/Wireless 3945ABG and Intel Wireless WiFi Link 4965AG clients.
•Regulatory domain update for Japan—The Japanese regulations allow the regulatory domain that is programmed into an access point's radio to be migrated from the -J domain to the -U domain. New access points for the Japanese market contain radios that are configured for the -P regulatory domain. -J radios are no longer being sold. In order to make sure that your existing -J radios work together with the new -P radios in one network, you need to migrate your -J radios to the -U domain.
•Multiple country code support—This release allows you to configure up to 20 country codes per controller. This multiple-country support enables you to manage access points in various countries from a single controller. This feature is not supported for use with Cisco Aironet mesh access points.
•Dynamic frequency selection (DFS)—This release adds DFS functionality to the -A (U.S., Canada, and Philippines), -N (Mexico, Australia, Hong Kong, India, and New Zealand), and -T (Taiwan) regulatory domains. Prior to this release, DFS was already enabled for many other regulatory domains, including -E, -J, and -K . DFS is enabled automatically on the following Cisco lightweight access points that are configured for use in these regulatory domains: AP1130, AP1230, and AP1240. DFS affects channels 52 to 64 and 100 to 140 of the 802.11a radio. The access points use DFS to detect radar signals such as military and weather sources and then switch channels to avoid interfering with them.
Note FCC DFS is enabled only for AP1130s with a new FCC ID. Refer to the "FCC DFS Support on AP1130s" section for details.
•Addition of troubleshooting CLI commands—Four controller CLI commands have been added to this release to aid in gathering information and debugging issues: show process cpu, show process memory, show tech-support, and show running-config.
New CCXv4 and CCXv5 Features
•Client management frame protection (MFP)—Client MFP is now available for CCXv5 client devices. In the previous 4.0 software release, only infrastructure MFP, which protects 802.11 session management functions by adding message integrity check information elements (MIC IEs) to the management frames emitted by access points, was available. In this release, the new client MFP feature allows a client to detect a spoofed management frame at the first instance of an attack and generate an intrusion detection system (IDS) alert to the device interface.
•Expedited bandwidth requests—This feature enables CCXv5 clients to attach a priority to specific types of call requests, such as emergency 911 calls, or to specific devices that are tagged as high priority, such as a senior executive's call from an IP soft phone while on a business trip.
•Radio measurement requests enhancement—The radio measurement request feature has been expanded to enable the controller to obtain information on the radio environment from the client's perspective (rather than from just that of the access point). In this case, the access points issue unicast radio measurement requests to a particular CCXv4 client. The client then sends various measurement reports back to the access point and onto the controller. These reports include information on the radio environment and data used to interpret the location of the clients.
New Location Features
•Support for Cisco format RFID tags—The controller supports both Aeroscout format RFID tags and now Cisco format RFID tags. The Location Appliance uses the Location Protocol (LOCP) to receive chokepoint, battery status, vendor-specific, telemetry, and emergency information for Cisco format tags.
•Location enhancements—This release improves location accuracy by gathering received signal strength indicator (RSSI) measurements from access points all around the client of interest. This new controller CLI command enables you to view the current location configuration values: show advanced location summary.
New Mesh Features
•Mesh high-speed roaming—This release supports high-speed roaming of CCXv4-compliant clients at speeds up to 70 mph in outdoor mesh deployments. An example application might be maintaining communication with a terminal in an emergency vehicle as it moves within a mesh public network.
•Mesh background scanning—This feature allows Cisco Aironet 1505 and 1510 Access Points to actively and continuously monitor neighboring channels for more optimal paths and parents. Identifying this information prior to the loss of a parent results in a faster transfer and the best link possible for the access points.
•Routing around interference—You can configure a wireless secondary backhaul between two Cisco Aironet 1510 Access Points to provide a temporary path for traffic that cannot be sent on the primary backhaul due to intermittent interference. Traffic is automatically diverted, as necessary, packet by packet from the primary backhaul to the secondary backhaul.
•Backhaul client access—When this feature is enabled, Cisco Aironet 1510 Access Points allow wireless client association over the 802.11a radio. This implies that a 1510 access point may carry both backhaul traffic and 802.11a client traffic over the same 802.11a radio. When this feature is disabled, the AP1510 carries backhaul traffic over the 802.11a radio and allows client association only over the 802.11b/g radio.
•Mesh call admission control (CAC)—You can now configure bandwidth-based, or static, CAC on the controller to manage voice and video quality on the mesh network. This feature enables the client to specify how much bandwidth or shared medium time is required to accept a new call. Each access point determines whether it is capable of accommodating a particular call by looking at the bandwidth available and comparing it against the bandwidth required for the call. If there is not enough bandwidth available to maintain the maximum allowed number of calls with acceptable quality, the access point rejects the call.
Note For CAC to operate properly with mesh access points, enable bandwidth-based CAC on both the 802.11a and 802.11b/g radios. Also, make sure to keep load-based CAC disabled when using mesh CAC.
•Mesh security—You can now define the security mode for mesh access points: either Pre-Shared Key (PSK) or Extensible Authentication Protocol (EAP). Only local authentication is supported for EAP, and it is provided by the controller.
•Mesh statistics—You can now view mesh statistics and neighbor statistics for specific access points using the controller GUI or CLI.
GUI Enhancements
•802.3 bridging enhancement—You can now configure 802.3 bridging through the controller GUI. Previously, you could configure this feature only through the controller CLI. This feature enables the controller to support 802.3 frames and the applications that use them, such as those typically used for cash registers and cash register servers.
•Cisco Discovery Protocol (CDP) enhancement—You can now configure CDP through the controller GUI. Previously, you could configure this feature only through the controller CLI. CDP is a device discovery protocol that runs on all Cisco-manufactured equipment. A device enabled with CDP sends out periodic interface updates to a multicast address in order to make itself known to neighboring devices. You can enable CDP on both controllers and access points. In addition, you can view the CDP neighbors on all interfaces and for all access points connected to the controller.
•RM channel selection—You can now specify the channels that the dynamic channel allocation (DCA) algorithm considers when selecting the channels to be used for RRM scanning using the controller GUI. Previously, you could configure this feature only through the controller CLI.
Other Changes
These additional changes are applicable to controller software release 4.1.171.0:
•The Airespace AS1200 is not supported for use with controller software release 4.1.171.0. The Airespace AS1200 (not to be confused with the Cisco Aironet AP1200) was never sold by Cisco and predates Cisco's acquisition of Airespace. If you attempt to connect an Airespace AS1200 to a controller running this software, the access point reboots continuously.
•There is no deployment restriction on the number of hybrid-REAP access points per location. However, the minimum bandwidth restriction remains 128 kbps with the roundtrip latency no greater than 100 ms and the maximum transmission unit (MTU) no smaller than 500 bytes.
Installation Notes
This section contains important information to keep in mind when installing controllers and access points.
Warnings
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.
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Warning Do not locate any antenna near overhead power lines or other electric light or power circuits, or where it can come into contact with such circuits. When installing antennas, take extreme care not to come in contact with such circuits, as they may cause serious injury or death. For proper installation and grounding of the antenna, refer to national and local codes (e.g. U.S.: NFPA70, National Electrical Code, Article 810, in Canada: Canadian Electrical Code, Section 54).
Warning This product relies on the building's installation for short-circuit (overcurrent) protection. Ensure that the protective device is rated not greater than: 120 VAC, 15A U.S. (240vac, 10A International)
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.
Warning Read the installation instructions before you connect the system to its power source.
Warning Do not work on the system or connect or disconnect cables during periods of lightning activity.
Warning Do not operate your wireless network near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use.
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.
Warning This unit is intended for installation in restricted areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security.
Safety Information
Follow the guidelines in this section to ensure proper operation and safe use of the controllers and access points.
FCC Safety Compliance Statement
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.
Safety Precautions
Each year hundreds of people are killed or injured when attempting to install an antenna. In many of these cases, the victim was aware of the danger of electrocution but did not take adequate steps to avoid the hazard.
For your safety, and to help you achieve a good installation, read and follow these safety precautions. They may 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:
a. Do not use a metal ladder.
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.
Installation Instructions
Refer to the appropriate quick start guide or hardware installation guide for instructions on installing controllers and access points.
Note To meet regulatory restrictions, all external antenna configurations must be professionally installed.
Personnel installing the controllers and access points must understand wireless techniques and grounding methods. Access points with internal antennas can be installed by an experienced IT professional.
The controller must be installed by a network administrator or qualified IT professional, and the proper country code must be selected. Following installation, access to the controller should be password protected by the installer to maintain compliance with regulatory requirements and ensure proper unit functionality.
Important Notes
This section describes important information about the controllers and access points.
802.11n
802.11n radios are not supported for use with controller software release 4.1.171.0. These radios will be supported in a future controller release. In this release, please disregard any 802.11n-related parameters that appear on the controller GUI pages and any 802.11n-related controller CLI commands.
CKIP Not Supported with Dynamic WEP
In controller software release 4.1.171.0, CKIP is supported for use only with static WEP. It is not supported for use with dynamic WEP. Therefore, a wireless client that is configured to use CKIP with dynamic WEP is unable to associate to a wireless LAN that is configured for CKIP. Cisco recommends that you use either dynamic WEP without CKIP (which is less secure) or WPA/WPA2 with TKIP or AES (which are more secure).
UNII-2 Channels Disabled on New 1000 Series Access Points for United States, Canada, and Philippines
New Cisco 1000 series lightweight access points for the United States, Canada, and the Philippines do not support the UNII-2 band (5.25 to 5.35 GHz). These models are labeled AP10x0-B, where "B" represents a new regulatory domain that replaces the previous "A" domain.
FCC DFS Support on AP1130s
Federal Communications Commission (FCC) dynamic frequency selection (DFS) is supported only on AP1130s in the United States, Canada, and the Philippines that have a new FCC ID. Access points use DFS to detect radar signals such as military and weather sources and then switch channels to avoid interfering with them. AP1130s with FCC DFS support have an FCC ID "LDK102054E" sticker. AP1130s without FCC DFS support have an "LDK102054" (no "E" suffix) sticker. AP1130s that are operating in the United States, Canada, or the Philippines; have an FCC ID "E" sticker; and are running the 4.1.171.0 software release can use channels 100 through 140 in the UNII-2 band.
Pings Supported on the Controller
Controller software release 4.1.171.0 is designed to support ICMP pings to the management interface either from a wireless client or a wired host. ICMP pings to other interfaces configured on the controller are not supported.
Access Point Radios Are Not Enabled After Upgrading to 4.1.171.0
After you upgrade the controller in the Catalyst 3750G Wireless LAN Controller Switch to software release 4.1.171.0, the access point radios are not enabled. This issue occurs because the switch is not correctly recognizing the access points. To work around this issue, uncheck the CDP State check box on the AP Configuration > CDP Template page.
Setting the Retransmit Timeout Value for TACACS+ Servers
Cisco recommends that the retransmit timeout value for TACACS+ authentication, authorization, and accounting servers be increased if you experience repeated reauthentication attempts or the controller falls back to the backup server when the primary server is active and reachable. The default retransmit timeout value is 2 seconds and can be increased to a maximum of 30 seconds.
Configuring an Access Point's Pre-Standard Power Setting
An access point can be powered by a Cisco pre-standard 15-watt switch with power over Ethernet (PoE) by entering this command:
config ap power pre-standard {enable | disable} {all | Cisco_AP}
A Cisco pre-standard 15-watt switch does not support intelligent power management (IPM) but does have sufficient power for a standard access point. The following Cisco pre-standard 15-watt switches are available:
•AIR-WLC2106-K9
•WS-C3550, WS-C3560, WS-C3750
•C1880
•2600, 2610, 2611, 2621, 2650, 2651
•2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691
•2811, 2821, 2851
•3631-telco, 3620, 3640, 3660
•3725, 3745
•3825, 3845
The enable version of this command is required for full functionality when the access point is powered by a Cisco pre-standard 15-watt switch. It is safe to use if the access point is powered by either an IPM switch or a power injector or if the access point is not using one of the 15-watt switches listed above.
You may need this command if your radio operational status is "Down" when you expect it to be "Up." Enter the show msglog command to look for this error message, which indicates a PoE problem:
Apr 13 09:08:24.986 spam_lrad.c:2262 LWAPP-3-MSGTAG041: AP 00:14:f1:af:f3:40 is unable to
verify sufficient in-line power. Radio slot 0 disabled.
Using CCKM with CB21AG Client Adapters
Cisco Aironet CB21AG client adapters support only this CCKM configuration setting: WPA + TKIP + authentication key management CCKM.
DHCP Option 60 and 1500 Series Access Points
The VCI string for DHCP option 60 on 1500 series access point changes to "Cisco AP c1500" after the access points are upgraded to controller software release 4.1.171.0
AP1000 and Radar Detection
The AP1000 performs radar detection on channels that do not require it (such as channel 36). If the access point detects radar on these channels, the controller captures it in log messages.
Controller Functions that Require a Reboot
After you perform these functions on the controller, you must reboot the controller in order for them to take effect:
•Switch between Layer 2 and Layer 3 LWAPP mode
•Enable or disable link aggregation (LAG)
•Enable a feature that is dependent on certificates (such as HTTPS and web authentication)
•Enable or disable the mobility protocol port using this CLI command:
config mobility secure-mode {enable | disable}
Multicast Queue Depth
The multicast queue depth is 512 packets on all controller platforms. However, the following message may appear on 2006 controllers: "CPU Receive Multicast Queue is full on Controller." This message does not appear on 4400 series controllers because the 4400 NPU filters ARP packets while all forwarding (multicast or otherwise) and multicast replication are done in the software on the 2006.
2106 Controller LEDs
The 2106 controller's Status LED and AP LED do not flash amber when software is being uploaded to the controller or downloaded to an access point, respectively.
Note Some versions of the Cisco 2106 Wireless LAN Controller Quick Start Guide may incorrectly state that these LEDs flash amber during a software upload or download.
Resetting the Configuration on 2006 Controllers
If you wish to reset the configuration to factory defaults on a 2006 controller, perform one of the following:
•From the controller GUI, click Commands > Reset to Factory Default > Reset.
•From the controller CLI (after system bootup and login), enter clear config. Then after the configuration has been cleared, enter reset system without saving the current configuration.
•From the controller console (after system bootup), enter Recover-Config from the User Name prompt.
Caution Do not attempt to reset the controller's configuration by choosing Option 5, Clear Config from the boot menu unless you have successfully upgraded to the ER.aes image on Cisco.com.
Rate-Limiting on the Controller
Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired). Cisco recommends that you always run the controller with the default config advanced rate enable command in effect in order to rate-limit traffic to the controller and protect against denial-of-service (DoS) attacks. You can use the config advanced rate disable command to stop rate-limiting of Internet Control Message Protocol (ICMP) echo responses for testing purposes. However, Cisco recommends that you reapply the config advanced rate enable command after testing is complete.
IPSec Not Supported
Software release 4.1.171.0 does not allow you to choose IPSec as a Layer 3 Security option. None and VPN Passthrough are the only available options. If you upgrade to this release from a previous release that supported IPSec as a Layer 3 Security option, any WLANs that are configured for this feature become disabled. If you want to configure IPSec, you must use a version of controller software prior to 3.2 or wait for a future release.
4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel
As designed, 4400 series controllers do not forward IP subnet broadcasts from the wired network to wireless clients across the EoIP guest tunnel.
Re-enable Broadcast after Upgrading to Release 4.0.206.0
In software releases 4.0.179.0 and earlier, broadcast and multicast forwarding were both controlled with a single global flag that enabled multicast. Beginning with software release 4.0.206.0, these functions were broken into separate configuration flags: one that controls broadcast and one that controls non-broadcast multicast. If you have multicast enabled in software releases 4.0.179.0 and earlier, the broadcast flag is left disabled after upgrading to software release 4.0.206.0. As a result, some applications that rely on broadcast do not work after the upgrade.
After you upgrade to software release 4.0.206.0, use this CLI command to re-enable broadcast:
config network broadcast enable
When re-enabled, broadcast uses the multicast mode configured on the controller.
Service Modules Supported in the Catalyst 6500 Series Switch
The Catalyst 6500 Series Switch chassis can support up to five Cisco WiSMs without any other service module installed. If one or more service modules are installed, the chassis can support up to a maximum of four service modules (WiSMs included).
Connecting 1100 and 1300 Series Access Points
You must install software release 4.0.179.8 or later on the controller before connecting 1100 and 1300 series access points to the controller.
Joining Delay for 1500 Series Access Points
The 1500 series access points may take up to 10 minutes to fully join the controller on initial startup.
Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain
To support access points configured for use in Japan, you must upgrade the controller software to release 3.2.116.21 or later. Earlier releases do not support access points configured for use in Japan (regulatory domain -P).
Preventing Clients from Accessing the Management Network on a Controller
To prevent or block a wired or wireless client from accessing the management network on a controller (from the wireless client dynamic interface or VLAN), the network administrator should ensure that there is no route through which to reach the controller from the dynamic interface or use a firewall between the client dynamic interface and the management network.
Voice Wireless LAN Configuration
Cisco recommends that aggressive load balancing always be turned off either through the controller GUI or CLI in any wireless network that is supporting voice, regardless of vendor. When aggressive load balancing is turned on, voice clients can hear an audible artifact when roaming, and the handset is refused at its first reassociation attempt.
Operating Mesh Networks through Switches and Routers
In mesh networks that operate through switches and routers, network round-trip delays between access points and the controller must be less than 100 milliseconds (ms); otherwise, timing problems may occur during wireless client authentication. Also, network path outages of 60 seconds between access points and the controller may cause the access points to lose connectivity.
Cisco 7920 Wireless IP Phone Support
When using Cisco 7920 Wireless IP Phones with controllers, make sure that the phones and controllers are configured as follows:
•Aggressive load balancing must be disabled for each controller. Otherwise, the initial roam attempt by the phone may fail, causing a disruption in the audio path.
•The QoS Basis Service Set (QBSS) information element (IE) must be enabled. The QBSS IE enables the access points to communicate their channel usage to wireless devices. Because access points with high channel usage might not be able to handle real-time traffic effectively, the 7920 phone uses the QBSS value to determine if they should associate with another access point. Use the following commands to enable the QBSS IE:
–sh wlan summary
Note Use this command to determine the WLAN ID number of the WLAN to which you want to add QBSS support.
–config wlan disable wlan_id_number
–config wlan 7920-support ap-cac-limit enable wlan_id_number
–config wlan enable wlan_id_number
–sh wlan wlan_id_number
Note Use this command to verify that the WLAN is enabled and the Dot11-Phone Mode (7920) field is configured for compat mode.
–save config
•The Dynamic Transmit Power Control (DTPC) information element (IE) must be enabled using the config 802.11b dtpc enable command. The DTPC IE is a beacon and probe information element that allows the access point to broadcast information on its transmit power. The Cisco 7920 Wireless IP Phone uses this information to automatically adjust its transmit power to the same level as the access point to which it is associated. In this manner, both devices are transmitting at the same level.
•Both the 7920 phones and the controllers support Cisco Centralized Key Management (CCKM) fast roaming.
•When configuring WEP, there is a difference in nomenclature for the controller and the 7920 phone. Configure the controller for 104 bits when using 128-bit WEP for the 7920.
Changing the IOS LWAPP Access Point Password
Cisco IOS Lightweight Access Point Protocol (LWAPP) access points have a default password of Cisco, and the pre-stage configuration for LWAPP access points is disabled by default. To enable it, you must configure the access point with a new username and password when it joins the controller. Enter this command using the controller CLI to push a new username and password to the access point:
config ap username user_id password password {Cisco_AP | all}
•The Cisco_AP parameter configures the username and password on the specified access point.
•The all parameter configures the username and password on all the access points registered to the controller.
The password pushed from the controller is configured as "enable password" on the access point.
There are some cases where the pre-stage configuration for LWAPP access points is disabled and the access point displays the following error message when the CLI commands are applied:
"ERROR!!! Command is disabled."
For more information, refer to Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode.
Exclusion List (Blacklist) Client Feature
If a client is not able to connect to an access point, and the security policy for the WLAN and client are correct, the client has probably been disabled. In the controller GUI, you can view the client's status on the Monitor > Summary page under Client Summary. If the client is disabled, click Remove to clear the disabled state for that client. The client automatically comes back and, if necessary, reattempts authentication.
Automatic disabling happens as a result of too many failed authentications. Clients disabled due to failed authorization do not appear on the permanent disable display. This display is only for those MACs that are set as permanently disabled by the administrator.
RADIUS Servers and the Management VLAN
If a RADIUS server is on a directly connected subnet (with respect to the controller), then that subnet must be the management VLAN subnet.
Cisco 1000 Series Access Points and WMM
•In order to use Layer 2 LWAPP mode and WMM with a 1000 series access point, you must make sure that WMM is disabled.
•Clients cannot associate to an AP1030 in REAP mode if WMM is enabled on the WLAN. Disable WMM to allow the clients to associate.
Cisco Aironet 1030 Remote Edge Lightweight Access Points and WPA2-PSK
Cisco Aironet 1030 Remote Edge Lightweight Access Points do not support WPA2-PSK in REAP standalone mode.
Lightweight Access Point Connection Limitations
Cisco Aironet lightweight access points do not connect to the 4400 series controller if the date and time are not set properly. Set the current date and time on the controller before allowing the access points to connect to it.
RADIUS Servers
This product has been tested with the following RADIUS servers:
•CiscoSecure ACS 3.2, 3.3, and 4.0
•Steel-Belted RADIUS Enterprise edition v4.4.337
•IAS Windows 2003
Management Usernames and Local Netuser Names
Management usernames and local netuser names must be unique because they are stored in the same database. That is, you cannot assign the same name to a management user and a local netuser.
802.1x and Microsoft Wireless Configuration Manager
Clients using the Microsoft Wireless Configuration Manager and 802.1x must use WLANs configured for 40- or 104-bit key length. Configuring for 128-bit key length results in clients that can associate but not authenticate.
Using the Backup Image
The controller bootloader (ppcboot) stores a copy of the active primary image and the backup image. If the primary image becomes corrupted, you can use the bootloader to boot with the backup image.
With the backup image stored before rebooting, be sure to choose Option 4: Change Active Boot Image from the boot menu to set the backup image as the active boot image. Otherwise, when the controller resets, it again boots off the corrupted primary image.
After the controller boots, the active boot image can be changed to the backup image using the config boot backup command.
Home Page Retains Web Authentication Login with IE 5.x
Because of a caching problem in the Internet Explorer 5.x browser, the home page retains the web authentication login. To correct this problem, clear the history or upgrade your workstation to Internet Explorer 6.x.
Rogue Location Discovery Protocol (RLDP)
Enabling RLDP may cause access points connected to the controller to lose connectivity with their clients for up to 30 seconds.
Ad-Hoc Rogue Containment
Client card implementations may mitigate the effectiveness of ad-hoc containment.
Changing the Default Values of SNMP Community Strings
The controller has commonly known default values of "public" and "private" for the read-only and read-write SNMP community strings. Using these standard values presents a security risk. Therefore, Cisco strongly advises that you change these values. Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 4.1 for configuration instructions.
Changing the Default Values for SNMP v3 Users
The controller uses a default value of "default" for the username, authentication password, and privacy password for SNMP v3 users. Using these standard values presents a security risk. Therefore, Cisco strongly advises that you change these values. Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 4.1 for configuration instructions.
Note SNMP v3 is time sensitive. Make sure that you have configured the correct time and time zone on your controller.
Features Not Supported on 2000 and 2100 Series Controllers
These hardware features are not supported on 2000 and 2100 series controllers:
•Power over Ethernet (PoE) for 2000 series controllers only
Note Ports 7 and 8 on 2100 series controllers are PoE ports.
•Service port (separate out-of-band management 10/100-Mbps Ethernet interface)
These software features are not supported on 2000 and 2100 series controllers:
•VPN termination (such as IPSec and L2TP)
•Termination of guest controller tunnels (origination of guest controller tunnels is supported)
•External web authentication web server list
•Layer 2 LWAPP
•Spanning tree
•Port mirroring
•Cranite
•Fortress
•AppleTalk
•QoS per-user bandwidth contracts
•IPv6 pass-through
•Link aggregation (LAG)
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
In a crowded RF environment, clients may not be able to detect the desired SSID because of internal table limitations. Sometimes disabling and then enabling the client interface forces a rescan. Your RF environment needs to be controlled. Cisco UWN rogue access point detection and containment can help you to enforce RF policies in your buildings and campuses.
Pinging from a Network Device to a Controller Dynamic Interface
Pinging from a network device to a controller dynamic interface may not work in some configurations. When pinging does operate successfully, the controller places Internet Control Message Protocol (ICMP) traffic in a low-priority queue, and the reply to ping is on best effort. Pinging does not pose a security threat to the network. The controller rate limits any traffic to the CPU, and flooding the controller is prevented. Clients on the WLAN associated with the interface pass traffic normally.
2006 Image Not Supported for 3504 Controllers
The 2006 controller image is supported for use with only 2000 series controllers. Do not install the 2006 image on a 3504 controller. Otherwise, errors may occur. Install only the 3504 image on a 3504 controller.
Running a 3504 Image on a 2000 Series Controller
It is possible to run a 3504 controller image on a 2000 series controller, but Cisco Aironet 1130, 1200, and 1240 series access points will not be able to connect to the controller.
Upgrading External Web Authentication
When upgrading a controller from operating system release 2.0 or 2.2.127.4 to release 3.2.116.21 or later, update the external web authentication configuration as follows:
1. Instead of using a preauthentication ACL, the network manager must configure the external web server IP address using this command:
config custom-web ext-webserver add index IP-address
Note IP-address is the address of any web server that performs external web authentication.
2. The network manager must use the new login_template shown here:
Note Make sure to format the script to avoid any extra characters or spaces before using the web authentication template.
<meta http-equiv="Pragma" content="no-cache"> <meta HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=iso-8859-1"> <title>Web Authentication</title> <script>
var link = document.location.href;
var searchString = "redirect=";
var equalIndex = link.indexOf(searchString);
equalIndex += searchString.length;
urlStr = link.substring(equalIndex);
if(redirectUrl.length > 255)
redirectUrl = redirectUrl.substring(0,255);
document.forms[0].redirect_url.value = redirectUrl;
