Cisco 4400 Series Wireless LAN Controllers

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release

  • Viewing Options

  • PDF (465.8 KB)
  • Feedback
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release

Table Of Contents

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release


Cisco Unified Wireless Network Solution Components

Special Notice for Mesh Networks

Controller Requirements

Software Release Information

Finding the Software Release

Upgrading to a New Software Release

Special Rules for Upgrading to Controller Software Release

Installation Notes


Safety Information

FCC Safety Compliance Statement

Safety Precautions

Installation Instructions

Important Notes

One-Time Password (OTP) Support

QoS Interaction with RRM

Crash Files for 1250 Series Access Points

Port Mirroring Not Supported on Some Controller Platforms

Internal DHCP Server

RLDP Limitations

Configuration File Stored in XML Format

Web Authentication Redirects

Disabling Radio Bands

40-MHz Channels in the 2.4-GHz Band

Impact of External Antenna Gain on Transmit Power

Supporting Oversized Access Point Images

Cisco 1250 Series Access Points and Cisco 7920 IP Phones

Multicast Limitations

MAC Filtering for WGB Wired Clients

CKIP Not Supported with Dynamic WEP

Synchronizing the Controller and Location Appliance

UNII-2 Channels Disabled on New 1000 Series Access Points for United States, Canada, and Philippines

FCC DFS Support on 1130 Series Access Points

Inaccurate Transmit Power Display

Setting the Retransmit Timeout Value for TACACS+ Servers

Configuring an Access Point's Prestandard Power Setting

1000 Series Access Points 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

Pings Supported to the Management Interface of the Controller

Pinging from a Network Device to a Controller Dynamic Interface

GLBP Not Supported

IPSec Not Supported

4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel

Connecting 1100 and 1300 Series Access Points

Preventing Clients from Accessing the Management Network on a Controller

Voice Wireless LAN Configuration

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

2006 Image Not Supported for 3504 Controllers

Running a 3504 Image on a 2000 Series Controller

Upgrading External Web Authentication


Open Caveats

Major Open Caveats

Moderate Open Caveats

Minor Open Caveats

Resolved Caveats

If You Need More Information


Documentation Updates


Related Documentation

Obtaining Documentation, Support, and Security Guidelines

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release

July 24, 2009

These release notes describe open and resolved caveats for software release 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, 1230AG, 1240, 1250, and 1300 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.


These release notes contain the following sections.

Cisco Unified Wireless Network Solution Components

Controller Requirements

Software Release Information

Installation Notes

Important Notes



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 for all Cisco controllers and lightweight access points

Cisco autonomous to lightweight mode upgrade tool release 3.0

Cisco Wireless Control System (WCS) software release, 5.2, or 6.0

Note Only Cisco WCS, 5.2, and 6.0 support controllers running software release

Cisco WCS Navigator

Location appliance software release

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 and Cisco 7600 Series Routers

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, 1230AG, 1240, 1250, and 1300 Series Lightweight Access Points

Note Only Cisco Aironet 1200 Series Access Points that contain 802.11g (AIR-MP21G) or second-generation 802.11a radios (AIR-RM21A or AIR-RM22A) are supported for use with controller software releases. The AIR-RM20A radio, which was included in early 1200 series access point models, is not supported. To see the type of radio module installed in your access point, enter this command on the access point: show controller dot11radio n, where n is the number of the radio (0 or 1).

Note The 1250 series access points have a hardware limitation where beacons can only be output at intervals that are multiples of 17 milliseconds. When these APs are configured for a 100-millisecond beacon interval, they transmit beacons every 102 milliseconds. Similarly, when the beacon interval is configured for 20 milliseconds, these APs transmit beacons every 17 milliseconds.

Special Notice for Mesh Networks

Note Do not upgrade to controller software release if you have mesh access points in your network. If your network uses mesh access points, use only mesh-specific releases. These releases are labeled MESH in the Software Center.

