Table Of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
Contents
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 4.2.61.0
New Features
Controller Platform Changes
New Controller Features
New CCXv5 Features
GUI Enhancements
Access Point Additions and Changes
Other Changes
Installation Notes
Warnings
Safety Information
FCC Safety Compliance Statement
Safety Precautions
Installation Instructions
Important Notes
Software Upgrade Might Fail If Certain Characters Used in Previous Configuration
Web Authentication Redirects
Disabling Radio Bands
40-MHz Channels in the 2.4-GHz Band
Regulatory Changes
Supporting Oversized Access Point Images
TKIP 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
IPSec Not Supported
4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel
Re-enable Broadcast after Upgrading to Release 4.0.206.0
Connecting 1100 and 1300 Series Access Points
Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain
Preventing Clients from Accessing the Management Network on a Controller
Voice Wireless LAN Configuration
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
Caveats
Open Caveats
Resolved Caveats
If You Need More Information
Troubleshooting
Documentation Updates
Omissions
Related Documentation
Obtaining Documentation, Support, and Security Guidelines
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
October 26, 2007
These release notes describe open and resolved caveats for software release 4.2.61.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.
Contents
These release notes contain the following sections.
•Cisco Unified Wireless Network Solution Components
•Controller Requirements
•Software Release Information
•New Features
•Installation Notes
•Important Notes
•Caveats
•Troubleshooting
•Documentation Updates
•Related Documentation
•Obtaining Documentation, Support, and Security Guidelines
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•Software release 4.2.61.0 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 4.2.62.0
•Cisco WCS Navigator 1.1.62.0
•Location appliance software release 3.1.35.0
•Cisco 2700 Series Location Appliances
•Cisco 2000 Series Wireless LAN Controllers
•Cisco 2100 Series Wireless LAN Controllers
•Cisco 4400 Series Wireless LAN Controllers
•Cisco Wireless Services Module (WiSM) for Cisco Catalyst 6500 Series Switches
•Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers
•Catalyst 3750G Wireless LAN Controller Switches
•Cisco 3201 Wireless Mobile Interface Card (WMIC)
•Cisco Aironet 1000, 1100, 1130, 1200, 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).
Special Notice for Mesh Networks
Note Do not upgrade to controller software release 4.2.61.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.190.5.
Note Cisco WCS software release 4.2.62.0 may be used to manage both mesh and non-mesh controllers (for example, controllers running software release 4.2.61.0 and 4.1.190.5). 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 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.
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 upgrade the controller to software release 4.2.61.0, the binary configuration file might not migrate correctly. For details, see the "Software Upgrade Might Fail If Certain Characters Used in Previous Configuration" note in the "Important Notes" section.
Caution Do not power down the controller or any access point during this process; otherwise, you might corrupt the software image. Upgrading a controller with a large number of access points can take as long as 30 minutes, depending on the size of your network. However, with the increased number of concurrent access point upgrades supported in software release 4.0.206.0 and later, the upgrade time should be significantly reduced. The access points must remain powered, and the controller must not be reset during this time.
Special Rules for Upgrading to Controller Software Release 4.2.61.0
Caution Before upgrading your controller to software release 4.2.61.0, 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 4.2.61.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 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 3.2.195.10 (or a later 3.2 release), 4.0.206.0 (or a later 4.0 release), or 4.1.171.0 (or a later 4.1 release), you can upgrade your controller directly to software release 4.2.61.0. If your controller is running an earlier 3.2 or 4.0 release, you must upgrade your controller to an intermediate release prior to upgrading to 4.2.61.0. Table 1 shows the upgrade path that you must follow before downloading software release 4.2.61.0.
Table 1 Upgrade Path to Controller Software Release 4.2.61.0
Current Software Release
|
Upgrade Path to 4.2.61.0 Software
|
3.2.78.0 or later 3.2 release
|
Upgrade to 4.0.206.0 (or a later 4.0 release) before upgrading to 4.2.61.0.
|
4.0.155.5
|
Upgrade to 4.0.206.0 (or a later 4.0 release) before upgrading to 4.2.61.0.
|
4.0.179.11
|
4.0.206.0 or later 4.0 release
|
You can upgrade directly to 4.2.61.0.
|
4.1.171.0 or later 4.1 release
|
You can upgrade directly to 4.2.61.0.
|
Note When you upgrade the controller to an intermediate software release, wait until all of the access points joined to the controller are upgraded to the intermediate release before you install the 4.2.61.0 software. In large networks, it can take some time to download the software on each access point.
•Cisco recommends that you also install the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file on the controller. This file resolves bootloader defect CSCsh61233 and is necessary to ensure proper operation of the controller. The ER.aes file is required for all controller platforms.
Note The bootloader is not upgradable on the 2106 controller.
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.61.0 ER.aes) ensures that the bootloader modifications in all of the previous and current boot software ER.aes files are installed.
Caution If you require a downgrade from one release to another, you may lose the configuration from your current release. The workaround is to reload the previous controller configuration files saved on the backup server or to reconfigure the controller.
Follow these steps to upgrade the controller software using the controller GUI.
Step 1 Upload your controller configuration files to a server to back them up.
Note Cisco highly recommends that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
Step 2 Disable the controller 802.11a and 802.11b/g networks.
Step 3 Disable any WLANs on the controller.
Step 4 Follow these steps to obtain the 4.2.61.0 controller software and the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file from the Software Center on Cisco.com:
a. Click this URL to go to the Software Center:
http://www.cisco.com/public/sw-center/sw-wireless.shtml
b. Click Wireless Software.
c. Click Wireless LAN Controllers.
d. Click Standalone Controllers, Wireless Integrated Routers, or Wireless Integrated Switches.
e. Click the name of a controller.
f. Click Wireless LAN Controller Software.
g. Click a controller software release.
h. Click the filename (filename.aes).
i. Click Download.
j. Read Cisco's End User Software License Agreement and then click Agree.
k. Save the file to your hard drive.
l. Repeat steps a. to k. to download the remaining file (either the 4.2.61.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file).
Step 5 Copy the controller software file (filename.aes) and the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file to the default directory on your TFTP server.
Step 6 Click Commands > Download File to open the Download File to Controller page.
Step 7 From the File Type drop-down box, choose Code.
Step 8 In the IP Address field, enter the IP address of the TFTP server.
Step 9 The default values of 10 retries and 6 seconds for the Maximum Retries and Timeout fields should work fine without any adjustment. However, you can change these values if desired. To do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries field and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout field.
Step 10 In the File Path field, enter the directory path of the software.
Step 11 In the File Name field, enter the name of the software file (filename.aes).
Step 12 Click Download to download the software to the controller. A message appears indicating the status of the download.
Step 13 Repeat Step 6 to Step 12 to install the remaining file (either the 4.2.61.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file).
Step 14 After the download is complete, click Reboot.
Step 15 If prompted to save your changes, click Save and Reboot.
Step 16 Click OK to confirm your decision to reboot the controller.
Step 17 After the controller reboots, re-enable the WLANs.
Step 18 Re-enable your 802.11a and 802.11b/g networks.
Step 19 If desired, reload your latest configuration file to the controller.
Step 20 To verify that the 4.2.61.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.
Step 21 To verify that the Cisco Unified Wireless Network Controller Boot Software 4.2.61.0 ER.aes file is installed on your controller, enter the show sysinfo command on the controller CLI and look at the Bootloader Version field.
Note You can use this command to verify the boot software version on all controllers except the 2106 because the bootloader is not upgradable on the 2106 controller.
New Features
The following new features are available in controller software release 4.2.61.0.
Note Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 4.2 for details and configuration instructions for each of these features.
Controller Platform Changes
•The Catalyst 6500 series switch chassis can now support up to six Cisco WiSMs (rather than five) without any other service module installed. If one or more service modules are installed, the chassis can support up to a maximum of four service modules (WiSMs included).
•The Cisco 7600 series router can support up to six Cisco WiSMs without any other service module installed. The integrated Cisco 7600 router and two Cisco 4404 controllers support up to 300 lightweight access points.
Note The WiSM is supported on Cisco 7600 series routers running only Cisco IOS Release 12.2(18)SXF5 or later.
New Controller Features
•7920 and 7921 co-existence—Because 7921 phones support WMM and 7920 phones do not, capacity and voice quality problems can arise if you do not properly configure both phones when they are used in a mixed environment. To enable both 7921 and 7920 phones to co-exist on the same network, make sure that load-based CAC and 7920 AP CAC are both enabled on the controller and the WMM Policy is set to Allowed.
•802.11n support—You can now configure the controller to manage 802.11n devices such as the Cisco Aironet 1250 Series Access Points. The 802.11n devices support the 2.4- and 5-GHz bands and offer high-throughput data rates. You can use the controller GUI or CLI to enable or disable 802.11n mode and to set the modulation and coding scheme (MCS) rates at which data can be transmitted between the access point and the client. By default, 802.11n mode and all of the MCS data rates are enabled. You can also use the CLI to convert the channel bandwidth for 802.11n access points from 20 MHz to 40 MHz and to specify the aggregation method used for 802.11n packets.
Note The 802.11n high-throughput rates are available only on 1250 series access points for WLANs with no Layer 2 encryption or with WPA2/AES encryption enabled.
•Access control list (ACL) counters—ACL counters can assist in determining which ACLs were applied to packets transmitted through the controller. This feature is useful when troubleshooting your system.
Note ACL counters are available only on the following controllers: 4400 series, Cisco WiSM, and Catalyst 3750G Integrated Wireless LAN Controller Switch.
•Access point join process—To better troubleshoot issues with access points that fail to join a controller, you can now configure the access points to send all LWAPP-related errors to a syslog server. You can then view join-related information for all access points that have attempted to join the controller.
•Backup controller support for access points to fail over to controllers outside the mobility group—A single controller at a centralized location can act as a backup for access points when they lose the primary controller in the local region. Centralized and regional controllers need not be in the same mobility group. Using the controller CLI, you can specify a primary, secondary, and tertiary controller for your network's access points. In controller software release 4.2.61.0, you can specify the IP address of the backup controller, which allows the access points to fail over to controllers outside of the mobility group. This feature is currently supported only through the controller CLI.
•CCKM support for hybrid REAP—Hybrid-REAP mode supports Layer 2 fast secure roaming using Cisco Centralized Key Management (CCKM). This feature prevents the need for full RADIUS EAP authentication as the client roams from one access point to another. To use CCKM fast roaming with hybrid-REAP access points, you need to configure hybrid-REAP groups.
•Debug facility—The debug facility enables you to display all packets going to and from the controller CPU. You can enable it for received packets, transmitted packets, or both. By default, all packets received by the debug facility are displayed. However, you can define access control lists (ACLs) to filter packets before they are displayed. Packets not passing the ACLs are discarded without being displayed.
•DHCP proxy—When DHCP proxy is disabled, the controller passes DHCP packets without any modification from the client to the upstream VLAN and vice versa. As a result, the internal DHCP server cannot be used when DHCP proxy is disabled. The ability to disable DHCP proxy allows organizations to use DHCP servers that do not support Cisco's native proxy mode of operation. It should be disabled only when required by the existing infrastructure.
•EDCA support—You can configure enhanced distributed channel access (EDCA) profiles per radio band to provide preferential wireless channel access for voice, video, and other quality-of-service (QoS) traffic. The available options are WMM (the default value), Spectralink Voice Priority, Voice Optimized, and Voice & Video Optimized.
Note In controller software release 4.1, the EDCA profiles are not configurable per radio and do not offer four configuration options. Therefore, you might need to reconfigure the EDCA profiles after upgrading to 4.2.61.0.
•Hybrid-REAP groups—To better organize and manage your hybrid-REAP access points, you can create hybrid-REAP groups and assign specific access points to them. All of the hybrid-REAP access points in a group share the same CCKM, WLAN, and backup RADIUS server configuration information. This feature is helpful if you have multiple hybrid-REAP access points in a remote office or on the floor of a building and you want to configure them all at once. For example, you can configure a backup RADIUS server for a hybrid-REAP group rather than having to configure the same server on each access point. Per controller, you can configure up to 20 hybrid-REAP groups with up to 25 access points per group.
•Hybrid-REAP 802.1X support—Hybrid-REAP mode supports 802.1X authentication to a backup AAA server when the WAN link is down. To support 802.1X EAP authentication, hybrid-REAP access points in standalone mode need to have their own RADIUS servers to authenticate clients. You can configure a backup RADIUS server for individual hybrid-REAP access points by using the controller CLI or for hybrid-REAP groups by using either the GUI or CLI. A backup server configured for an individual access point overrides the RADIUS server configuration for a hybrid-REAP group.
•IPv4 and IPv6 support on the same WLAN—You can enable IPv6 bridging and IPv4 web authentication on the same WLAN. The controller bridges IPv6 traffic from all clients on the WLAN while IPv4 traffic goes through the normal web authentication process. The controller begins bridging IPv6 as soon as the client associates and even before web authentication for IPv4 clients is complete.
Note No other Layer 2 or Layer 3 security policy configuration is supported on the WLAN when IPv6 bridging and web authentication are enabled.
•Local EAP support for PEAP—Local EAP now supports PEAPv0/MSCHAPv2 and PEAPv1/GTC authentication (in addition to LEAP, EAP-FAST, EAP-TLS authentication) between the controller and wireless clients.
•MAC enhancement—A new parameter called Enable Low Latency MAC has been added to the 802.11a or 802.11b/g > EDCA Parameters page. This feature enhances voice performance by controlling packet retransmits and appropriately aging out voice packets on lightweight access points, thereby improving the number of voice calls serviced per access point. You should enable low latency MAC only if the WLAN allows WMM clients.
•Multicast enhancement—In controller software release 4.2, Internet Group Management Protocol (IGMP) snooping is introduced to better direct multicast packets. When this feature is enabled, an access point transmits multicast packets only if a client associated to the access point is subscribed to the multicast group.
Note IGMP snooping is not supported on the 2000 series controllers, the 2100 series controllers, and the Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers.
•NAT mobility—In controller software releases prior to 4.2.61.0, mobility between controllers in the same mobility group does not work if one of the controllers is behind a network address translation (NAT) device. This behavior creates a problem for the guest anchor feature where one controller is expected to be outside the firewall.
Mobility message payloads carry IP address information about the source controller. This IP address is validated with the source IP address of the IP header. This behavior poses a problem when a NAT device is introduced in the network because it changes the source IP address in the IP header. Hence, in the guest WLAN feature, any mobility packet being routed through a NAT device is dropped because of the IP address mismatch.
In controller software release 4.2.61.0, the mobility group lookup is changed to use the MAC address of the source controller. Because the source IP address is changed due to the mapping in the NAT device, the mobility group database is searched before a reply is sent to get the IP address of the requesting controller. This is done using the MAC address of the requesting controller.
When configuring the mobility group in a network where NAT is enabled, enter the IP address sent to the controller from the NAT device rather than the controller's management interface IP address. Also, make sure that the following ports are open on the firewall if you are using a firewall such as pix:
–UDP 16666 for tunnel control traffic
–UDP 16667 for encrypted traffic
–IP protocol 97 for user data traffic
–UDP 161 and 162 for SNMP
Note Client mobility among controllers works only if auto-anchor mobility (also called guest tunneling) or symmetric mobility tunneling is enabled. Asymmetric tunneling is not supported when mobility controllers are behind the NAT device.
•Peer-to-peer blocking—In controller software release 4.2, peer-to-peer blocking is applied to individual WLANs, and each client inherits the peer-to-peer blocking setting of the WLAN to which it is associated. You can configure client traffic on the same WLAN to be bridged locally within the controller, dropped by the controller, or forwarded to the upstream VLAN. This feature is not applicable to the wired guest access feature.
Note The GUI option and CLI command to enable or disable peer-to-peer blocking globally have been removed from the software in favor of this new, more flexible feature.
•QoS roles—In order to prevent guest users from using the same level of bandwidth as regular users, you can create QoS roles with different (and presumably lower) bandwidth contracts and assign them to guest users.
•Splash pages—In controller software releases prior to 4.2, a default login page appears when a client associates to a WLAN using web authentication.This page, which is the same for every WLAN, allows users to enter their credentials. In controller software release 4.2, you can use the splash page feature to display different login pages for different WLANs. For example, different departments within an organization might want to display login pages with their own logo, message, and so on. When you enable web authentication for a wired or wireless guest access WLAN, you can choose to override the global authentication configuration set on the Web Login page (using the Override Global Config parameter) and choose one of the following web login pages for wired or wireless guest users: the default web login page for the controller, a custom web login page that is downloaded to the controller, or a web login page from an external server.
•Syslog server—You can configure the syslog facility for sending syslog messages to a remote host and set the severity level for filtering the syslog messages.
•Wired guest access—This feature enables guest users to connect to the guest access network from a wired Ethernet connection designated and configured for guest access. Wired guest access ports might be available in a guest office or through specific ports in a conference room. Like wireless guest user accounts, wired guest access ports are added to the network using the lobby ambassador feature. Wired guest access can be configured in a standalone configuration or in a dual-controller configuration that uses both an anchor controller and a foreign controller. This latter configuration is used to further isolate wired guest access traffic but is not required for deployment of wired guest access.
Note Although wired guest access is managed by anchor and foreign anchors when two controllers are deployed, mobility is not supported for wired guest access clients. In this case, DHCP and web authentication for the client are handled by the anchor controller.
Note Wired guest access is supported only on the following controllers: 4400 series controllers, the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch.
New CCXv5 Features
•Diagnostic channel—This feature enables you to troubleshoot problems regarding client communication with a WLAN. The client and access points can be put through a defined set of tests in an attempt to identify the cause of communication difficulties the client is experiencing and then allow corrective measures to be taken to make the client operational on the network.
•Client reporting—This protocol is used by CCXv5 clients and the access point to exchange client information. Client reports are collected automatically when the client associates. There are four types of client reports:
–Client profile—Provides information about the configuration of the client.
– Operating parameters—Provides the details of the client's current operational modes.
– Manufacturers' information—Provides data about the wireless LAN client adapter in use.
–Client capabilities—Provides information about the client's capabilities.
•Roaming and real-time diagnostics—You can use roaming and real-time logs and statistics to solve system problems. The event log enables you to identify and track the behavior of a client device. It provides a log of events and reports them to the access point. There are three categories of event logs:
– Roaming log—Provides a historical view of the roaming events for a given client.
–Robust Security Network Association ( RSNA) log—Provides a historical view of the authentication events for a given client.
– Syslog—Provides internal system information from the client. For example, it may indicate problems with 802.11 operation, system operation, and so on.
GUI Enhancements
•Monitor and Controller Menus—The options on these menus have been rearranged.
•All APs page— This page now shows the access point mode, and the layout has been changed to a tabbed format.
•AP Policies page—You can now search for an access point in the authorization list by MAC address.
•Clients page—You can filter clients so that only clients that meet certain criteria (such as MAC address, access point name, WLAN profile, status, radio type, and/or WGB status) are displayed on the Clients page.
•Summary page—You can view the default mobility group under Controller Summary.
Access Point Additions and Changes
•Cisco Aironet 1250 Series Access Point—All controllers now support the Cisco Aironet 1250 Series Access Point. This access point supports two (draft IEEE 802.11n version 2.0) radio modules: a 2.4-GHz radio and a 5-GHz radio. You can configure the radios separately, using different settings on each. For more information, refer to the Cisco Aironet 1250 Series Access Point Q&A at this URL: http://www.cisco.com/en/US/netsol/ns767/netqa0900aecd806b7c82.html
•Support for 16 BSSIDs—All Cisco lightweight access points support 16 BSSIDs per radio and a total of 16 wireless LANs per access point. In previous releases, they supported only 8 BSSIDs per radio and a total of 8 wireless LANs per access point.
Other Changes
These additional changes are applicable to controller software release 4.2.61.0:
•The PMK cache lifetime timer, which is used to trigger reauthentication with the client when necessary, has been changed. It is now based on the timeout value received from the AAA server or the WLAN session timeout setting rather than on the default PMK cache lifetime default value of 12 hours.
•The LDAP backend database now supports these local EAP methods: EAP-TLS, EAP-FAST/GTC, and PEAPv1/GTC. LEAP, EAP-FAST/MSCHAPv2, and PEAPv0/MSCHAPv2 are also supported but only if the LDAP server is set up to return a clear-text password. For example, Microsoft Active Directory is not supported because it does not return a clear-text password.
•You can configure the controller to allow users to access the controller GUI using browsers that support 128-bit (or larger) ciphers. This change provides increased security for secure web mode.
•CLI commands containing locp have been changed to nmsp for Network Mobility Services Protocol (NMSP).
•A new encryption option is available from the Privacy Protocol drop-down box on the SNMP V3 Users > New page called CFB-AES-128 (Cipher Feedback Mode-Advanced Encryption Standard-128). This option is the default value.
•A trap is generated if a WPA or WPA2 client requests a security policy that is inconsistent with the approved security configuration.
•Over-the-air provisioning (OTAP) is now disabled by default on the controller.
•Load-based call admission control (CAC) is now supported on Cisco 1000 series access points.
•The controller's bootup configuration file is now 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.61.0. However, when you upgrade a controller from a previous software release to 4.2.61.0, the configuration file is migrated and converted to XML.
Note Do not attempt to make changes to the configuration file. If you do so and then download the file to a controller, the controller displays a cyclic redundancy checksum (CRC) error while it is rebooting and returns the configuration parameters to their default values.
Installation Notes
This section contains important information to keep in mind when installing controllers and access points.
Warnings
Warning This warning means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents.
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Warning Do not locate any antenna near overhead power lines or other electric light or power circuits, or where it can come into contact with such circuits. When installing antennas, take extreme care not to come in contact with such circuits, as they may cause serious injury or death. For proper installation and grounding of the antenna, refer to national and local codes (e.g. U.S.: NFPA70, National Electrical Code, Article 810, in Canada: Canadian Electrical Code, Section 54).
Warning This product relies on the building's installation for short-circuit (overcurrent) protection. Ensure that the protective device is rated not greater than: 120 VAC, 15A U.S. (240vac, 10A International)
Warning This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the absence of a suitably installed ground connector. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that suitable grounding is available.
Warning Read the installation instructions before you connect the system to its power source.
Warning Do not work on the system or connect or disconnect cables during periods of lightning activity.
Warning Do not operate your wireless network near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use.
Warning In order to comply with radio frequency (RF) exposure limits, the antennas for this product should be positioned no less than 6.56 ft. (2 m) from your body or nearby persons.
Warning This unit is intended for installation in restricted areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security.
Safety Information
Follow the guidelines in this section to ensure proper operation and safe use of the controllers and access points.
FCC Safety Compliance Statement
FCC Compliance with its action in ET Docket 96-8, has adopted a safety standard for human exposure to RF electromagnetic energy emitted by FCC-certified equipment. When used with approved Cisco Aironet antennas, Cisco Aironet products meet the uncontrolled environmental limits found in OET-65 and ANSI C95.1, 1991. Proper operation of this radio device according to the instructions in this publication results in user exposure substantially below the FCC recommended limits.
Safety Precautions
Each year hundreds of people are killed or injured when attempting to install an antenna. In many of these cases, the victim was aware of the danger of electrocution but did not take adequate steps to avoid the hazard.
For your safety, and to help you achieve a good installation, read and follow these safety precautions. They may save your life!
1. If you are installing an antenna for the first time, for your own safety as well as others, seek professional assistance. Your Cisco sales representative can explain which mounting method to use for the size and type of antenna you are about to install.
2. Select your installation site with safety as well as performance in mind. Electric power lines and phone lines look alike. For your safety, assume that any overhead line can kill you.
3. Call your electric power company. Tell them your plans and ask them to come look at your proposed installation. This is a small inconvenience considering your life is at stake.
4. Plan your installation carefully and completely before you begin. Successfully raising a mast or tower is largely a matter of coordination. Each person should be assigned to a specific task and should know what to do and when to do it. One person should be in charge of the operation to issue instructions and watch for signs of trouble.
5. When installing an antenna, remember:
a. Do not use a metal ladder.
b. Do not work on a wet or windy day.
c. Do dress properly—shoes with rubber soles and heels, rubber gloves, long-sleeved shirt or jacket.
6. If the assembly starts to drop, get away from it and let it fall. Remember that the antenna, mast, cable, and metal guy wires are all excellent conductors of electrical current. Even the slightest touch of any of these parts to a power line completes an electrical path through the antenna and the installer: you!
7. If any part of an antenna system should come in contact with a power line, do not touch it or try to remove it yourself. Call your local power company. They will remove it safely.
8. If an accident should occur with the power lines, call for qualified emergency help immediately.
Installation Instructions
Refer to the appropriate quick start guide or hardware installation guide for instructions on installing controllers and access points.
Note To meet regulatory restrictions, all external antenna configurations must be professionally installed.
Personnel installing the controllers and access points must understand wireless techniques and grounding methods. Access points with internal antennas can be installed by an experienced IT professional.
The controller must be installed by a network administrator or qualified IT professional, and the proper country code must be selected. Following installation, access to the controller should be password protected by the installer to maintain compliance with regulatory requirements and ensure proper unit functionality.
Important Notes
This section describes important information about the controllers and access points.
Software Upgrade Might Fail If Certain Characters Used in Previous Configuration
In controller software release 4.2.61.0, the controller's bootup configuration file is stored in an Extensible Markup Language (XML) format rather than in binary format. When you upgrade a controller from a previous software release to 4.2.61.0, the binary configuration file is migrated and converted to XML. However, the configuration file does not migrate correctly if it contains any of the following characters as part of a user configuration string: &, <, >, ', ". For example, a WLAN profile named R&D causes an XML parsing error after the second reboot, even though this profile name is valid in 4.1 and previous configurations.
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.
Regulatory Changes
These regulatory changes apply to the following countries for controller software 4.2.61.0:
•Argentina—802.11a support is removed
•Brazil—802.11a support is removed
•Canada—802.11a -N support is removed
•Philippines—802.11a -N support is removed
•Turkey—For 802.11a, -R is replaced by -I
Access points can no longer join the controller if you attempt to use the restricted 802.11 bands in these countries. For a complete list of the current regulatory rules, refer to the Wireless LAN Compliance Status document at this URL:
http://www.cisco.com/application/pdf/en/us/guest/products/ps5861/c1650/cdccont_0900aecd80537b6a.pdf
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 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.
TKIP and Cisco 7920 IP Phones
When a 7920 phone is associated to a 1250 series access point using Temporal Key Integrity Protocol (TKIP) encryption, the access point might report "TKIP TSC replay detected" and discard the packets transmitted by the phone (CSCsj35039). To work around this issue, perform one of the following:
•Use static or dynamic WEP with 802.1X key management for the 7920 SSID.
•Disable long preambles.
Multicast Limitations
Multicast applications have known performance limitations on the 2000 series controllers, 2100 series controllers, and the Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers. Cisco is working to address these limitations in a future production code release. In the meantime, Cisco recommends that you use the 4400 series or WiSM controllers for multicast intensive applications.
Note 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 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.
CKIP Not Supported with Dynamic WEP
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).
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 4.1.171.0 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:
•AIR-WLC2106-K9
•WS-C3550, WS-C3560, WS-C3750
•C1880
•2600, 2610, 2611, 2621, 2650, 2651
•2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691
•2811, 2821, 2851
•3631-telco, 3620, 3640, 3660
•3725, 3745
•3825, 3845
The enable version of this command is required for full functionality when the access point is powered by a Cisco 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)
•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 controllers: "Rx Multicast Queue is full on Controller." This message does not appear on 4400 series controllers because the 4400 NPU filters ARP packets while all forwarding (multicast or otherwise) and multicast replication are done in the software on the 2006.
2106 Controller LEDs
The 2106 controller's Status LED and AP LED do not flash amber when software is being uploaded to the controller or downloaded to an access point, respectively.
Note Some versions of the Cisco 2106 Wireless LAN Controller Quick Start Guide 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 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
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.
IPSec Not Supported
Software release 4.2.61.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.
4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel
As designed, 4400 series controllers do not forward IP subnet broadcasts from the wired network to wireless clients across the EoIP guest tunnel.
Re-enable Broadcast after Upgrading to Release 4.0.206.0
In software releases 4.0.179.0 and earlier, broadcast and multicast forwarding were both controlled with a single global flag that enabled multicast. Beginning with software release 4.0.206.0, these functions were broken into separate configuration flags: one that controls broadcast and one that controls non-broadcast multicast. If you have multicast enabled in software releases 4.0.179.0 and earlier, the broadcast flag is left disabled after upgrading to software release 4.0.206.0. As a result, some applications that rely on broadcast do not work after the upgrade.
After you upgrade to software release 4.0.206.0, use this CLI command to re-enable broadcast:
config network broadcast enable
When re-enabled, broadcast uses the multicast mode configured on the controller.
Connecting 1100 and 1300 Series Access Points
You must install software release 4.0.179.8 or later on the controller before connecting 1100 and 1300 series access points to the controller.
Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain
To support access points configured for use in Japan, you must upgrade the controller software to release 3.2.116.21 or later. Earlier releases do not support access points configured for use in Japan (regulatory domain -P).
Preventing Clients from Accessing the Management Network on a Controller
To prevent or block a wired or wireless client from accessing the management network on a controller (from the wireless client dynamic interface or VLAN), the network administrator should ensure that there is no route through which to reach the controller from the dynamic interface or use a firewall between the client dynamic interface and the management network.
Voice Wireless LAN Configuration
Cisco recommends that aggressive load balancing always be turned off either through the controller GUI or CLI in any wireless network that is supporting voice, regardless of vendor. When aggressive load balancing is turned on, voice clients can hear an audible artifact when roaming, and the handset is refused at its first reassociation attempt.
Changing the IOS LWAPP Access Point Password
Cisco IOS Lightweight Access Point Protocol (LWAPP) access points have a default password of Cisco, and the pre-stage configuration for LWAPP access points is disabled by default. To enable it, you must configure the access point with a new username and password when it joins the controller. Enter this command using the controller CLI to push a new username and password to the access point:
config ap username user_id password password {Cisco_AP | all}
•The Cisco_AP parameter configures the username and password on the specified access point.
•The all parameter configures the username and password on all the access points registered to the controller.
The password pushed from the controller is configured as "enable password" on the access point.
There are some cases where the pre-stage configuration for LWAPP access points is disabled and the access point displays the following error message when the CLI commands are applied:
"ERROR!!! Command is disabled."
For more information, refer to Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode.
Exclusion List (Blacklist) Client Feature
If a client is not able to connect to an access point, and the security policy for the WLAN and client are correct, the client has probably been disabled. In the controller GUI, you can view the client's status on the Monitor > Summary page under Client Summary. If the client is disabled, click Remove to clear the disabled state for that client. The client automatically comes back and, if necessary, reattempts authentication.
Automatic disabling happens as a result of too many failed authentications. Clients disabled due to failed authorization do not appear on the permanent disable display. This display is only for those MACs that are set as permanently disabled by the administrator.
RADIUS Servers and the Management VLAN
If a RADIUS server is on a directly connected subnet (with respect to the controller), then that subnet must be the management VLAN subnet.
Cisco 1000 Series Access Points and WMM
•
