Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.130.0
Cisco Unified Wireless Network Solution Components
Special Notice for Mesh Networks
Upgrading to a New Software Release
Special Rules for Upgrading to Controller Software Release 4.2.130.0
FCC Safety Compliance Statement
Crash Files for 1250 Series Access Points
Configuration File Stored in XML Format
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
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
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
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 Point s and WPA2-PSK
Lightweight Access Point Connection Limitations
Management Usernames and Local Netuser Names
802.1X and Microsoft Wireless Configuration Manager
Home Page Retains Web Authentication Login with IE 5.x
Rogue Location Discovery Protocol (RLDP)
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
Obtaining Documentation, Support, and Security Guidelines
These release notes describe open and resolved caveats for software release 4.2.130.0 for Cisco 2000, 2100, and 4400 Series Wireless LAN Controllers; Cisco Wireless Services Modules (WiSM); Cisco Wireless LAN Controller Network Modules; Catalyst 3750G Integrated Wireless LAN Controller Switches; Cisco 3201 Wireless Mobile Interface Cards (WMICs); and Cisco Aironet 1000, 1100, 1130, 1200, 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.
The following components are part of the Cisco UWN Solution and are compatible in this release:
Note
Cisco WCS 5.0.56.0 and 5.0.56.2 do not support controllers running software release 4.2.99.0, 4.2.112.0, or 4.2.130.0.
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.
Note
Do not upgrade to controller software release 4.2.130.0 if you have mesh access points in your network. If your network uses mesh access points, use only mesh-specific releases such as 4.1.191.24M.
Note
Cisco WCS software release 4.2.81.0 may be used to manage both mesh and non-mesh controllers (for example, controllers running software release 4.2.130.0 and 4.1.191.24M). You do not need different instances of WCS to manage mesh and non-mesh controllers.
The controller GUI requires the following operating system and web browser:
Note
Internet Explorer 6.0 SP1 or higher is the only browser supported for accessing the controller GUI and for using web authentication.
Software is factory installed on your controller and automatically downloaded to the access points after a release upgrade and whenever an access point joins a controller. As new releases become available for the controllers and their access points, consider upgrading.
Note
The Cisco WiSM requires software release SWISMK9-32 or later. The Supervisor 720 12.2(18)SXF2 supports the Cisco WiSM software release 3.2.78.4 or later, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release 4.0.155.5 (with Cisco IOS Software Modularity).
Note
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
To use the controller in the Catalyst 3750G Wireless LAN Controller Switch, the switch must be running Cisco IOS Release 12.2(25)FZ, 12.2(35)SE or later, 12.2(37)SE or later, 12.2(44)SE or later, or 12.2(46)SE or later. The following Cisco IOS Releases and any variants are not supported: 12.2(25)SEC, 12.2(25)SED, 12.2(25)SEE, 12.2(25)SEF, and 12.2(25)SEG. All Catalyst 3750 software feature sets (IP Base, IP Service, and Advanced IP Services) are supported for use with the controller.
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.
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 4.2.130.0 to 4.2.61.0 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.
–
Controller software release 4.2.130.0 is greater than 32 MB; therefore, you must make sure that your TFTP server supports files that are larger than 32 MB. Some TFTP servers that support files of this size are tftpd and the TFTP server within the WCS. If you attempt to download the 4.2.130.0 controller software and your TFTP server does not support files of this size, the following error message appears: “TFTP failure while storing in flash.”
–
If 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.
Note
When you upgrade the controller to an intermediate software release, wait until all of the access points joined to the controller are upgraded to the intermediate release before you install the 4.2.130.0 software. In large networks, it can take some time to download the software on each access point.
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 (4.2.112.0 ER.aes) ensures that the boot software modifications in all of the previous and current boot software ER.aes files are installed.
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 4.2.130.0 controller software and the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 ER.aes file from the Software Center on Cisco.com:
a.
Click this URL to go to the Software Center:
https://software.cisco.com/download/navigator.html
c.
Click Wireless LAN Controllers.
d.
Click Standalone Controllers or Integrated Controllers and Controller Modules.
f.
If necessary, click a controller model.
g.
If you chose Standalone Controllers in Step Click Standalone Controllers or Integrated Controllers and Controller Modules., click Wireless LAN Controller Software.
h.
If you chose Cisco Catalyst 6500 Series/7600 Series Wireless Services Module (WiSM) in Step Click a controller series., 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:
j.
Click a software release number.
k.
Click the filename ( filename.aes).
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 4.2.130.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 ER.aes file).
Step 3
Copy the controller software file ( filename.aes) and the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 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 Click Commands > Download File to open the Download File to Controller page. to Click Download to download the software to the controller. A message appears indicating the status of the download. to install the remaining file (either the 4.2.130.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 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 4.2.130.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.
Step 17
To verify that the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 ER.aes file is installed on your controller, enter the show sysinfo command on the controller CLI and look at the Bootloader Version field. “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.
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.
Follow the guidelines in this section to ensure proper operation and safe use of the controllers and access points.
FCC Compliance with its action in ET Docket 96-8, has adopted a safety standard for human exposure to RF electromagnetic energy emitted by FCC-certified equipment. When used with approved Cisco Aironet antennas, Cisco Aironet products meet the uncontrolled environmental limits found in OET-65 and ANSI C95.1, 1991. Proper operation of this radio device according to the instructions in this publication results in user exposure substantially below the FCC recommended limits.
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:
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.
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.
This section describes important information about the controllers and access points.
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.
The 1250 series access points may contain either an old bootloader or a new bootloader. Those with an old bootloader 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. Those with a new bootloader generate a crash log if the access point is running controller software release 4.2.112.0 or later.
New 1250 series access points shipped from the factory contain the new bootloader image, 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 4.2.112.0 or later. Therefore, no user configuration is needed to enable a crash log on new 1250 series access points shipped from the factory.
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.
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.
The controller disables the radio bands that are not permitted by the configured country of operation (CSCsi48220).
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.
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.
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 Cisco.com (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 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 is not supported on access points that are connected directly to the local port of a 2000 or 2100 series controller.
Controller software release 4.1.178.0 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.
In controller software release 4.1.185.0 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).
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.
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.
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 4.1.171.0 software release or later can use channels 100 through 140 in the UNII-2 band.
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)
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.
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:
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:
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.
After you perform these functions on the controller, you must reboot the controller in order for them to take effect:
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.
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.
If you wish to reset the configuration to factory defaults on a 2006 controller, perform one of the following:
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.
Controller software release 4.1.185.0 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 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.
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.
Software release 4.2.130.0 does not allow you to choose IPSec as a Layer 3 security option. None and VPN Passthrough are the only available options. If you upgrade to this release from a previous release that supported IPSec as a Layer 3 security option, any WLANs that are configured for this feature become disabled. If you want to configure IPSec, you must use a version of controller software prior to 4.0.
As designed, 4400 series controllers do not forward IP subnet broadcasts from the wired network to wireless clients across the EoIP guest tunnel.
You must install software release 4.0.179.8 or later on the controller before connecting 1100 and 1300 series access points to the controller.
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.
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.
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 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.
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.
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 in REAP mode do not support the Wi-Fi Multi-Media (WMM) protocol.
Cisco Aironet 1030 Remote Edge Lightweight Access Points do not support WPA2-PSK in REAP standalone mode.
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.
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 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.
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.
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.
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.
Enabling RLDP may cause access points connected to the controller to lose connectivity with their clients for up to 30 seconds.
Client card implementations may mitigate the effectiveness of ad-hoc containment.
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.
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.
These hardware features are not supported on 2000 and 2100 series controllers:
Note
Ports 7 and 8 on 2100 series controllers are PoE ports.
These software features are not supported on 2000 and 2100 series controllers:
Note
Port mirroring is also not supported on 4400 series controllers.
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.
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.
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.
When upgrading a controller from operating system release 2.0 or 2.2.127.4 to release 3.2.116.21 or later, update the external web authentication configuration as follows:
1.
Instead of using a preauthentication ACL, the network manager must configure the external web server IP address using this command:
config custom-web ext-webserver add index IP-address
Note
IP-address is the address of any web server that performs external web authentication.
2.
The network manager must use the new login_template shown here:
Note
Make sure to format the script to avoid any extra characters or spaces before using the web authentication template.
This section lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points.
These caveats are open in controller software release 4.2.130.0.
Workaround: Ignore the prompt and exit as usual.
Workaround: Use the controller CLI.
Workaround: Users can interpret the None option as Static and a logical alternative to DHCP.
Workaround: Clear the configuration on the controller. Then reconfigure the controller and perform the redundancy test.
Workaround: Use a wireless sniffer trace.
Workaround: Use an external packet capture device to collect packets to and from the controller. Send these packets to the Technical Assistance Center (TAC) for analysis.
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 1.1.1.1
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.
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.
Workaround: Reset the access point so that it rejoins the controller and the controller updates the access point with the new configuration.
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.
–
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.
Workaround: Power cycle the 7921 phone.
Workaround: Do not stop the console using Ctrl-S.
Workaround: Redesign the network and reconfigure the communication endpoints to eliminate any points where such a small fragment could be generated.
Workaround: None. This is a cosmetic issue.
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.
Workaround: Recover the LAG link when service is not in use. You might also want to consider not using this type of configuration.
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.
Workaround: Unplug the service port and reconfigure it on the correct subnet.
Workaround: Change the WLAN QoS profile on both the internal controller and the anchor controller to silver.
Workaround: Follow these steps to disable channels 100 to 140. Make sure to disable the radio network and then enable it after the channel change.
a.
On the controller GUI, click Wireless > 802.11a/n.
c.
Uncheck all of the channels between 100 to 140.
d.
Click Apply to commit your changes.
Workaround: Use access points other than the 1250 when RLDP needs to be used.
Workaround: Manually adjust the antenna gain, but this action can interfere with auto RF.
Workaround: Use an upstream ACL if packets with reserved multicast addresses need to be blocked.
Workaround: Ignore the message and choose the correct options to upload files on the controller.
Workaround: Use a direct console connection to the Cisco WiSM.
Workaround: Enable the rogue access point trap for the registered controllers or view the channel information on the controller.
Workaround: Use the controller CLI to view this information.
–
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: Enter a valid netmask.
Workaround: View the current rogue client information from 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.
Workaround: None. Although an error message appears, the user configuration is saved.
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.
Workaround: Reboot the access point, or disassociate the client from the controller and then reassociate it.
Workaround: Use country code KR instead of KE. Note that this reduces the number of available channels on the 802.11a radio to 149, 153, 157, and 161.
Workaround: Use ACL names with up to 31 characters.
Workaround: Disconnect the access point-to-controller path before upgrading the controller from software release 4.2.61.0 or earlier.
Workaround: Reboot the controller after changing the RF domain name.
Workaround: Use port 1 for the management interface, or assign a different port for the management interface and then change back to the original port using these CLI commands:
–
config interface port management any_other_port#
–
config interface port management original_port#
Workaround: After you confirm that the cause is not a spoofing attack from a rogue access point, disable and then re-enable the access points identified in the messages. If the problem persists, disable MFP validation on some of the access points, or disable infrastructure MFP globally.
Workaround: Reassociate the user between logout of the old user and login of the new user.
Workaround: Wait until the access point’s connectivity to the controller recovers, or reboot the access point.
Workaround: To reduce the occurrence of this issue, disable paging using the config paging disable command.
Oct 25 22:21:10.747: WARNING: invalid slot ID (255) passed to REAP -Traceback= 0x51F760 0x51F910 0x4CA740 0x4CDC60 0x4DAB20 0x4BCCBC 0x4BD5E8 0x1CC6DC 0x1CE454
Workaround: Upload the XML file from the controller.
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:
The output shows all UDP packets sent and received by the access point.
Workaround: None; this issue is cosmetic.
Workaround: Change the device’s IP address.
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/71250-h-reap-design-deploy.html
Workaround: Make sure that the interface IP address and gateway IP address are different.
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.
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.
Workaround: Use the controller GUI to create guest user accounts.
Workaround: If you need to enter more than 130 characters on the internal web authentication page, use the controller interface instead of WCS.
Workaround: Unplug and then plug in both Etherchannel links on the CE500 or the controller. Plug in or unplug any device on the CE500.
Workaround: On the controller CLI, enter config network fast-ssid-change to allow the client devices to connect without incident.
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.
Workaround: Disable the master controller mode.
Workaround: Install the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 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.
Workaround: Perform one of the following:
–
Reconfigure the IP endpoints to use smaller MTUs.
–
If there is an IOS router in the IP path used by the IP endpoints, use ip tcp adjust-mss 1300 or a similar command to get the endpoints to reduce the size of the TCP/IP packets that they transmit.
–
Redesign the network path between the EoIP tunnel endpoints to eliminate ICMP filters, tunnels, NAT translations, firewalls, and so on so that it can forward 1500-byte IP packets without fragmentation.
Workaround: Disable and re-enable the radio interface.
Workaround: Move the AP-manager to the same VLAN as the management interface.
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.
b.
If the client is configured for DHCP but sometimes still sends IP packets after associating without performing DHCP, then perform the following:
The message should read as follows:
Workaround: Reboot the controller, and guest users should be able to work fine.
Workaround: Reboot the access point.
Workaround: Release and renew the DHCP IP address manually on the WGB wired client.
Workaround: Reboot the controller.
Workaround: Disable the wired guest WLAN on one of the controllers and enable it as needed. Using an external DHCP server might resolve this issue as well.
Workaround: Manually enable the power injector state after the access point is rebooted.
Workaround: Use the config guest-lan custom-web global disable guest_lan_id CLI command to disable the global configuration.
Workaround: Add an access point to the controller. Then you can add the controller to WCS or change the CDP parameter.
Workaround: Reapply the power configuration.
Workaround: None. You must reconfigure the hybrid-REAP groups.
–
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
These caveats are resolved in controller software release 4.2.130.0.
Browsing to https://1.1.1.1 does work. If browsing to this address does not work when you encounter these symptoms, then you are not encountering this bug.
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
https://tools.cisco.com/bugsearch/
(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
http://www.cisco.com/c/en/us/support/index.html
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
This section lists updates to user documentation that has not yet been added to either printed or online documents.
For additional information on the Cisco controllers and lightweight access points, refer to these documents:
Click this link to browse to the Cisco Support and Documentation page:
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:
http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html