Note Cisco WCS software release may be used to manage both mesh and non-mesh controllers (such as controllers running software release and You do not need different instances of WCS to manage mesh and non-mesh controllers.

Controller Requirements

The controller 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 web authentication.

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 or later, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release (with Cisco IOS Software Modularity).

Note To use the Cisco WiSM in the Cisco 7609 and 7613 Series Routers, the routers must be running Cisco IOS Release 12.2(18)SXF5 or later.

Note The Cisco Wireless LAN Controller Network Module is supported on Cisco 28/37/38xx Series Integrated Services Routers running Cisco IOS Release 12.4(11)T2, 12.4(11)T3, and 12.5.

Note When you use the controller in the Catalyst 3750G Wireless LAN Controller Switch, the 3750 should not run Cisco IOS Releases 12.2(44)SE2 and 12.2(46)SE due to defect CSCsu02630.

Finding the Software Release

To find the software release running on your controller, click Monitor and look at the Software Version field under Controller Summary on the controller GUI or enter show sysinfo on the controller 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. Up to 10 access points can be concurrently upgraded from the controller.

Note When you downgrade from to or an earlier release, the LWAPP mode may or may not change from Layer 3 to Layer 2, depending on whether the configuration was saved in the earlier image. If the LWAPP mode changes, access points may not join the controller, and you must manually reset the controller to Layer 3 to resolve this issue.

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 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

Caution Before upgrading your controller to software release, you must comply with the following rules.

Make sure you have a TFTP server available for the software upgrade. Keep these guidelines in mind when setting up a TFTP server:

Controller software release is larger 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 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 you are upgrading through the service port, the TFTP server must be on the same subnet as the service port because the service port is not routable, or you must create static routes on the controller.

If you are upgrading through the distribution system network port, the TFTP server can be on the same or a different subnet because the distribution system port is routable.

A third-party TFTP server cannot run on the same computer as the WCS because the WCS built-in TFTP server and the third-party TFTP server require the same communication port.

If your controller is running software release (or a later 4.0 release), (or a later 4.1 release), or,,, or, you can upgrade your controller directly to software release If your controller is running a 3.2 release or a 4.0 release prior to, you must upgrade your controller to an intermediate release prior to upgrading to Table 1 shows the upgrade path that you must follow before downloading software release

Table 1 Upgrade Path to Controller Software Release

Current Software Release
Upgrade Path to Software or later 3.2 release

Upgrade to (or a later 4.0 release) before upgrading to

Upgrade to (or a later 4.0 release) before upgrading to or later 4.0 release

You can upgrade directly to or later 4.1 release

You can upgrade directly to or later 4.2 release

You can upgrade directly to

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 software. In large networks, it can take some time to download the software on each access point.

Cisco requires you to install the Cisco Unified Wireless Network Controller Boot Software ER.aes file on the following controllers: 4400 series, Cisco WiSM, and Catalyst 3750G Wireless LAN Controller Switch. It is optional on other controller platforms. This file resolves CSCso00774 and is necessary to ensure proper operation of the controller. If you do not install the ER.aes file, your controller does not obtain the fix for this defect, and "Error" appears in the Bootloader Version field in the output of the show sysinfo command.

Note When you install the ER.aes file, a new bootloader file is also loaded. This is true for all controllers except the 2106 controller, for which the bootloader is not upgradable.

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 ( ER.aes) ensures that the boot software 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.

Note Do not install the controller software file and the ER.aes boot software file at the same time. Install one file and reboot the controller; then install the other file and reboot 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 Follow these steps to obtain the controller software and the Cisco Unified Wireless Network Controller Boot Software ER.aes file from the Software Center on

a. Click this URL to go to the Software Center:

b. Click Wireless Software.

c. Click Wireless LAN Controllers.

d. Click Standalone Controllers or Integrated Controllers and Controller Modules.

e. Click a controller series.

f. If necessary, click a controller model.

g. If you chose Standalone Controllers in Step d., click Wireless LAN Controller Software.

h. If you chose Cisco Catalyst 6500 Series/7600 Series Wireless Services Module (WiSM) in Step e., click Wireless Services Modules (WiSM) Software.

i. Click a controller software release. The software releases are labeled as follows to help you determine which release to download:

Early Deployment (ED)—These software releases provide new features and new hardware platform support as well as bug fixes.

Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.

Deferred (DF)—These software releases have been deferred. Cisco recommends that you migrate to an upgraded release.

j. Click a software release number.

k. Click the filename (filename.aes).

l. Click Download.

m. Read Cisco's End User Software License Agreement and then click Agree.

n. Save the file to your hard drive.

o. Repeat Steps a. to n. to download the remaining file (either the controller software or the Cisco Unified Wireless Network Controller Boot Software ER.aes file).

Step 3 Copy the controller software file (filename.aes) and the Cisco Unified Wireless Network Controller Boot Software ER.aes file to the default directory on your TFTP server.

Step 4 Click Commands > Download File to open the Download File to Controller page.

Step 5 From the File Type drop-down box, choose Code.

Step 6 In the IP Address field, enter the IP address of the TFTP server.

Step 7 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 8 In the File Path field, enter the directory path of the software.

Step 9 In the File Name field, enter the name of the software file (filename.aes).

Step 10 Click Download to download the software to the controller. A message appears indicating the status of the download.

Step 11 Repeat Step 4 to Step 10 to install the remaining file (either the controller software or the Cisco Unified Wireless Network Controller Boot Software ER.aes file).

Step 12 After the download is complete, click Reboot.

Step 13 If prompted to save your changes, click Save and Reboot.

Step 14 Click OK to confirm your decision to reboot the controller.

Step 15 If desired, reload your latest configuration file to the controller.

Step 16 To verify that the controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.

Step 17 To verify that the Cisco Unified Wireless Network Controller Boot Software ER.aes file is installed on your controller, enter the show sysinfo command on the controller CLI and look at the Bootloader Version field. "N/A" appears if the ER.aes file is installed successfully. "Error" appears if the ER.aes file is not installed.

Note You can use this command to verify the boot software version on all controllers except the 2106 because the bootloader is not upgradable on the 2106 controller.

Installation Notes

This section contains important information to keep in mind when installing controllers 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.

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.

One-Time Password (OTP) Support

One Time Passwords (OTP) are supported on the Wireless Lan Controller (WLC) using TACACS and RADIUS. In this configuration, the controller acts as a transparent pass-thru device. The controller forwards all client requests to the TACACS/RADIUS server without inspecting the client behavior. When using OTP the client must only establish a single connection to the controller to function properly. The controller currently does not have any intelligence or checks to correct a client that is trying to establish multiple connections.

QoS Interaction with RRM

Controller software release or later affects the way that QoS interacts with the RRM scan defer feature:

When you configure a WLAN with a Bronze (Background Priority) QoS policy level, traffic with Scan Defer Priority 0 (UP=0) should be downgraded to UP=1 (UP 1,2 are the lowest priority; 0,3 are the next higher priority). Traffic to and from clients on this WLAN will compete with clients sending UP=0 traffic in Silver/Gold/Platinum policies.

The QoS policy for the WLAN configuration overrides the traffic sent. In other words, if you have patient monitors, phones, or other client devices in a WLAN with a Silver QoS policy, the traffic is downgraded to a priority no higher than UP=3. If you attempt to defer off-channel scanning by configuring the WLAN for UP=5, the QoS policy overrides that configuration and off-channel scanning is not deferred.

Traffic sent with UP=7 on a WLAN with a Platinum policy will be downgraded to UP=6; if you configure off-channel scanning for UP=7 only, scanning will not be deferred. You might not want to defer scanning for UP=7 traffic but you might for UP=6 traffic; in this case, the traffic sent with UP=7 will be downgraded and cause a deferral. Similarly, if you want to defer scanning for UP=7 traffic, you must set the scanning priority to UP=6 because the traffic will be downgraded.

If you completely disable off-channel scanning on your network, you should consider alternative ways to implement off-channel scanning: adding monitor-mode access points or creating AP groups where some access points in the area do not carry the configured WLANs for those devices.

Crash Files for 1250 Series Access Points

The 1250 series access points may contain a bootloader older than version 12.4(10b)JA. Units with old bootloaders do not generate a crash log when a crash occurs. The crash log is disabled so that a crash does not corrupt the flash file system. Units with bootloader versions 12.4(10b)JA or later generate a crash log if the access point is associated to a controller software release or later.

New 1250 series access points shipped from the factory contain new bootloader images, which fixes the flash file system after it is corrupted during a crash (without losing files). This new bootloader automatically sets a new CRASH_LOG environment variable to "yes," which enables a crash log to be generated following a crash but only on controllers running software release or later. Therefore, no user configuration is needed to enable a crash log on new 1250 series access points shipped from the factory.

These examples show the output from the CLI commands (in bold) that you use to check the bootloader version on LWAPP and autonomous 1250 series access points:

LWAPP (commands entered on the controller CLI):

(wlc) >debug ap enable AP001b.d513.1754
(wlc) >debug ap command "show version | include BOOTLDR" AP001b.d513.1754
(wlc) >Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader 
(C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)

Autonomous (command entered on the access point CLI):

ap# show version | include BOOTLDR
BOOTLDR: C1250 Boot Loader (C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)

Port Mirroring Not Supported on Some Controller Platforms

The controller port mirroring feature is not supported on 2100 series controllers, 4400 series controllers, Cisco WiSM controllers, and controller network modules.

Internal DHCP Server

When clients use the controller's internal DHCP server, IP addresses are not preserved across reboots. As a result, multiple clients can be assigned the same IP address. To resolve any IP address conflicts, clients must release their existing IP address and request a new one.

RLDP Limitations

Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue access points that are connected to your wired network. RLDP operates with these limitations:

RLDP detects rogue access points that are configured for open authentication.

RLDP detects rogue AP which use a broadcast BSSID--that is, the access point broadcasts its SSID in beacons.

RLDP detects only rogue AP that are on the same the network. In other words, if an access list in the network prevents the sending of RLDP traffic from the rogue AP to the controller, RLDP will not work.

RLDP does not work on 5-GHz DFS channels.

RLDP is a best-effort protocol. For each rogue, the controller initiates RLDP only once. If the controller does not detect a rogue (due to a noisy RF environment, for example), the controller does not retry. However, you can initiate RLDP manually on a rogue at any time.

Configuration File Stored in XML Format

In controller software 4.2, the controller's bootup configuration file is stored in an Extensible Markup Language (XML) format rather than in binary format. Therefore, you cannot download a binary configuration file onto a controller running software release 4.2. However, when you upgrade a controller from a previous software release to 4.2, the configuration file is migrated and converted to XML.

Web Authentication Redirects

The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not support web authentication redirects to HTTPS (HTTP over SSL) servers.

Disabling Radio Bands

The controller disables the radio bands that are not permitted by the configured country of operation (CSCsi48220).

40-MHz Channels in the 2.4-GHz Band

Cisco recommends that you do not configure 40-MHz channels in the 2.4-GHz radio band because severe co-channel interference is likely to occur.

Impact of External Antenna Gain on Transmit Power

In controller software release 4.2 or later, external antenna gain is factored into the maximum transmit power of the access point. Therefore, when you upgrade from an earlier software release to 4.2 or later, you might see a decrease in transmit power output.

Supporting Oversized Access Point Images

Controller software release 4.2 or later allows you to upgrade to an oversized access point image by deleting the recovery image to create sufficient space. This feature affects only access points with 8 MB of flash (the 1100, 1200, and 1310 series access points). All newer access points have a larger flash size than 8 MB.

Note As of August 2007, there are no oversized access point images, but as new features are added, the access point image size will continue to grow.

The recovery image provides a backup image that can be used if an access point power-cycles during an image upgrade. The best way to avoid the need for access point recovery is to prevent an access point from power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized access point image, you can recover the access point using the TFTP recovery procedure.

Follow these steps to perform the TFTP recovery procedure.

Step 1 Download the required recovery image from (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx, or c1310-rcvk9w8-mx) and install it in the root directory of your TFTP server.

Step 2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access point boots from the TFTP image and then joins the controller to download the oversized access point image and complete the upgrade procedure.

Step 3 After the access point has been recovered, you may remove the TFTP server.

Cisco 1250 Series Access Points and Cisco 7920 IP Phones

Cisco 1250 series access points are not supported for use with the Cisco 7920 IP phone. They can, however, be used with the Cisco 7921 and 7925 IP phones.

Multicast Limitations

Multicast is not supported on access points that are connected directly to the local port of a 2000 or 2100 series controller.

MAC Filtering for WGB Wired Clients

Controller software release or later enables you to configure a MAC-filtering IP address for a workgroup bridge (WGB) wired client to allow passive WGB wired clients, such as terminal servers or printers with static IP addresses, to be added and remain in the controller's client table while the WGB is associated to a controller in the mobility group. This feature, activated by the config macfilter ipaddress MAC_address IP_address CLI command, can be used with any passive device that does not initiate any traffic but waits for another device to start communication.

This feature allows the controller to learn the IP address of a passive WGB wired client when the WGB sends an IAPP message to the controller that contains only the WGB wired client's MAC address. Upon receiving this message from the WGB, the controller checks the local MAC filter list (or the anchor controller's MAC filter list if the WGB has roamed) for the client's MAC address. If an entry is found and it contains an IP address for the client, the controller adds the client to the controller's client table.

Note Unlike the existing MAC filtering feature for wireless clients, you are not required to enable MAC filtering on the WLAN for WGB wired clients.

Note WGB wired clients using MAC filtering do not need to obtain an IP address through DHCP to be added to the controller's client table.

CKIP Not Supported with Dynamic WEP

In controller software release or later, 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).

Synchronizing the Controller and Location Appliance

For controller software release 4.2 or later, if a location appliance (release 3.1 or later) is installed on your network, the time zone must be set on the controller to ensure proper synchronization between the two systems. Also, Cisco highly recommends that the time be set for networks that do not have location appliances. Refer to Chapter 4 of the Cisco Wireless LAN Controller Configuration Guide, Release 4.2 for instructions for setting the time and date on the controller.

Note The time zone can be different for the controller and the location appliance, but the time zone delta must be configured accordingly, based on Greenwich Mean Time (GMT).

Note Daylight Savings Time (DST) is not supported in controller software release 4.2.

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 1130 Series Access Points

Federal Communications Commission (FCC) dynamic frequency selection (DFS) is supported only on 1130 series access points 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. 1130 series access points with FCC DFS support have an FCC ID LDK102054E sticker. 1130 series access points without FCC DFS support have an LDK102054 (no E suffix) sticker. 1130 series access points that are operating in the United States, Canada, or the Philippines; have an FCC ID E sticker; and are running the software release or later can use channels 100 through 140 in the UNII-2 band.

Inaccurate Transmit Power Display

After you change the position of the 802.11a radio antenna for a lightweight 1200 or 1230 series access point, the power setting is not updated in the controller GUI and CLI. Regardless of the user display, the internal data is updated, and the transmit power output is changed accordingly. To see the correct transmit power display values, reboot the access point after changing the antenna's position. (CSCsf02280)

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 Prestandard Power Setting

An access point can be powered by a Cisco prestandard 15-watt switch with Power over Ethernet (PoE) by entering this command:

config ap power pre-standard {enable | disable} {all | Cisco_AP}

A Cisco prestandard 15-watt switch does not support intelligent power management (IPM) but does have sufficient power for a standard access point. The following Cisco prestandard 15-watt switches are available:


WS-C3550, WS-C3560, WS-C3750


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 prestandard 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 might 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.

1000 Series Access Points and Radar Detection

The 1000 series access points perform radar detection on channels that do not require it (such as channel 36). If the access points detect 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)

Add new or modify existing SNMP v3 users

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 might appear on 2006 and 2106 controllers: "Rx Multicast Queue is full on Controller." This message does not appear on 4400 series controllers because the 4400 NPU filters ARP packets, and all forwarding (multicast or otherwise) and multicast replication are done in the software on the 2006 and 2106.

This message appears when too many multicast messages are sent to the CPU. In controller software releases prior to 5.1, multicast, CDP, and ARP packets share the same queue. However, in software releases 5.1 and later, these packets are separated into different queues. There are currently no controller commands that can be entered to determine if the multicast receive queue is full. When the queue is full, some packets are randomly discarded.

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 might 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.

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.

Pings Supported to the Management Interface of the Controller

Controller software release or later 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.

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.

GLBP Not Supported

Controller software release 4.2 or later is not compatible with the Gateway Load Balancing Protocol (GLBP). Make sure to configure the controller's default gateway to a fixed address and not to the GLBP virtual address.

IPSec Not Supported

Software release 4.2 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 4.0.

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.

Connecting 1100 and 1300 Series Access Points

You must install software release or later on the controller before connecting 1100 and 1300 series access points to the controller.

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.

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 at this URL:

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

Cisco 1000 series access points in REAP mode do not support the Wi-Fi Multi-Media (WMM) protocol.

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 CiscoSecure ACS 3.2 and later and works with any RFC-compliant RADIUS server.

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 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 2: Run Backup Image from the boot menu to boot from the backup image. Then upgrade with a known working image and reboot the controller.

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.2 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.2 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

Note Port mirroring is also not supported on 4400 series controllers.




QoS per-user bandwidth contracts

IPv6 pass-through

Link aggregation (LAG)

Multicast-unicast mode

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.

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 to release 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>
function submitAction(){
     var link = document.location.href;
     var searchString = "redirect=";
     var equalIndex = link.indexOf(searchString);
     var redirectUrl = "";
     var urlStr = "";
     if(equalIndex > 0) {
            equalIndex += searchString.length;
            urlStr = link.substring(equalIndex);
            if(urlStr.length > 0){
   redirectUrl += urlStr;
         if(redirectUrl.length > 255)
        redirectUrl = redirectUrl.substring(0,255);
       document.forms[0].redirect_url.value = redirectUrl;
     document.forms[0].buttonClicked.value = 4;
function loadAction(){
     var url = window.location.href;
     var args = new Object();
     var query =;
     var pairs = query.split("&");
     for(var i=0;i<pairs.length;i++){
          var pos = pairs[i].indexOf('=');
          if(pos == -1) continue;
          var argname = pairs[i].substring(0,pos);
          var value = pairs[i].substring(pos+1);
          args[argname] = unescape(value);
     //alert( "AP MAC Address is " + args.ap_mac);
     //alert( "The Switch URL is " + args.switch_url);
     document.forms[0].action = args.switch_url;
     // This is the status code returned from webauth login action
     // Any value of status code from 1 to 5 is error condition and user
     // should be shown error as below or modify the message as it suits
     // the customer
     if(args.statusCode == 1){
        alert("You are already logged in. No further action is required on your 
     else if(args.statusCode == 2){
        alert("You are not configured to authenticate against web portal. No further 
action is required on your part.");
     else if(args.statusCode == 3){
        alert("The username specified cannot be used at this time. Perhaps the user is 
already logged into the system?");
     else if(args.statusCode == 4){
        alert("Wrong username and password. Please try again.");
     else if(args.statusCode == 5){
        alert("The User Name and Password combination you have entered is invalid. 
Please try again.");
<body topmargin="50" marginheight="50" onload="loadAction();"> <form method="post"> 
<input TYPE="hidden" NAME="buttonClicked" SIZE="16" MAXLENGTH="15" value="0"> <input 
TYPE="hidden" NAME="redirect_url" SIZE="255" MAXLENGTH="255" VALUE=""> <input 
TYPE="hidden" NAME="err_flag" SIZE="16" MAXLENGTH="15" value="0">
<div align="center">
<table border="0" cellspacing="0" cellpadding="0"> <tr> <td>&nbsp;</td></tr>
<tr align="center"> <td colspan="2"><font size="10" color="#336699">Web 
<tr align="center">
<td colspan="2"> User Name &nbsp;&nbsp;&nbsp;<input type="TEXT" name="username" 
SIZE="25" MAXLENGTH="63" VALUE=""> </td> </tr> <tr align="center" > <td colspan="2"> 
Password &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<input type="Password" name="password" 
SIZE="25" MAXLENGTH="24"> </td> </tr>
<tr align="center">
<td colspan="2"><input type="button" name="Submit" value="Submit" class="button" 
onclick="submitAction();"> </td> </tr> </table> </div>


This section lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points.

Open Caveats

These caveats are open in controller software release

Major Open Caveats

These caveats are open in controller software release and have a severity of 1 or 2.

CSCsg66040—After a software upgrade, controllers might experience intermittent access to the management interface through HTTPS.

Workaround: Follow these steps to workaround the issue:

a. Make sure HTTPS is enabled on the controller's management interface, reboot the controller from the CLI, and monitor the last service if error messages appear after the controller prompts you to enter a username and password to login.

b. Login with the relevant credentials and reconfigure the virtual interface with this CLI command:

config interface address virtual

c. Reboot the controller and make sure the Secure Web service shows up as OK.

d. Generate a certificate using this CLI command:

config certificate generate webauth

e. Click Yes when prompted and wait a few minutes for the certificate to generate.

f. Reboot the controller.

CSCsh93279—The 1000 series access points do not consistently forward probe requests to the controller.

Workaround: None.

CSCsj67447—When you use the controller GUI to modify an existing (or newly created) guest LAN and you choose an ingress interface that is already in use, no error appears. The error that appears on the CLI should also appear on the GUI: "Ingress interface is in use by some other guest lan."

Workaround: None.

CSCsk68117—U-APSD state changes on a client device are not updated on the controller.

Workaround: Reboot the access point, or disassociate the client from the controller and then reassociate it.

CSCsl24600—The 1000 series access points might experience multiple "Watch Exception" errors.

Workaround: None.

CSCsl48639—An IP address can be configured on a dynamic interface on a controller when that IP address has already been assigned to another device on the network.

Workaround: Check the ARP table on the switch to see if the IP address is bound to a MAC address on the network that is not the controller MAC address.

CSCsl79765—When connected to a controller, 1230 series access points containing AIR-MP31G radios sometimes disable the radios and report that no channel is available.

Workaround: Contact Cisco TAC for more information. A Cisco internal-only procedure can be used to update missing environment variables and burn them into a cookie.

CSCsm65043—1240 series access points might stop accepting new clients. In this case, the show controller d1 command shows the following:

Beacon Flags: 0; Beacons are disabled; Probes are disabled 

Workaround: Reboot the access point.

CSCsm96105—The controller does not pass traffic to a client device with a MAC address beginning with 00:00:00:00. This issue occurs with both WGB and wireless clients.

Workaround: None.

CSCso50723—When you use the controller's local RADIUS server for EAP-FAST authentications, authentication might fail if your client already has a protected access credentials (PAC) for the controller to which you are authenticating.

Workaround: Remove the PAC from the client.

CSCso79135—After an initial reboot of the Cisco WiSM or after the online insertion and removal (OIR) of the Cisco WiSM line card, the output of the show wism status CLI command on the Catalyst 6500 series switch shows that the service port is down, even if it is pingable. Wireless functionality is not impacted.

Workaround: Follow these steps:

a. Enter this CLI command on the Cisco WiSM to remove the service VLAN: no wism service-vlan vlan_id.

b. Enter this command to OIR the Cisco WiSM: hw-module module slot reset.

c. Enter this CLI command to add the service VLAN again: wism service-vlan vlan_id.

CSCsq26051—When a Cisco terminal server connects to the controller but the user is not logged in through the console, the controller might hang after a reboot.

Workaround: Remove the console connection cable from the Cisco terminal server.

CSCsr39682—Some access points (such as the 1231, 1240, and 1250) might run out of memory soon after restarting with the latest access point code received from the controller. The access points report low memory and refuse CLI changes.

Workaround: Disable infrastructure management frame protection (MFP).

CSCsr53764—When workgroup bridges (WGBs) are installed on a train and clients joined to the WGBs are running some type of application, the WGBs roam very quickly between access points, and some wired clients might become stuck at a specific access point.

Workaround: Reset the WGBs, enter the clear bridge command on the WGBs, or wait for the WGBs to roam back to the access point where the client is stuck.

CSCsu49139—The config prompt CLI command makes the controller unusable.

Workaround: None.

CSCsw45913—The wrong access control list (ACL) might be applied when the AAA override option is enabled.

Workaround: Disable the AAA override option.

CSCsx48164—The controller has insufficient debugs to troubleshoot web authentication while under a heavy load.

Workaround: None.

CSCsx94678—An 1130 or 1140 series access point might fail to reset its configuration to factory default settings, despite undergoing Mode button recovery. This behavior occurs if the first IOS image in the access point's flash is the recovery image.

Workaround: Connect to the access point using the console port and enter the following commands:

If running IOS prior to 12.4(18a)JA:

debug lwapp console cli
clear lwapp private-config
write erase 

If running IOS 12.4(18a)JA or later:

debug capwap console cli
clear capwap private-config

write erase

CSCsy23940—The controller might reboot because of a software failure of the osapiBsnTimer.

Workaround: None. The controller reboots and automatically returns to normal operation.

CSCsy31995—A 1000 series access point is mapping the wrong 802.11e value on downlink traffic when WLAN mapping to any QoS profile but sending different downlink traffic from the wired client.

Workaround: None.

CSCsz39384—A Cisco WiSM controller running software release is unable to upload the radio core dump file with TFTP from the GUI. The following error message appears: "Failure while storing in flash!"

Workaround: None.

CSCsz48244—The mobility control path for controllers to the DMZ sometimes flaps up and down. However, the data path for the same controllers does not flap.

Workaround: None.

CSCsz53434—When the DHCP address required flag is not enabled for a WLAN, wireless client devices can sometimes forge the IP address for the VLAN if the selected IP address is not in the ARP table.

Workaround: None.

CSCsz64049—Controllers sometimes reboot unexpectedly, and the console output suggests that nf_iterate causes a kernel panic exception error. After rebooting, the controller operates normally until it unexpectedly reboots again.

Workaround: None.

CSCsz87643—The controller might become unreachable while an interface is added to the controller using WCS.

Workaround: Reboot the controller.

CSCta05979—LDAP authentication does not work when the base DN is set to the DC itself (and not to the root of the tree). This problem occurs when the controller is performing LDAP directly (without ACS) and when the server is Active Directory.

Workaround: Set a more precise DN.

CSCta18919—A 2100 series controller might reboot when its access points are downloading software release but it is downloading software release

Workaround: None.

CSCta19001—On a controller with 1000 series access points running software release in an outdoor deployment, when you issue the config advanced 802.11a channel outdoor-ap-dca {enable | disable} CLI command so that the controller does not perform a check for non-DFS channels in the DCA list, the access points reboot continuously.

Workaround: None.

CSCta28660—The controller might reboot because of a software failure of the tsmTask.

Workaround: None.

Moderate Open Caveats

These caveats are open in controller software release and have a severity of 3.

CSCsd54928—The CPU ACL is unable to block LWAPP packets that are destined for the IP address of the dynamic interface.

Workaround: None.

CSCsd77121—Only one CLI session is permitted from the router to the controller network module in a Cisco 28/37/38xx Series Integrated Services Router, even if multiple sessions are configured.

Workaround: None.

CSCsd84706—Containment information for ad-hoc rogue access points is not shown on the controller GUI.

Workaround: Use the controller CLI.

CSCse06202—When a controller's IKE lifetime expires, a rekey is not offered.

Workaround: None.

CSCse06206—The controller sends a DEL notification when the IKE lifetime expires, but it does not send the notice to the client.

Workaround: None.

CSCse43488—The controller might not show the correct maximum output power configuration of a 1000 series access point 5-GHz radio in the -P domain.

Workaround: None.

CSCse75417—A 1000 series access point might report an 802.11b client transmitting at 12 Mbps.

Workaround: None.

CSCse87087—A controller with link aggregation (LAG) enabled fails Ethernet link redundancy. This problem occurs when the controller uses an Ethernet copper gigabit interface converter (GBIC) instead of a fiber GBIC and one of two Ethernet cables is pulled out of the GBIC.

Workaround: Clear the configuration on the controller. Then reconfigure the controller and perform the redundancy test.

CSCsg39910—The 1000 series access points should support direct Telnet to the controller CLI.

Workaround: None.

CSCsg39928—The 1000 series access points should support direct Secure Shell (SSH) to the controller CLI.

Workaround: None.

CSCsg48089—If you lose your controller password and have not backed up the configuration, the recovery mechanism is to revert to the factory default settings.

Workaround: None.

CSCsg68046—The complete reason for a TFTP download failure needs to appear on the controller GUI. If the controller cannot find the software file on the TFTP server during a software upgrade, it reports that the transfer failed rather than that the file is not present.

Workaround: Make sure that the file and filename are entirely correct before upgrading, or upgrade using the CLI to receive a more accurate reason for the failure. Further details are available if you use the debug transfer all enable command prior to upgrade.

CSCsg74578—If you change a controller's management IP address, it is not sent to the access point unless the access point is reset. As a result, multicasting does not work until the change is made on the access point.

Workaround: Reset the access point so that it rejoins the controller and the controller updates the access point with the new configuration.

CSCsg84209—The export foreign controller is not deleting the client device when it receives a HandoffEnd message.

Workaround: None.

CSCsg87111—While editing a WLAN configured for WPA1+WPA2 with a conditional web redirect to 802.1X, the MIB browser shows a commit failure error.

Workaround: Do not directly change from WPA1+WPA2+conditional web redirect to 802.1X+conditional web redirect. Instead, follow these steps:

a. Remove conditional web redirect and save your change.

b. Change Layer2 to 802.1X and save your change.

c. Change Layer3 to conditional web redirect and save your change.

CSCsh11086—If you press Ctrl-S and Ctrl-Q to pause and restart the output of a command such as debug dot1x event enable, the controller reboots.

Workaround: Do not stop the console using Ctrl-S.

CSCsi17242—If a controller starts a timer (such as reauthentication or keylife time) after running for approximately 52 days, the timer might take a long time to fire (up to another 52 days).

Workaround: Clean up the timers. If the problem is related to the client, deauthenticate the client to clean the timer. If the problem is related to the WLAN, such as a broadcast key update, disable and then re-enable the WLAN.

CSCsi26248—You might lose connectivity when adding or recovering a second link aggregation (LAG) link.

Workaround: Recover the LAG link when service is not in use. You might also want to consider not using this type of configuration.

CSCsi72767—A script runs each time you generate a dependency file, which makes the build very slow.

Workaround: None.

CSCsj03124—RLDP behavior is inconsistent when initiated from a Cisco 1250 series access point.

Workaround: Use access points other than the 1250 when RLDP needs to be used.

CSCsj14255—Sometimes the multicast stream to wireless clients stops, and the upstream router does not receive IGMP reports. This problem occurs when there are multiple IGMP requests on the same VLAN and the controller responds only to the last query or when simultaneous IGMP queries are sent from more than five VLANs and the controller responds to only the first five.

Workaround: None.

CSCsj29501—When the session slot or telnet command times out on the supervisor on the Cisco WiSM and you try to log in again, any character that you enter is duplicated.

Workaround: Use a direct console connection to the Cisco WiSM.

CSCsj44861—An access point might transmit neighbor messages when it is not connected to a controller.

Workaround: None.

CSCsj59237—The traffic stream metric (TSM) packet count is not reported correctly.

Workaround: None.

CSCsj59441—Channel information for a rogue access point does not appear on the rogue access point report.

Workaround: Enable the rogue access point trap for the registered controllers or view the channel information on the controller.

CSCsj61649—Whenever a log analysis report is generated on a CCXv5 client using WCS, the DHCP and AAA logs are swapped.

Workaround: Use the controller CLI to view this information.

CSCsj85329—The controller GUI should explain how the password changes with RADIUS compatibility mode. The RADIUS server names help users match to their type of RADIUS server, but the server types should be explained:

Cisco ACS—In the RADIUS access-request packet, the username is the client MAC address, and the password is the client MAC address.

Free RADIUS—In the RADIUS access-request packet, the username is the client MAC address, and the password is the controller's shared secret with the RADIUS server.

Other—In the RADIUS access-request packet, the username is the client MAC address, and the password is not sent in the RADIUS access-request packet.

Workaround: None.

CSCsj87925—The controller GUI netmask for an ACL accepts arbitrary values.

Workaround: Enter a valid netmask.

CSCsj88889—WGB and wired WGB clients are shown using different radios.

Workaround: None.

CSCsj88990—Rogue access point client information shown for the access point does not match the client information from the Rogue Client Details link.

Workaround: View the current rogue client information from the controller.

CSCsj96589—Using the MAC address from the label on an 1131 or 1242 access point in the debug mac addr command produces limited debug output.

Workaround: None.

CSCsj97900—The call admission control (CAC) TSPEC is not traffic shaping and allows a new call setup when the physical data rate is higher than one single data rate configured on the controller.

Workaround: Follow the instructions in the VoWLAN deployment guide to enable a realistic higher data rate for the Cisco 7921 phone and turn on the supported rate as recommended.

CSCsk08401—The formatting for the config paging ? CLI command needs to be corrected.

Workaround: None.

CSCsk08707—The 1250 series access points receive console error messages indicating that the primary discover decode failed.

Workaround: None.

CSCsk12420—Sometimes a 1000 series access point does not accept the DHCP offer from a Catalyst 3750 switch.

Workaround: None.

CSCsk16462—Deauthentication messages might appear in the WCS logs.

Workaround: Upgrade the controller to software release

CSCsk17001—When a guest LAN with a blank ingress interface name is added to the controller, the application fails with an SNMP exception message.

Workaround: Use the controller CLI to configure a guest LAN. You might need to delete a previous guest LAN if it has a blank ingress interface configured on it and then recreate it. By default, the ingress interface is blank.

CSCsk22861—An MGID entry is not cleared from the access point when IGMP snooping is disabled.

Workaround: None.

CSCsk49157—When you change the session timeout of a WLAN that is using a backend RADIUS authentication server, any existing client that is using that WLAN shows its reauthentication timeout as infinite, even though there is a finite time after which reauthentication occurs.

Workaround: None.

CSCsk49200—The hybrid-REAP local switching option should be removed for wired guest LANs.

Workaround: None.

CSCsk49282—The guest LAN and WLAN are not clearly differentiated.

Workaround: None.

CSCsk50477—The BCAST_Q_ADD_FAILED message contains typographical errors.

Workaround: None.

CSCsk74050— If you configure an ACL name with 32 characters, the ACL override fails during roaming.

Workaround: Use ACL names with up to 31 characters.

CSCsk78264—A change in the RF domain name takes effect only after a reboot.

Workaround: Reboot the controller after changing the RF domain name.

CSCsk79382—CCXv4 and CCXv5 clients receive an Adjacent Access Point Report from the controller even though this report should be sent only to CCXv2 and CCXv3 clients.

Workaround: None.

CSCsk83426—A hybrid-REAP access point does not reauthenticate after entering standalone mode.

Workaround: None.

CSCsk85091—If Rogue Location Detection Protocol (RLDP) is enabled on the controller, you may see radio reset messages on the access point console. There may also be a brief interruption in client traffic flow.

Workaround: Disable RLDP.

CSCsk86536—The wrong error message appears when you change country channels with the 802.11a radio enabled.

Workaround: None.

CSCsl01005—Sometimes bandwidth contracts do not take effect. If a user who has bandwidth restrictions logs in and logs out and then another user who does not have bandwidth restrictions logs in, the bandwidth restrictions are not removed immediately.

Workaround: Reassociate the user between logout of the old user and login of the new user.

CSCsl03097—When a hybrid-REAP access point in standalone mode is on the DFS channel, the access point's radio goes down if a radar event occurs on its operating channel.

Workaround: Wait until the access point's connectivity to the controller recovers, or reboot the access point.

CSCsl42328—The controller should not allow you to use the IP address of the gateway as the interface address.

Workaround: Make sure that the interface IP address and gateway IP address are different.

CSCsl47720—The link test report for a CCX client generated using the controller GUI does not provide enough information.

Workaround: Use the controller CLI. It always provides the correct link test report, except in cases of a CCX client connected to a hybrid-HREAP access point broadcasting a centrally switched WLAN.

CSCsl48776—Controllers sometimes incorrectly forward SSC authentication requests to a RADIUS server.

Workaround: None.

CSCsl52445—The internal web authentication page on the controller accepts up to 2,047 characters, but the internal web authentication page in WCS accepts only 130 characters.

Workaround: If you need to enter more than 130 characters on the internal web authentication page, use the controller interface instead of WCS.

CSCsm03461—A command is needed to show the ER image or bootloader version that is currently running as well as the one that will be installed on the next bootup. Currently, the bootloader is used to verify if an ER image or bootloader upgrade is successful. However, not all controllers include the bootloader in the ER image.

Workaround: Install the Cisco Unified Wireless Network Controller Boot Software ER.aes file, which contains a new bootloader. A successful transfer and upgrade of the ER file indicates that the ER file has been updated properly.

CSCsm40903—Additional information is needed for the following message: "claspam_lrad.c:1626 LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface 4, using default index (50)."

Workaround: None.

CSCsm40906—The following message appears on the 2106 controller when multicast is disabled: "claspam_lrad.c:1626 LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface 4, using default index (50)." No multicast messages should appear when multicast is disabled.

Workaround: None.

CSCsm79901—Wired clients attached to a workgroup bridge (WGB) are retaining the previous IP address after the WGB obtains a new IP address. As a result, the wired client stops sending traffic to the infrastructure network.

Workaround: Release and renew the DHCP IP address manually on the WGB wired client.

CSCsm84048—A 1250 series access point connected to an enhanced power switch cannot get
20 W, even though the switch has enough power remaining.

Workaround: Change the port to be an access port, make the native VLAN 1and allow the VLAN across the trunk port, or configure cdp timer 30 on the switch.

CSCso02340—The controller might report a different power level than is actually used by the access point if you change the channel from one supporting one transmit power to another supporting a different transmit power.

Workaround: Reapply the power configuration.

CSCso07457—When the controller downloads a file using FTP, WCS shows the previous transfer state as the intermediate state, which is different from the final transfer state.

Workaround: None.

CSCso22875—During code download, some access points might disconnect and then reconnect to the controller.

Workaround: None.

CSCso28323—Clients might fail to associate to an 1130 series access point configured for WPA1 AES-CCMP and optional MFP.

Workaround: None.

CSCso31067—Some clients might experience failures during upstream-only prioritized traffic on 802.11a, despite radio resource management (RRM) features being disabled.

Workaround: None.

CSCso31640—When you downgrade a 2100 series controller from software release 5.1 to software release, any hybrid-REAP groups configured on the controller are lost after the downgrade.

Workaround: None. You must reconfigure the hybrid-REAP groups.

CSCso60597—If a 1250 series access point is configured for 20-MHz channel width and is then placed into sniffer mode, you cannot change the channel width to Above 40 MHz or Below 40 MHz. If the access point is configured for Above 40 MHz or Below 40 MHz before it is placed into sniffer mode, you can change the channel width to 20 MHz but not to a 40-MHz setting.

Workaround: Return the access point to local mode in order to modify the channel width settings. Then return it to sniffer mode. This process requires a minimum of two reboots of the access point.

CSCsq14310—If the Allow AAA Override option is enabled for a WLAN, the guest role might not be applied for the local net user.

Workaround: Disable the Allow AAA Override option.

CSCsq14326—A 4400 series controller using a Cisco ACS as a TACACS+ server does not log these CLI commands into the ACS:

config hreap group name add

config hreap group name ap add 00:1c:58:34:40:cc

config hreap group name ap add 00:1a:a1:3f:07:08

config hreap group name delete

Workaround: None.

CSCsq19472—Cisco Compatible Extensions RM measurements are inaccurate if beacon, channel load, frame, and noise histograms are triggered together.

Workaround: Trigger the RM measurements one at a time.

CSCsq23594—When a CCXv5 request is manually sent to a CCXv5 client, an emergency log message is written to the log and sent to any configured syslog servers.

Workaround: None.

CSCsq25129—A controller software upgrade might fail with a Nessus scan running.

Workaround: Stop the Nessus scan and reboot the controller.

CSCsq26491—The show ap uptime CLI command might contain some bogus values.

Workaround: None.

CSCsq29243—When you configure the 802.11h channel switch mode, you should be able to enter only 0 or 1, but you can enter any value.

Workaround: None.

CSCsq30821—When a WLAN is configured on two controllers using web authentication and the WLAN is on a different VLAN on each controller, web authentication can be bypassed if a client roams from one controller to another controller and then back to the first controller.

Workaround: Make sure that any WLAN spanning two controllers using web authentication is on the same VLAN on both controllers.

CSCsq32038—The config interface CLI command allows up to 31 characters to be entered for the interface name. It should allow up to 32 characters.

Workaround: None.

CSCsq34262—A traceback might occur if you include three controllers in the same mobility group and enable a dynamic interface on all of them.

Workaround: Reset the controller.

CSCsq35402—After you upgrade the controller to software release, the following error message appears on the console of the Cisco WiSM controllers: "Mon May 19 12:56:44 2008: dtlARPProtoRecv: Invalid ARP packet!"

Workaround: None.

CSCsq35574—The Authorityid and the server key do not accept a value of 17 or greater.

Workaround: None.

CSCsq35590—If you change a 1240 series access point's country of operation from Spain to the U.S., tracebacks might occur while the access point joins the controller.

Workaround: None; you can safely ignore the tracebacks.

CSCsq38075—If you change a 1240 series access point's country of operation to Spain, tracebacks might appear on the access point console.

Workaround: None; you can safely ignore the tracebacks.

CSCsq38700—If you change the power level on an access point radio while clients are associated to the access point, the controller might display DOWN for the operational status of that radio. However, clients continue to pass traffic and function properly.

Workaround: None.

CSCsq47493—The cLReapApVlanId is not being updated on the controller, and the API is not throwing any exception to indicate that it has not been set.

Workaround: First change the native VLAN ID. Then change the cLReapApVlanId.

CSCsq74144—The controller does not show the channel on which an access point in sniffer mode is sniffing. It shows only the last channel on which the access point was broadcasting in local mode.

Workaround: None.

CSCsr02316—Some SNMPSet operations show a successful status even though the controller is truncating the string.

Workaround: Set a shorter value for the string.

CSCsr16689—The 2106 controller cannot be managed over the dynamic interface even when the management-over-dynamic feature is enabled.

Workaround: None.

CSCsr44439—The web authentication page does not load on the browser when the client connects through a wired guest VLAN on a controller running software release

Workaround: None.

CSCsr45163—When IPv6 clients move from an access point group or VLAN to a new access point group or VLAN, they lose connectivity because all traffic is forwarded to the old VLAN.

Workaround: Configure the clients with a static IPv6 address.

CSCsr58532—The following error message might appear on 2106 controllers: "sim_config.c:194 SIM-3-INTFGET_GIG_ETH_FAIL: Failed to get the interface number of the Gigabit Ethernet Port."

Workaround: None.

CSCsr63100—The controller's message log sometimes fills with "sysapi.c:160 SYSTEM-3-SYSAPI_ERR" messages after dump-low-level debugs are run.

Workaround: None.

CSCsr72091—The radio resource management (RRM) feature in controller software release is not providing consistent results from coverage hole events and channel assignments.

Workaround: None.

CSCsu31680—The AIRESPACE-SWITCHING-MIB contains a missing entry for

Workaround: None.

CSCsu35398—The generated core file does not have a timestamp, which results in an overwrite if you do not change the core filename every time the controller generates a core dump.

Workaround: None.

CSCsu40636—The access point sometimes violates the CTS duration when receiving a U-APSD trigger frame. Instead of waiting for a few milliseconds to protect an upcoming link exchange, it simply transmits the trigger frame.

Workaround: Configure the client to carry through medium reservation time in subsequent frames.

CSCsu44722—The following invalid error message appears when you enable IPv6 for a mobility-anchor-enabled WLAN: "Cannot enable IPv6-bridging when DHCP Address Assignment is enabled for WLAN."

Workaround: Do not enable IPv6 on a mobility anchor-enabled WLAN.

CSCsu80604—The memory monitor configuration returns to default values after the controller reboots.

Workaround: None.

CSCsu84498—The transmit diversity for multicast-broadcast packets is not alternating on the 1240 series access point's antenna ports.

Workaround: None.

CSCsv14863—When access points that have been converted to lightweight mode join a controller with a channel of 0 and a power level of 0, the controller does not send the correct RF settings to the access point.

Workaround: Reapply the auto-RF settings.

CSCsv54436—SSH is sometimes denied on the controller with the following message: "Sorry, telnet is not allowed on this port."

Workaround: Retry the SSH connection.

CSCsv76513—On a 2100 series controller, the WLANs for the 802.11a and 802.11b/g access point radios might show the same BSSID while the same access point on a 4400 series controller shows the correct BSSIDs.

Workaround: None.

CSCsv80270—The following error message might appear when you download a software image to the controller: "TFTP Failure while storing in flash!" This error occurs when access points are downloading the image at the same time.

Workaround: Wait until all the access points finish downloading the image from the controller.

CSCsw68923—HTTP requests sent by Cisco 7921 phones sometimes fail to access the Internet.

Workaround: None.

CSCsx62342—If you configure a hybrid-REAP group in controller software release and then upgrade to software release 6.0, the controller GUI does not show that a hybrid-REAP group is configured.

Workaround: None.

CSCsx67133—The 4.2 controller software includes some mesh configuration options in the GUI and CLI even though the 4.2 software does not support mesh access points.

Workaround: Ignore the mesh options in 4.2.x software releases, or upgrade the controller software if you require mesh support.

CSCsx73649—1140 series access points join the controller, drop off, and then join again repeatedly, and appear on the controller GUI.

Workaround: None.

CSCsx75442—2106 controllers sometimes display this message during software upgrade:

Routine system resource notification.

You can safely ignore these messages.

CSCsx75872—When a client device connected to a workgroup bridge deauthenticates and then reauthenticates, it fails to receive an IP address through DHCP.

Workaround: Force the workgroup bridge to reauthenticate to the wireless LAN; the client devices connected to the workgroup bridge then successfully receive IP addresses.

CSCsx96204—Controllers fail to mark disabled client devices as excluded.

Workaround: None.

CSCsy03762—Local-Eap authentication fails the controller's issuer check when the controller and client certificates are from the same SubCA.

Workaround: Disable these three controller settings:

Check against CA certificates

Verify certificate CN identity

Check certificate date validity

CSCsy31678—When you use the controller CLI to enter a fingerprint SHA value for the CIDS sensor, the fingerprint value does not appear on the controller GUI.

Workaround: None.

CSCsy31942—4404 controllers add the incorrect 802.1p tag on uplink traffic sent with a bronze QoS profile.

Workaround: None.

CSCsy32534—When an access point that is running a CAPWAP image joins an LWAPP controller, the access point might become stuck in the join state during the image downgrade.

Workaround: Reboot the access point and try again.

CSCsy50470—The show wlan summary command is case-sensitive, but it should not be.

Workaround: Enter show wlan summary in lower-case letters on the CLI.

CSCsy60739—The R regulatory domain shows invalid power levels for a 1000 series access point when the transmit power level is set to 1.

Workaround: None.

CSCsy71541—Controllers sometimes fail to clear TSPEC statistics when phones are associated to 1010 series access points.

Workaround: None.

CSCsy76474—Clients are showing as active and in the run state on multiple controllers at the same time.

Workaround: None.

CSCsy76954—Cisco 1242 access points might generate the following traceback:

%SYS-3-NOELEMENT: data_enqueue:Ran out of buffer elements for enqueue -Process= 
"<interrupt level>", ipl= 6, pid= 74 -Traceback= 0x5DCFC 0xFB918 0x16BF94 0x48E5DC 
0x4597FC 0x45940C 0x45C8A4 0x45E7D8 0x2804F4 

Workaround: None.

CSCsy82585—2106 controllers fail to detect that a rogue access point is connected to the wired infrastructure.

Workaround: None.

CSCsy83568—DHCP debug output does not contain mobility state information.

Workaround: None.

CSCsy87329—When you enable WPA1 on the controller GUI, WPA2 is also sometimes enabled.

Workaround: None.

CSCsy99807—RLDP sometimes fails to detect that Linksys 802.11n access points are wired to the infrastructure.

Workaround: None.

CSCsy99905—RLDP consistently finds wired threats only when you use it manually.

Workaround: None.

CSCsz08837—If you downgrade a 2100 series controller from software release 6.0 to, access points might fail to join the controller, and the GUI and Telnet might stop working. This behavior occurs when the controller receives a packet with itself as the source, which can happen when you remote span for the controller port with the controller VLAN included.

Workaround: While doing a remote span, exclude the VLAN used by the controller or prevent the controller packet from looping back and reaching the controller.

CSCsz14243—If you try to enable an 802.1X WLAN on a controller network module when an access point is in the process of joining, the WLAN fails to be enabled, and this error message appears in the system log: "Request failed - refer to log."

Workaround: Try again to enable the WLAN a few seconds later.

CSCsz15011—The auto smartport views an AIR-AP1231G-A-K9 access point as an LWAPP access point and thus applies the LWAPP macro to the interface.

Workaround: None.

CSCsz27349—Some clients fail to authenticate using local authentication. The EAP session appears to complete successfully, but the client rejects the session after receiving the EAP success.

Workaround: None.

CSCsz31934—A controller might intermittently stop forwarding unicast traffic from its wireless clients. This behavior usually occurs on a controller with approximately 115 1250 series access points, 400+ clients associated in the same SSID/VLAN, and all clients transmitting multicast traffic.

Workaround: Enable client exclusion on the WLANs, and manually enter an exclusion entry for the MAC address of each VLAN's default gateway using these CLI commands:

config wlan exclusionlist wlan_id enabled

config exclusionlist add mac_addr description

CSCsz32424—The controller cannot detect an identified rogue on the wire despite seeing it on the wired infrastructure.

Workaround: None.

CSCsz35570—Clients on the management interface cannot access the controller's dynamic interface, even though it can reach other IP addresses in the dynamic subnet.

Workaround: None.

CSCsz36028—Client devices connected to a web authentication WLAN are sometimes not redirected to a login page where the user can enter login credentials and join the network.

Workaround: None.

CSCsz63461—When the WLAN DHCP override is enabled, you can specify the IP address of the mapped interface as a DHCP server.

Workaround: None.

CSCsz72416—Roaming client devices are sometimes assigned to the wrong VLAN when the ACS server is configured for AAA override.

Workaround: None.

CSCsz82548—Web authentication clients used with hybrid-REAP access points can communicate even though their authentication status is "No" after Layer 3 roaming.

Workaround: None.

CSCsz84895—An 802.11g client that is configured with only 802.11b rates receives incomplete rates from the controller's access point.

Workaround: Enable at least one 802.11g rate on the client if possible.

CSCsz85880—Rogue detector access points are not reporting that rogue access points and attached clients are on the wired infrastructure.

Workaround: None.

CSCsz88085—AppleTalk zone information is not accessible for MacBooks that connect through the wireless network.

Workaround: None.

CSCsz88241—The per-user bandwidth contract stops being enforced.

Workaround: Reboot the controller.

CSCsz89606—A 1240 series access point using the DNS option for discovery cannot join the controller after downloading software.

Workaround: Use DHCP option 43 or 60 or use over-the-air provisioning (OTAP).

CSCsz89858—Web authentication fails when the controller does not answer the SSL client hello during the handshake.

Workaround: Reboot the controller.

CSCsz89866—Controllers sometimes fail to send a redirection message during web authentication.

Workaround: None.

CSCsz95595—Some access point IOS commands (copy, for example) might be unavailable from the access point CLI when you use Telnet or SSH to connect to the access point.


Connect a console cable to the access point. At the ap# prompt, enter one of the following hidden commands:

#debug lwapp console cli (4.2 [12.4(10b)J*] or earlier)

#debug capwap console cli (5.0 [12.4(13d)JA] or later)

On the controller CLI, enter the following command:

debug ap enable AP_name

Then you can enter any IOS CLI command using the following syntax:

debug ap command command AP_name

CSCta00537—You can change an access point from hybrid-REAP mode to local mode even if the access point is included in a hybrid-REAP group. The controller should not allow this change.

Workaround: None.

CSCta04267—Third-party chained certificates are not available after downloading a backup configuration file.

Workaround: None.

CSCta05222—Pings drop when a client roams from one hybrid-REAP access point to another and the access points are on the same VLAN subnet as the management and AP-manager subnet. Also, the client MAC address appears in the wrong VLAN on both the hybrid-REAP access point's native VLAN and the client VLAN.

Workaround: Remove the unwanted WLANs on the port channels, except for the locally switched VLAN.

CSCta06460—When a 1231 access point is trying to join a Cisco WiSM, the LWAPP error output shows the "spamVerifyRegDomainSlot: AP (slot 1) unsupported radio type 0XFF" message, and the access point fails to join the controller.

Workaround: None.

CSCta09306—The show client roam-history CLI command does not show the roaming history for the client. This behavior occurs when the controller is running software release and has multiple mobility groups defined and clients are roaming with access points on the same controller.

Workaround: None.

CSCta09996—Sometimes an access point cannot join a controller using an alternative port in a port redundancy environment.

Workaround: None.

CSCta17517—The "%SIM-3-PORT_DOWN" and "%SIM-3-PORT_UP" error messages are not generated when the controller is configured for link aggregation (LAG).

Workaround: None.

CSCta31618—When you use the debug ap command command AP_name CLI command to collect the output of an IOS command, the output might be truncated.

Workaround: Connect directly to the access point using the console, Telnet, or SSH.

CSCta40160—The message logs continuously flood with the following message: "Dropping primary discovery request from AP xx:xx:xx:xx - maximum APs joined x/x." The reported MAC address of the access point is one of the access points already joined to the controller.

Workaround: Prime the access point. Set the primary controller on the access point using this CLI command: config ap primary-base controller_name AP_name controller_IP_address.

CSCta41584—SIM-3-PORT messages are not displayed if the admin status of the port is changed using the controller GUI or CLI. When the messages are displayed, the status might be incorrect.

Workaround: None.

CSCta47390—When you enable IPv6 and then try to add an anchor controller to the WLAN, the following error message appears: "Failed to create anchor switch entry local." The message should be reworded to indicate that IPv6 is not supported with the anchor controller.

Workaround: None.

CSCta49375—A 4400 series controller with a specific configuration (23 interfaces in LAG mode) sometimes crashes during a reboot.

Workaround: None. The controller starts successfully after the next reboot.

CSCta52813—If paging is enabled, the output of the show run-config command contains the "--More-- or (q)uit" prompt; however, the prompt does not stop the command output.

Workaround: Use the show run-config command with paging disabled.

Minor Open Caveats

These caveats are open in controller software release and have a severity of 4 or 5.

CSCsb77595—When logging out from Telnet/SSH sessions, the session always prompts the user to save changes, even when no changes have been made.

Workaround: Ignore the prompt and exit as usual.

CSCsd95723—Some users might be confused when presented with the None and DHCP options for configuring the service port interface in the initial controller setup wizard. These options are available for a controller that has no configuration and the setup wizard is being used to configure it.

Workaround: Users can interpret the None option as Static and a logical alternative to DHCP.

CSCsg32646—If link aggregation (LAG) is enabled on the controller and the port channel is configured on the infrastructure switch, the controller displays only a single entry for its neighbor when you enter the show cdp neighbor CLI command. When you enter the same command on the switch, it displays two entries for the controller for two different ports that are part of LAG. The controller should display two entries when the command is entered on the controller because the switch sends the CDP message from two different ports that are part of the port channel.

Workaround: None.

CSCsg88704—When you use the default controller setting of 512 for the controller database size, the following problems may occur:

If you attempt to add a MAC address to a very long MAC filter list, the following error message appears: "Error in creating MAC filter."

If you add a large number of users to the local database, some user entries might be silently ignored.

If you add SSCs for the access points, at some point no more entries can be added, and the following error message appears: "Authorization entry does not exist in Controller's AP Authorization List."

Workaround: Configure a larger value for the controller database, such as 2048.

CSCsh31104—The word channel is misspelled in the message log.

Workaround: None.

CSCsi13399—The Expiration Timeout for Rogue AP Entries parameter on the Rogue Policies page applies to both rogue access point entries and rogue client entries. The parameter name should be changed to reflect both types of entries.

Workaround: None. This is a cosmetic issue.

CSCsi27596—The controller lacks a supported way to configure the broadcast key rotation interval. Instead, it is hardcoded to a group key rotation interval of 3600 seconds (1 hour).

Workaround: On the console, configure the hidden command devshell dot1xUpdateBroadcastRekeyTimer seconds. This command does not work in an SSH or Telnet session and does not survive a reboot.


(Cisco Controller) >devshell dot1xUpdateBroadcastRekeyTimer(86400)

value = 0 = 0x0

CSCsi30541—Loss of connectivity to the management interface occurs when you add a new dynamic interface and the configured DHCP server on all other interfaces is in the new dynamic interface subnet and the new interface has a shorter mask than the other interfaces.

Workaround: Configure a 10/24 interface or a different 10/16 subnet such that the new dynamic interface does not contain the DHCP server IP address currently defined on all interfaces.

CSCsi40354—Traffic stream metrics (TSM) information is not sorted chronologically on the controller GUI.

Workaround: None.

CSCsi54588—Some 802.1X error messages have inadequate descriptions or incorrect severity levels. For example, the following messages, which can be caused by an incorrectly configured client, have a severity level of 1 when they should have a severity level of 3. As a result, they are logged even when the logging level is set to Critical.



Workaround: Make sure that clients are correctly configured to minimize error logging.

CSCsi59203—Despite holding down the Mode button while powering up a lightweight IOS access point until its LED turns yellow, the access point might retain some nonvolatile configuration information, such as its static IP address, controller information, or default IP gateway.

Workaround: Convert the access point to IOS and then from IOS back to LWAPP.

CSCsi62915—Static IP wireless devices are not shown on the controller until they send a packet. The IP address information should appear on the MAC Filtering > Details page of the controller GUI and in the output of the show run-config CLI command.

Workaround: To see static IP wireless devices in the controller's local MAC filter list, enter a CLI command similar to the following:

config macfilter add 00:01:02:03:04:05 3 200 "test prt"

CSCsi72324—A service port with IP address responds to an ARP for the AP-manager interface.

Workaround: Unplug the service port and reconfigure it on the correct subnet.

CSCsj06245—Portions of the output of the show tech-support CLI command might be formatted incorrectly, making the information difficult to read.

Workaround: None.

CSCsk01633—The EAPOL key message is truncated with an invalid replay counter.

Workaround: None.

CSCsk60655—The default frequency value in the intrusion detection system (IDS) file should be equal to or greater than the maximum deauthentication packets sent by an access point.

Workaround: None.

CSCsk63047—Dynamic transmit power control (DTPC) does not work on Cisco1240 series access points in WGB mode.

Workaround: None.

CSCsl04281—The show run-config command might truncate access point neighbor information in a large environment.

Workaround: To reduce the occurrence of this issue, disable paging using the config paging disable command.

CSCsl11352—The console output in software release 4.2 does not indicate which controller an access point joins when you add it to your network.

Workaround: On the access point console, right after you see the "Press Return to get started" message, enter enable mode (the default password is Cisco), and enter this debug command:

debug ip udp

The output shows all UDP packets sent and received by the access point.

CSCsl16445—When an access point radio status is down due to lack of CDP response from a neighboring switch, the controller reports Cause=Unknown. However, it should report Cause=Waiting for CDP response.

Workaround: None; this issue is cosmetic.

CSCsl40018—The hybrid-REAP design and deployment guide incorrectly implies that you can configure NAT on both the hybrid-REAP and controller sides of the network link. In reality, NAT is supported only on the access point side of the network link. The hybrid-REAP design and deployment guide is available at this URL:

Workaround: None.

CSCsl67177—The Catalyst Express 500 (CE500) might lose connectivity to a 4400 series controller when one port of the portchannel is shut down.

Workaround: Unplug and then plug in both Etherchannel links on the CE500 or the controller. Plug in or unplug any device on the CE500.

CSCsl70043—When a client device connects to a secure EAP WLAN and immediately switches to an open WLAN, the access point sends a status 12 association response (which is normal) but sends it from the wrong MAC address and BSSID.

Workaround: On the controller CLI, enter config network fast-ssid-change to allow the client devices to connect without incident.

CSCsl19319—If you create a local user profile on the GUI of a 2106 controller with the WLAN profile "any WLAN" and then edit the profile, the following error message appears: "Error in setting WLAN ID for user." However, your change is applied.

Workaround: Delete the local user profile and create a new one with the updated password or description or define a WLAN profile for the user.

CSCsl95615—When a master controller exists on the network, an access point that is joined to a secondary or tertiary controller keeps going back to discovery.

Workaround: Disable the master controller mode.

CSCsm08623—If the config paging disabled CLI command is entered on the controller, the output of the show msglog command is periodically interrupted with the "Would you like to display the next 15 entries?" prompt.

Workaround: None.

CSCsm25943—The meaning of the following error message on the controller is not clear. This message does not necessarily imply that any actual "ARP poisoning" is occurring. Rather, this message appears when a WLAN is configured for DHCP Required and a client (after associating to this WLAN) transmits an ARP message without first using DHCP. The client is unable to send or receive any data traffic until it performs DHCP through the controller.

DTL-1-ARP_POISON_DETECTED: STA [00:01:02:0e:54:c4,] ARP (op 1) received with 
invalid SPA 

Workaround: Perform the following steps:

a. Determine whether you want to force your wireless clients to perform DHCP first, after associating, before they can send IP packets.

If you do, then disable DHCP Required, and you will not encounter this problem.

If you do not, then configure all clients to use DHCP.

b. If the client is configured for DHCP but sometimes still sends IP packets after associating without performing DHCP, then perform the following:

Verify that the client eventually does perform DHCP without undergoing an unacceptable outage. If the outage before performing DHCP is acceptable, then you can ignore this message.

If the client never does perform DHCP after associating, then it can never pass Layer 3 traffic. In this case, either determine how to change the client's behavior so that it always performs DHCP after associating, or simply accept that this client does not work in this application or reconsider your decision to use DHCP Required.

CSCsm40870—The following error message should be reworded:

Jan 24 15:20:55.374 apf_80211.c:2552 APF-4-ASSOCREQ_PROC_FAILED: Failed to process an 
association request from00:13:ce:37:8b:ff. WLAN:2, SSID:TMDInternal-WPA. mobile in 
exclusion list or marked for deletion 

The message should read as follows:

ASSOCREQ_PROC_FAILED: Failed to process an association request from 00:13:ce:37:8b:ff. 
WLAN:2, SSID:TMDInternal-WPA. Mobile excluded or marked for deletion. 

Workaround: None.

CSCsm94702—When the controller is configured through the service port, the VLAN ID and port information do not appear in the output of the show int summary CLI command.

Workaround: None.

CSCso38808—When a CCXv5 client associates to a WLAN that has Aironet IE extensions enabled, the client information table contains no information.

Workaround: None.

CSCso69011—After config paging disable is entered to disable page scrolling, the show interface summary command still shows a "paging" prompt, which could break customer scripts.

Workaround: None.

CSCso69016—After config paging disable is entered to disable page scrolling, the show traplog command still shows a "paging" prompt, which could break customer scripts.

Workaround: None.

CSCsq09590—The client details on the controller GUI and CLI show a session timeout of 0 and a reauthentication timeout of infinite when you connect. However, after the client roams to another access point on the controller, the session timeout remains at 0, but the reauthentication timeout shows 1800 regardless of the timeout configured on the controller. This issue occurs when the controller is configured for WPA2+802.1X with no AAA override.

Workaround: Use the show pmk-cache mac_address CLI command to see the timeout.

CSCsq14833—When using VLSM, if the fourth octet of the management IP address is the same as the fourth octet of the broadcast address of another interface on the controller, the controller does not respond to access point discoveries.

Workaround: Change the IP address of the management interface.

CSCsq46220—Lightweight access points do not get a DNS IP address and syslog facility IP address from a DHCP server hosted on an IOS router.

Workaround: Use a Windows 2000 DHCP server.

CSCsq55045—The IAPP-3-MSGTAG015 and other controller IAPP messages are not documented or documented inadequately.

Workaround: None. The CAPWAP packet message format is documented in the IETF draft.

CSCsq65895—If a DHCP server is not configured on a WLAN or interface, the config dhcp proxy enable CLI command returns the following message, even if all WLANs do not require DHCP: "Some WLAN configurations are inconsistent with the new configuration of the DHCP Proxy. Please check the message log ('show msglog') for details."

Workaround: Configure a valid (or dummy) DHCP address on the WLAN or interface.

CSCsq78560—You can configure port mirroring on 4400 series controllers although this feature is not supported on those controllers.

Workaround: Do not use port mirroring on 4400 series controllers.

CSCsq83787—The port mirroring feature is not implemented on 4400 series controllers and should be removed. This is a legacy feature on 4000 series controllers and is no longer supported.

Workaround: None.

CSCsq83810—STP commands should be removed from the controller GUI and CLI. They are no longer supported and might cause undesired effects when interacting with PSVT.

Workaround: None.

CSCsu24197—Users need the ability to limit the number of associations per access point or WLAN on the controller.

Workaround: None.

CSCsu37392—If you connect a 1250 series access point directly to a PC running Tftpd32 without a firewall and use a Mode button reset, a timeout might occur during a TFTP transfer.

Workaround: Configure the TFTP server for a timeout of 45 seconds.

CSCsu61354—When you attempt to set MAC filters on the controller from WCS, an error message appears indicating that the MAC address cannot be set because it already exists in the database. The error message should indicate that the MAC address is already associated by Auth-list.

Workaround: Enter config auth-list delete mac_address and config macfilter mac_address using the controller CLI. Then enter show mac-filter to see the newly created MAC address.

CSCsu84629—The 1250 series access points change from maximum uniform transmit power back to maximum transmit power on neighbor discovery packets.

Workaround: None.

CSCsu89905—The following error message might appear on a controller running software release during boot-up:

dtl_cfg.c:714 DTL-3-CALLBACK_PROC_FAILED: Callback for command:26 failed for user 
port: 0/0/x 

Workaround: None.

CSCsu90052—The following error message might appear on 4400 series controllers: "sim_config.c:194 SIM-3-INTFGET_GIG_ETH_FAIL: Failed to get the Interface number of the Gigabit Ethernet Port."

Workaround: Clear the configuration and reconfigure the controller.

CSCsu90074—The following error message might appear on the controller at boot-up: "sim.c:272 SIM-3-INVALID_PORT: Using invalid port number. Port out of range. Port # 0."

Workaround: None.

CSCsu90097—The following error message might appear on the controller: "spam.c:449 LWAPP-2-SEM_CREATE_ERR: Could not create semaphore for notifying AP registration."

Workaround: None.

CSCsu90112—The following error message appears on the controller at boot-up, even though symmetric mobility tunneling is disabled: "dtl_ds.c:428 DTL-3-DSNET_CONF_FAILED: Unable to set symmetric mobility tunneling to enabled on Distribution Service interface."

Workaround: Clear the controller configuration and reconfigure the controller.

CSCsv18730—Controllers sometimes unicast an ARP check to the default gateway every 5 to 7 seconds rather than using the configured ARP timeout interval.

Workaround: None.

CSCsv79885—If you initially enter an incorrect mobility group name, the Edit All feature does not save the new mobility group name.

Workaround: Delete the mobility member and re-enter it with the correct name.

CSCsv87385—The controller logs this message when the DHCP packet received on the interface does not contain any DHCP options: "dhcpd.c:206 DHCP-3-MSGTAG095: Bad DHCP packet from DHCP Server, dropping."

Workaround: None.

CSCsw53035—When a controller running software release (with hybrid-REAP local switching and hybrid-REAP VLAN mode enabled) sends a ping reply to a wireless client, the destination MAC address is the client MAC address. As a result, the Layer 3 switch cannot transfer the ping reply packet.

Workaround: None.

CSCsw79978—On the SNMP Trap Controls (Security) page on the controller GUI, the WEP Decrypt Error check box should be reworded because this setting also controls the SNMP decrypt error traps for WPA and WPA2. With the current wording, it is not clear whether this setting also disables the WPA decrypt traps.

Workaround: None.

CSCsw91395—"Trusted AP Missing or Failed" messages appear in the controller log even after you disable trusted access point alerts.

Workaround: None.

CSCsx05502—A guest-access anchor controller stops forwarding traffic to the wired clients.

Workaround: Reset the PC card on the client.

CSCsx09827—In controller software release, the config ap ? CLI command does not list the possible subcommands in alphabetical order.

Workaround: None.

CSCsx50408—LWAP DOS Attack trap messages sometimes fail to record the source MAC address.

Workaround: None.

CSCsx53685—The output of the show run-config ap config CLI command always displays default values for Power Type/Mode.

Workaround: None.

CSCsy19477—When a guest user is logged in and logged out using web auth, incorrect messages appear on the controller console.

Workaround: None.

CSCsy27532—"EAP-Identifier" is misspelled in AAA debug outputs.

Workaround: None.

CSCsy32145—You can only configure HTTP/HTTPS globally on the controller.

Workaround: None.

CSCsy62007—Controllers sometimes drop the DHCP inform packet when a client device is in DHCP required state.

Workaround: Use the config dhcp proxy disabled command to disable DHCP proxy on the controller.

CSCsy74281—The show interface detail interface_name command for a guest LAN interface does not show the VLAN ID.

Workaround: Use the controller GUI to see the VLAN ID for the guest LAN interface.

CSCsy94911—When you try to delete a guest WLAN, the controller sometimes displays this message: "Anchors configured on WLAN - unable to delete WLAN entry," even when no anchors are configured.

Workaround: Add an anchor to the guest WLAN and then delete the anchor; you can then delete the WLAN.

CSCsy98796—The controller web authentication Login Success page does not show the logical DNS name for the virtual interface when configured.

Workaround: Use the raw IP address link provided by the Success page for the logout.html call if needed.

CSCsz03162—When a controller is configured to allow only 802.11g traffic, 802.11b client devices are able to successfully associate to an access point but cannot pass traffic.

Workaround: When you configure the controller for 802.11g traffic only, disable any channels (such as channel 14 in Japan) that allow associations from 802.11b client devices.

CSCsz09498—When client devices trigger the auto-immune code on a controller, it can be difficult to determine how exactly the client device violated the auto-immune rules.

Workaround: None.

CSCsz25704—The VLAN and IP values are sometimes swapped in DHCP-4-INVALID_VLANID_
ARP system messages.

Workaround: None.

CSCsz50249—Access points in local mode, connected to a controller running software release or later, sometimes send 802.11g extended supported rate information elements, regardless of the supported rates on the client. The access point sends the information elements only when 802.11g is enabled on the network. However, hybrid-REAP access points never send 802.11g extended supported rate information elements. To be consistent with access points in local mode, they should.

Workaround: None.

CSCsz62198—Third-party certificates for web authentication are installed but sometimes indicate that they are locally generated.

Workaround: None.

CSCta01626—The controller produces rogue syslog messages, but rogue entries are not populated into the tables.

Workaround: None.

CSCta07301—When you use the default NTP polling interval of 86400 seconds, the controller's clock might drift 2 seconds or more from the actual time. This behavior can cause problems for location.

Workaround: Use the config time ntp interval 3600 CLI command to set the NTP polling interval to the minimum value of 3600 seconds.

Resolved Caveats

These caveats are resolved in controller software release

CSCsl34068—A guest user client is not restricted to the bandwidth configured for the guest role.

CSCsm19182—When an 802.11n radio is operating on channels 52 through 140, the channel width is configured for 40 MHz, and a radar event is detected, it is possible for the radio interface to become disabled instead of moving to another channel. This problem occurs when the access point is operating in the vicinity of radar operations or under extreme traffic conditions (when a false radar detection might occur).

CSCsm32845—The Guest LAN parameter on the Interfaces > Edit page of the controller GUI might cause confusion for users because the guest LAN is used for interfaces involved in wired guest LANs, not for wireless guest WLANs.

CSCso88340—A lightweight IOS access point that has not been configured with a default domain suffix (for example, from its DHCP server) might attempt to resolve the CISCO-LWAPP-
CONTROLLER domain name when it boots up by first attempting to resolve CISCO-LWAPP-
CONTROLLER and then attempting to resolve

CSCsq06451—If you configure a guest LAN and map the ingress interface to a guest LAN interface, you cannot change the mapping to None using the controller GUI.

CSCsq13610—WCS allows special characters in the primary, secondary, and tertiary controller names and access point names, but the controller does not, making the overall behavior inconsistent.

CSCsr89694—On Cisco WiSM controllers running software release, trap logs are generated indicating that the control path between two random mobility members is down. About 10 to 20 minutes later the control path comes back up.

CSCsu52837—Preauthenticated clients cannot reach web-authenticated clients on the same WLAN.

CSCsv42697—The radio interface in an 1140 or 1250 series access point might intermittently display one or more of the following symptoms:

The show controller CLI command might show that beacons and probes are disabled.

This syslog message might appear with tracebacks: "Transmitter seems to have stopped."

This syslog message might appear with tracebacks: "Command 16 timeout."

Radio core dumps might be left in the flash.

CSCsv67671—When an 1140 series access point is in autonomous or hybrid-REAP mode and SSIDs are mapped to VLANs that do not exist on the controller, the access point produces tracebacks and reboots continuously.

CSCsv77658—A 1250 or 1520 series access point no longer reboots because the watchdog timer expired.

CSCsw27841—The controller allows you to configure multiple untagged VLAN interfaces on the same physical port.

CSCsw75392—If you configure a WLAN to simultaneously support WPA+TKIP, WPA+AES, and WPA2+AES, 802.11n clients that are configured for WPA2+PSK or WPA2+802.1X can now associate at all available data rates.

CSCsw84822—An snmpWalk of the clcrRoamReasonReportTable to any controller connected with some clients returns an infinite number of records and the following error message: "Error: OID not increasing."

CSCsx41062—Controllers sometimes reject valid NTP packets and label them spurious.

CSCsx49415—After some time, 1230 series access points stop servicing clients, and the following message appears on the controller: "%CAPWAP-3-ERRORLOG: Could not allocate buffer for sending data transfer request."

CSCsx52830—A 1250 series access point radio might stop providing client access. The radio seems to lose client connectivity, and a reboot of the access point brings the clients back up.

CSCsx57611—The 2.4-GHz radio transmitter in a 1250 series access point might fail, stop, and reset.

CSCsx70686—When Rogue Location Detection Protocol (RLDP) and rogue containment are enabled with a large number of rogues, the beacons and the probes on a 1250 series access point become disabled, and the access point must be rebooted.

CSCsx82639—An 1142 or 1252 access point might stop serving clients. When this behavior occurs, the following message is logged on the access point:

Jan 29 12:28:20.496: %DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - command 16 
timeout -Traceback= 0x5F82C 0x480D00 0x4BBB70 0x4BF2D8 0x47FDC8 0x480190 0x480514 
*Jan 29 12:28:20.505: Writing radio coredump to 'flash:/r0.rcore'  

CSCsy05707—An 1131 access point joined to a controller running software release might enter a state in which clients are not able to associate.

CSCsy15893—Some clients have connectivity issues with lightweight access points when world mode is enabled.

CSCsy68874—The RetryCount field always shows 0 in the output of the show ap stats CLI command.

CSCsy71960—A 1240 series access point receives discovery replies from its primary or secondary controller but joins another controller instead.

CSCsy73154—The access point does not forward the DHCP offer to the client.

CSCsy76154—When link aggregation (LAG) is disabled and DHCP proxy is enabled, DHCP packets relayed from the controller to the DHCP server might be intermittently lost.

CSCsy79782—Controllers sometimes reset the uptime counter to zero when the uptime count reaches 497 days. When the counter resets to zero, client devices are disconnected.

CSCsy96551—When a PC tries to renew an IP address it had before (for example from home network), the controller's internal DHCP server does not send an NAK frame. Instead the controller sends a DHCP ignore message and does not assign an IP address to the machine.

CSCsy97077—The show run-config controller CLI command is truncated or incomplete.

CSCsz17157—When voice traffic runs continuously on 1130 or 1240 series access points for a prolonged period of time, the access points reboot on the CPU voice metrics task.

CSCsz19203—A controller running software release might reboot because of a software failure of the sshpmMainTask.

CSCsz19675—Controllers reboot unexpectedly when LDAP authentication is enabled.

CSCsz40659—During a software upgrade, the file transfer of the new image sometimes fails.

CSCsz51403—When multiple clients connect to the controller with the same username or the AAA server returns a username different from that registered by the client, the following message floods the Cisco WiSM controller's message log: "%APF-1-USER_DEL_FAILED: apf_ms.c:5055."

CSCsz57828—The counters for 1140 series access points do not increment in the output of the show ap stats CLI command.

CSCsz68239—On 2006 controllers, the output for the show acl detail command is not properly formatted.

CSCsz76796—The PMK cache is not updated after a new authentication. The previous cache remains even if the PMK ID is incremented by roaming.

CSCsz80099—Controllers in the same mobility group cannot ping each other but can ping other devices on the network.

CSCta34714—Web authentication redirects might fail for controllers running software release 4.2.

If You Need More Information

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:

(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.)


For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at

Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.

Documentation Updates

This section lists updates to user documentation that has not yet been added to either printed or online documents.


The Package Contents section in the Quick Start Guide: Cisco 4400 Series Wireless LAN Controllers should be updated to include this item, which is included with the 4400 series controller:

DB-9-to-DB-9 null modem cable

Related Documentation

For additional information on the Cisco controllers and lightweight access points, refer to these documents:

The quick start guide for your particular controller or access point

Cisco Wireless LAN Controller Configuration Guide

Cisco Wireless LAN Controller Command Reference

Cisco Wireless Control System Configuration Guide

Click this link to browse to the Cisco Support and Documentation page:

Obtaining Documentation, Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: