 Feedback
|
Table Of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.1.91.0
Cisco Unified Wireless Network Solution Components
Special Rules for Upgrading to Controller Software Release 7.1.91.0
Software Release Support for Access Points
Interoperability With Other Clients in 7.1.91.0
Upgrading to a New Software Release
FCC Safety Compliance Statement
Using the Cisco 5500 Series Controller USB Console Port
Important Notes for Controllers and Non-mesh Access Points
Controllers Unreacheable from WCS when Upgrading from 7.0.116.0 to 7.0.220.0
WPlus License Features Included in Base License
Additive Licenses Available for 5500 Series Controllers
One-Time Password (OTP) Support
RADIUS Called-station-id and Calling-station-id Attributes
Using Access Points in Sniffer Mode
Inter-Release Controller Mobility
802.11g Controller and 802.11b Clients
CAPWAP Problems with Firewalls and ACLs
Messages Appearing Upon Controller Bootup
Crash Files for Cisco Aironet 1250 Series Access Points
802.11a Channels 120, 124, and 128 Disabled
Impact of External Antenna Gain on Transmit Power
Supporting Oversized Access Point Images
MAC Filtering for WGB Wired Clients
CKIP Not Supported with Dynamic WEP
Setting the Date and Time on the Controller
FCC DFS Support on 1130 Series Access Points
Setting the Retransmit Timeout Value for TACACS+ Servers
Configuring an Access Point's Prestandard Power Setting
Controller Functions that Require a Reboot
Rate-Limiting on the Controller
Pings Supported to the Management Interface of the Controller
Pinging from a Network Device to a Controller Dynamic Interface
Preventing Clients from Accessing the Management Network on a Controller
Voice Wireless LAN Configuration
Enabling/Disabling Band Selection and Client Load Balancing
Changing the IOS CAPWAP Access Point Password
Exclusion List (Blacklist) Client Feature
RADIUS Servers and the Management VLAN
Management Usernames and Local Netuser Names
Home Page Retains Web Authentication Login with IE 5.x
Changing the Default Values of SNMP Community Strings
Changing the Default Values for SNMP v3 Users
DirectStream Feature Is Not Supported With WGB
Features Not Supported on Cisco 5500 Series Controllers
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
Upgrading External Web Authentication
Switch Port and Controller Port
Unsupported mac-address Command for Unified and Autonomous Access Points
Fast Roaming and Authentication/Key Management for CCKM Clients
Errors When Using AAA with an Active RADIUS Fallback
Roaming Clients When Access Points are in Standalone Mode
Using Lightweight Access Points with NAT
Important Notes for Controllers and Mesh Access Points
Features Not Supported on Mesh Networks
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.1.91.0
First Published: November 8, 2011OL-19342-07These release notes describe open and resolved caveats for release 7.1.91.0 for Cisco 2500, 5500, WiSM2, WLCM2, and Cisco Flex 7500 Series Wireless LAN Controllers. 7.1.91.0 is a special release to introduce the Cisco Aironet 3600 Access Points. Ongoing support for this release will not be provided and is not supported in any other 7.0 maintenance release.
The release 7.1.91.0 for the AP-3600 is a restricted lifetime release, with no planned maintenance images. For future fix and feature development, customers are encouraged to migrate to next major release for ongoing support and improvements.
Note
Unless otherwise noted, all of the Cisco Wireless LAN controllers are referred to as controllers, and all of the Cisco lightweight access points are referred to as access points.
Contents
These release notes contain the following sections:
•
•
•
•
•
•
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•
•
•
•
•
•
Note
•
•
•
•
•
•
•
•
•
Note
The AP801 is an integrated access point on the Cisco 800 Series Integrated Services Routers (ISRs). For more information on the SKUs for the access points and the ISRs, refer to the following data sheets:
•
–
•
–
–
–
–
•
http://www.cisco.com/en/US/prod/collateral/routers/ps380/data_sheet_c78-519930.html
Note
Controller Requirements
The controller GUI requires the following operating system and web browser:
•
•
MIB Files
Cisco controllers support standard SNMP Management Information Base (MIB) files. MIBs can be downloaded from the Software Center on Cisco.com. Only one MIB is posted per major release (7.0.220.0, 7.0.116.0, 7.0.98.0, 6.0, 5.2, 5.1, and so on). If an updated MIB becomes available, the previous version is removed from the Software Center and replaced by the new version.
New Features
Two new Access Point platforms (3600 Series) are supported in this Controller release (7.1.91.0).
There are no other new software features in this release.
Software Release Information
The 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. We recommend that you install the latest software version available for maximum operational benefit.
Guidelines and Limitations
The Cisco Wireless LAN Controller Network Module is supported on Cisco 2800/3700/3800 Series Integrated Services Routers running Cisco IOS Release 12.4(15)T, 15.0(1)M or later, and on 2900/3900 ISRs running 15.0(1)M and later.
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.
Special Rules for Upgrading to Controller Software Release 7.1.91.0
Before upgrading your controller to software release 7.1.91.0, you must comply with the following rules:
•
•
•
•
–
–
–
–
•
•
•
•
•
•
Software Release Support for Access Points
Table 1-2 lists the controller software releases that support specific Cisco access points. The First Support column lists the earliest controller software release that supports the access point. For access points that are not supported in ongoing releases, the Last Support column lists the last release that supports the access point.
Table 1-2 Software Support for Access Points
1000 Series
AIR-AP1010
3.0.100.0
4.2.207.0
AIR-AP1020
3.0.100.0
4.2.207.0
AIR-AP1030
3.0.100.0
4.2.207.0
Airespace AS1200
—
4.0
AIR-LAP1041N
7.0.98.0
AIR-LAP1042N
7.0.98.0
1100 Series
AIR-LAP1121
4.0.155.0
7.0.x
AIR-LAP1131
3.1.59.24
AIR-LAP1141N
5.2.157.0
AIR-LAP1142N
5.2.157.0
1220 Series
AIR-AP1220A
3.1.59.24
7.0.x
AIR-AP1220B
3.1.59.24
7.0.x
1230 Series
AIR-AP1230A
3.1.59.24
7.0.x
AIR-AP1230B
3.1.59.24
7.0.x
AIR-LAP1231G
3.1.59.24
7.0.x
AIR-LAP1232AG
3.1.59.24
7.0.x
1240 Series
AIR-LAP1242G
3.1.59.24
—
AIR-LAP1242AG
3.1.59.24
—
1250 Series
AIR-LAP1250
4.2.61.0
—
AIR-LAP1252G
4.2.61.0
—
AIR-LAP1252AG
4.2.61.0
—
1260 Series
AIR-LAP1261N
7.0.116.0
AIR-LAP1262N
7.0.98.0
1300 Series
AIR-BR1310G
4.0.155.0
7.0.x
1400 Series
Standalone Only
N/A
—
3500 Series
AIR-CAP3501E
7.0.98.0
AIR-CAP3501I
7.0.98.0
AIR-CAP3502E
7.0.98.0
AIR-CAP3502I
7.0.98.0
AIR-CAP3502P
7.0.116.0
1500 Mesh Series
AIR-LAP-1505
3.1.59.24
4.2.207.54M
AIR-LAP-1510
3.1.59.24
4.2.207.54M
1520 Mesh Series
AIR-LAP1522AG
-A and N: 4.1.190.1 or 5.2 or later1
—
All other reg. domains: 4.1.191.24M or 5.2 or later1
—
AIR-LAP1522HZ
-A and N: 4.1.190.1 or 5.2 or later1
—
All other reg. domains: 4.1.191.24M or 5.2 or later1
—
AIR-LAP1522PC
-A and N: 4.1.190.1 or 5.2 or later1
—
All other reg. domains: 4.1.191.24M or 5.2 or later1
—
AIR-LAP1523CM
7.0.116.0 or later.
AIR-LAP1524SB
-A, C and N: 6.0 or later
—
All other reg. domains: 7.0.116.0 or later.
AIR-LAP1524PS
-A: 4.1.192.22M or 5.2 or later1
—
1550
AIR-CAP1552I-x-K9
7.0.116.0
AIR-CAP1552E-x-K9
7.0.116.0
AIR-CAP1552C-x-K9
7.0.116.0
AIR-CAP1552H-x-K9
7.0.116.0
1552S
AIR-CAP1552SA-x-K9
7.0.220.0
AIR-cAP1552SD-x-K9
7.0.220.0
3600e
AIR-CAP3602E-x-K9
7.1.91.0
3600i
AIR-CAP3602I-x-K9
7.1.91.0
1 These access points are supported in the separate 4.1.19x.x mesh software release or with release 5.2 or later releases. These access points are not supported in the 4.2, 5.0, or 5.1 Releases.
Interoperability With Other Clients in 7.1.91.0
This section describes the interoperability of the version of controller software with other client devices.
Table 1-3 describes the configuration used for testing the clients.
Table 1-4 lists the versions of the clients. The traffic tests included data or voice. The clients included laptops, handheld devices, phones, and printers.
Upgrading to a New Software Release
When you upgrade to the latest software release, the software on the access points associated with the controller 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.
Guidelines and Limitations
•
•
•
•
–
–
•
To upgrade the controller software using the controller GUI, follow these steps.
Step 1
Note
Step 2
a.
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875243
b.
c.
d.
e.
f.
g.
h.
•
•
•
i.
j.
k.
l.
m.
n.
Step 3
Step 4
Note
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
a.
b.
c.
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Note
Installation Notes
This section contains important information to keep in mind when installing controllers and access points.
Warnings
Warning
Warning
Warning
WarningSafety 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
For your safety, and to help you achieve a good installation, read and follow these safety precautions. They might save your life!
1.
2.
3.
4.
5.
a.
b.
c.
6.
7.
8.
Installation Instructions
Refer to the appropriate quick start guide or hardware installation guide for instructions on installing controllers and access points.
Note
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.
Using the Cisco 5500 Series Controller USB Console Port
The USB console port on the Cisco 5500 Series Controllers connects directly to the USB connector of a PC using a USB Type A-to-5-pin mini Type B cable.
Note
For operation with Microsoft Windows, the Cisco Windows USB console driver must be installed on any PC connected to the console port. With this driver, you can plug and unplug the USB cable into and from the console port without affecting Windows HyperTerminal operations.
Note
USB Console OS Compatibility
•
•
•
To install the Cisco Windows USB console driver, follow these steps:
Step 1
a.
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875243
b.
c.
d.
e.
f.
g.
Step 2
Step 3
Step 4
Note
http://support.microsoft.com/kb/918365The USB driver is mapped to COM port 6. Some terminal emulation programs do not recognize a port higher than COM 4. If necessary, change the Cisco USB systems management console COM port to an unused port of COM 4 or lower. To do so, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Important Notes for Controllers and Non-mesh Access Points
This section describes important information about controllers and non-mesh lightweight access points.
Controllers Unreacheable from WCS when Upgrading from 7.0.116.0 to 7.0.220.0
When upgrading the controller software from release 7.0.116.0 to 7.0.220.0, it is found that the controllers that were previously reachable from WCS with SNMPv3 authentication were now unreachable.
Use any of the following workarounds to correct this:
•
•
•
Note
WPlus License Features Included in Base License
These WPlus license features are included in the base license:
•
•
•
The licensing change can affect features on your wireless LAN when you upgrade or downgrade software releases, so you should be aware of these guidelines:
•
•
•
Note
Additive Licenses Available for 5500 Series Controllers
You can now purchase licenses to support additional access points on Cisco 5500 Series Controllers. The new additive licenses (for 25, 50, or 100 access points) can be upgraded from all license tiers (12, 25, 50, 100, and 250 access points). The additive licenses are supported through both rehosting and RMAs.
One-Time Password (OTP) Support
One Time Passwords (OTPs) are supported on the Wireless Lan Controller (WLC) using TACACS and RADIUS. In this configuration, the controller acts as a transparent passthrough device. The controller forwards all client requests to the TACACS/RADIUS server without inspecting the client behavior. When using OTP, the client must establish a single connection to the controller to function properly. The controller currently does not have any intelligence or checks to correct a client that is trying to establish multiple connections.
RADIUS Called-station-id and Calling-station-id Attributes
In software releases prior to 6.0, the controller sends uppercase alphabetic characters in the MAC address. In software release 6.0 or later, the controller sends lowercase alphabetic characters in the MAC address for the RADIUS called-station-id and calling-station-id attributes. If you enabled these attributes for 802.1X authentication in previous releases and upgrade to software release 6.0, client authentication fails. Therefore, you must change the MAC addresses to lowercase characters on the RADIUS server before upgrading to software release 6.0.
Access Point Groups
You can create up to 500 AP Groups on 5500 Series Controllers.
Using Access Points in Sniffer Mode
You must disable IP-MAC address binding in order to use an access point in sniffer mode if the access point is joined to a 5500 series controller or a controller network module running software release 6.0. To disable IP-MAC address binding, enter this command using the controller CLI: config network ip-mac-binding disable.
WLAN 1 must be enabled in order to use an access point in sniffer mode if the access point is joined to a 5500 series controller or a controller network module running software release 6.0. If WLAN 1 is disabled, the access point cannot send packets.
Inter-Release Controller Mobility
Learn more about inter-release controller mobility compatibility across releases at this URL: http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp80877.
RLDP Limitations
The Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue access points that are connected to your wired network. RLDP operates with these limitations:
•
•
•
•
Internal DHCP Server
When clients use the internal DHCP server of the controller, IP addresses are not preserved across reboots. As a result, multiple clients can be assigned with the same IP address. To resolve any IP address conflicts, clients must release their existing IP address and request a new one.
Bootloader Menu
When you plug a controller into an AC power source, the bootup script and power-on self-test run to initialize the system. During this time, you can press Esc to display the bootloader Boot Options Menu. The menu options for the 5500 and Flex 7500 series controllers are different than for other controller platforms.
Bootloader Menu for 5500 Series Controllers:
Boot OptionsPlease choose an option from below:1. Run primary image2. Run backup image3. Change active boot image4. Clear Configuration5. Format FLASH Drive6. Manually update imagesPlease enter your choice:Bootloader Menu for Other Controller Platforms:
Boot OptionsPlease choose an option from below:1. Run primary image2. Run backup image3. Manually update images4. Change active boot image5. Clear ConfigurationPlease enter your choice:Enter 1 to run the current software, enter 2 to run the previous software, or enter 4 (on a 5500 series controller) or 5 (on another controller platform) to run the current software and set the controller configuration to factory defaults. Do not choose the other options unless directed to do so.
Note
Fragmented Pings
Cisco 5500 series controllers do not support fragmented pings on any interface.
802.11g Controller and 802.11b Clients
When a controller is configured to allow only 802.11g traffic, 802.11b client devices are able to successfully connect to an access point but cannot pass traffic. When you configure the controller for 802.11g traffic only, you must mark 11g rates as mandatory.
CAPWAP Problems with Firewalls and ACLs
If you have a firewall or Access Control List (ACL) between the controller and its access points that allows LWAPP traffic, before upgrading to software release 5.2 or later and CAPWAP, you should allow CAPWAP traffic from the access points to the controller by opening the following destination ports:
•
•
The access points use a random UDP source port to reach these destination ports on the controller. In controller software release 5.2, LWAPP was removed and replaced by CAPWAP, but if you have a new out-of-the-box access point, it could try to use LWAPP to contact the controller before downloading the CAPWAP image from the controller. Once the access point downloads the CAPWAP image from the controller, it uses only CAPWAP to communicate with the controller.
Note
Note
Messages Appearing Upon Controller Bootup
Several messages might flood the message logs when the controller boots up. These messages appear because of a failure to read or delete several different configuration files. These are low-severity messages that can safely be ignored. They do not affect controller functionality. These are some examples:
Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : sshpmInitParms.cfg. file removal failed.-Process: Name:fp_main_task, Id:11ca7618Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : bcastInitParms.cfg. file removal failed.-Process: Name:fp_main_task, Id:11ca7618Web 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.
Note
Crash Files for Cisco Aironet 1250 Series Access Points
The 1250 series access points might contain a bootloader older than version 12.4(10b)JA. Units with old bootloaders do not generate a crash log when a crash occurs. The crash log is disabled so that a crash does not corrupt the flash file system. Units with bootloader versions 12.4(10b)JA or later generate a crash log if the access point is associated to a controller running software release 4.2.112.0 or later.
New 1250 series access points shipped from the factory contain new bootloader images, which fix 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.
These examples show the output from the CLI commands (in bold) that you use to check the bootloader version on lightweight and autonomous 1250 series access points:
Commands entered on the controller CLI:
debug ap enable AP001b.d513.1754
debug ap command "show version | include BOOTLDR" AP001b.d513.1754
Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader(C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)Command entered on the access point CLI:
show version | include BOOTLDR
BOOTLDR: C1250 Boot Loader (C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)LWAPP Mode Changes
When you upgrade to controller software release 5.0.148.0 or later, the LWAPP mode changes to Layer 3 if it was previously configured for Layer 2.
If you downgrade from controller software release 7.0.220.0, 6.0.196.0, 6.0.188.0, 5.2.178.0, 5.2.157.0, 5.1.151.0, or 5.0.148.0 to 4.2.61.0 or an earlier release, the LWAPP mode changes from Layer 3 to Layer 2. Access points might not join the controller, and you must manually reset the controller to Layer 3 to resolve this issue.
Issues with APs that Transmit Multicast Frames at Highest Configured Basic Rate and Management Frames with Lowest Basic Rates
Access points running recent Cisco IOS versions transmit multicast frames at the highest configured basic rate and management frames at the lowest basic mandatory rates, can cause reliability problems. Access points running LWAPP or autonomous Cisco IOS should transmit multicast and management frames at the lowest configured basic rate. Such behavior is necessary to provide good coverage at the cell's edge, especially for unacknowledged multicast transmissions where multicast wireless transmissions might fail to be received.
Because multicast frames are not retransmitted at the MAC layer, clients at the edge of the cell might fail to receive them successfully. If reliable reception is a goal, multicast frames should be transmitted at a low data rate. If support for high data rate multicast frames is required, it might be useful to shrink the cell size and disable all lower data rates.
Depending on your specific requirements, you can take the following actions:
•
•
Disabling Radio Bands
The controller disables the radio bands that are not permitted by the configured country of operation (CSCsi48220).
802.11a Channels 120, 124, and 128 Disabled
802.11a channels 120, 124, and 128 are disabled to achieve compliance with draft EN 301 893 version 1.5.1 on the following -E regulatory domain products: AP1131AG, AP1242AG, and AP1252AG.
Impact of External Antenna Gain on Transmit Power
In controller software release 4.2 or later, external antenna gain is factored into the maximum transmit power of the access point. Therefore, when you upgrade from an earlier software release to 4.2 or later, you might see a decrease in transmit power output.
Note
Supporting Oversized Access Point Images
Controller software release 4.2 or later enables 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 1310 series access points). All newer access points have a larger flash size than 8 MB.
Note
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.
To recover the access point using the TFTP recovery procedure, follow these steps:
Step 1
Step 2
Step 3
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 enables 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
Note
Controller software releases 7.0.116.0 and higher provide the passive client feature for Cisco 2500, and 5500 Series Controllers that enable devices like printers connected to WGB to hear ARP requests, answer and move to run state. That is a dynamic alternative that replaces the MAC filter.
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. We recommend that you use either dynamic WEP without CKIP (which is less secure) or WPA/WPA2 with TKIP or AES (which are more secure).
Setting the Date and Time on the Controller
Cisco Aironet lightweight access points do not connect to the 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.
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.
Setting the Retransmit Timeout Value for TACACS+ Servers
We recommend 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-W switch with Power over Ethernet (PoE) by entering this command:
config ap power pre-standard {enable | disable} {all | Cisco_AP}
A Cisco prestandard 15-W switch does not support intelligent power management (IPM) but does have sufficient power for a standard access point. The following Cisco prestandard 15-W 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-W 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-W 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.Controller Functions that Require a Reboot
After you perform these functions on the controller, you must reboot the controller for the changes to take effect:
•
•
•
Rate-Limiting on the Controller
Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired). We recommend 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, we recommend 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 might 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 by best effort. Pinging does not pose a security threat to the network. The controller rate limits any traffic to the CPU, and flooding the controller is prevented. Clients on the WLAN associated with the interface pass traffic normally.
GLBP Support
This version of the controller software release 7.1.91.0 is compatible with the Gateway Load Balancing Protocol (GLBP).
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 must ensure that only authorized clients gain access to the management network through proper CPU ACLs, or use a firewall between the client dynamic interface and the management network.
Voice Wireless LAN Configuration
We recommend 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, if the handset is refused at its first reassociation attempt.
Enabling/Disabling Band Selection and Client Load Balancing
It is not possible to enable or disable band selection and client load balancing globally through the controller GUI or CLI. You can, however, enable or disable band selection and client load balancing for a particular WLAN. Band selection and client load balancing are enabled globally by default.
Changing the IOS CAPWAP Access Point Password
Cisco IOS Control and Provisioning of Wireless Access Points Protocol (CAPWAP) access points have a default password of Cisco, and the pre-stage configuration for CAPWAP 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 mgmtuser add 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 CAPWAP access points is disabled and the access point displays the following error message when the CLI commands are applied:
"ERROR!!! Command is disabled."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.
Client exclusion can happen both statically and dynamically. In a static exclusion, the client is disabled permanently. In dynamic exclusion, the client is excluded until the configured exclusion timeout is reached in the WLAN.
The following client exclusion policies are available:
•
•
•
•
•
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. If you use RADIUS interface override (using the command config wlan radius_server overwrite-interface), you can connect to the dynamic interface to the server.
RADIUS Servers
This product has been tested with CiscoSecure ACS 4.2 and later and works with any RFC-compliant RADIUS server.
Management Usernames and Local Netuser Names
Management usernames and local netuser names must be unique because they are stored in the same database. That is, you cannot assign the same name to a management user and a local netuser.
Using the Backup Image
The controller bootloader stores a copy of the active primary image and the backup image. If the primary image becomes corrupted, you can use the bootloader to boot with the backup image.
With the backup image stored before rebooting, be sure to choose Option 2: Run Backup Image from the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot the controller.
Home Page Retains Web Authentication Login with IE 5.x
Because of a caching problem in the Internet Explorer 5.x browser, the home page retains the web authentication login. To correct this problem, clear the history or upgrade your workstation to Internet Explorer 6.x.
Ad-Hoc Rogue Containment
Client card implementations might mitigate the effectiveness of ad-hoc containment.
Changing the Default Values of SNMP Community Strings
The controller has commonly known default values of "public" and "private" for the read-only and read-write SNMP community strings. Using these standard values presents a security risk. Therefore, We strongly advise that you change these values. See to the Cisco Wireless LAN Controller Configuration Guide, Release 7.0, for configuration instructions.
Changing the Default Values for SNMP v3 Users
The controller uses a default value of "default" for the username, authentication password, and privacy password for SNMP v3 users. Using these standard values presents a security risk. Therefore, we strongly advise that you change these values. See to the Cisco Wireless LAN Controller Configuration Guide, Release 7.0.116.0, for configuration instructions.
Note
DirectStream Feature Is Not Supported With WGB
The DirectStream feature from the controller does not work for clients behind workgroup bridges and the stream is denied.
Features Not Supported on Cisco 5500 Series Controllers
These software features are not supported on Cisco 5500 Series Controllers:
•
Note
•
•
•
•
•
•
Note
•
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
In a crowded RF environment, clients might 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.
Upgrading External Web Authentication
When upgrading a controller from operating system release 2.0 or 2.2.127.4 to release 3.2.116.21 or later, update the external web authentication configuration as follows:
1.
2.
login_templateshown here as follows:
Note
<html><head><meta http-equiv="Pragma" content="no-cache"> <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <title>Web Authentication</title> <script>function submitAction(){var link = document.location.href;var searchString = "redirect=";var equalIndex = link.indexOf(searchString);var redirectUrl = "";var urlStr = "";if(equalIndex > 0) {equalIndex += searchString.length;urlStr = link.substring(equalIndex);if(urlStr.length > 0){redirectUrl += urlStr;if(redirectUrl.length > 255)redirectUrl = redirectUrl.substring(0,255);document.forms[0].redirect_url.value = redirectUrl;}}document.forms[0].buttonClicked.value = 4;document.forms[0].submit();}function loadAction(){var url = window.location.href;var args = new Object();var query = location.search.substring(1);var pairs = query.split("&");for(var i=0;i<pairs.length;i++){var pos = pairs[i].indexOf('=');if(pos == -1) continue;var argname = pairs[i].substring(0,pos);var value = pairs[i].substring(pos+1);args[argname] = unescape(value);}//alert( "AP MAC Address is " + args.ap_mac);//alert( "The Switch URL is " + args.switch_url);document.forms[0].action = args.switch_url;// This is the status code returned from webauth login action// Any value of status code from 1 to 5 is error condition and user// should be shown error as below or modify the message as it suits// the customerif(args.statusCode == 1){alert("You are already logged in. No further action is required on your part.");}else if(args.statusCode == 2){alert("You are not configured to authenticate against web portal. No further action is required on your part.");}else if(args.statusCode == 3){alert("The username specified cannot be used at this time. Perhaps the user is already logged into the system?");}else if(args.statusCode == 4){alert("Wrong username and password. Please try again.");}else if(args.statusCode == 5){alert("The User Name and Password combination you have entered is invalid. Please try again.");}}</script></head><body topmargin="50" marginheight="50" onload="loadAction();"> <form method="post"> <input TYPE="hidden" NAME="buttonClicked" SIZE="16" MAXLENGTH="15" value="0"> <input TYPE="hidden" NAME="redirect_url" SIZE="255" MAXLENGTH="255" VALUE=""> <input TYPE="hidden" NAME="err_flag" SIZE="16" MAXLENGTH="15" value="0"><div align="center"><table border="0" cellspacing="0" cellpadding="0"> <tr> <td> </td></tr><tr align="center"> <td colspan="2"><font size="10" color="#336699">Web Authentication</font></td></tr><tr align="center"><td colspan="2"> User Name <input type="TEXT" name="username" SIZE="25" MAXLENGTH="63" VALUE=""> </td> </tr> <tr align="center" > <td colspan="2"> Password <input type="Password" name="password" SIZE="25" MAXLENGTH="24"> </td> </tr><tr align="center"><td colspan="2"><input type="button" name="Submit" value="Submit" class="button" onclick="submitAction();"> </td> </tr> </table> </div></form></body></html>Switch Port and Controller Port
When the port status on the controller changes, the switch status does not get changed. This is a known issue. For example, when the controller port goes down, the switch port is still in the administrable state. This has been resolved in Cisco 5500 Series Controllers.
Unsupported mac-address Command for Unified and Autonomous Access Points
The unified and autonomous access point do not support the mac-address command for the wireless interfaces. When invoked, the command executes but can cause the access point to fail.
Fast Roaming and Authentication/Key Management for CCKM Clients
CCKM Fast-roaming clients in hybrid REAP mode works only with the following authentication or key management combinations:
•
•
CCKM Fast-roaming clients in hybrid REAP mode is not supported with the following authentication or key management combinations:
•
•
Errors When Using AAA with an Active RADIUS Fallback
Consider a scenario where you configured the active RADIUS fallback feature using AAA for a controller. When using this feature, the controller sends the accounting request probes without the session ID during a fallback, which might be dropped by the RADIUS Server. The controller cannot send accounting information with the session ID because during the fallback the controller does not have the context of the client. Some RADIUS Servers like ISE might report errors for accounting probes that are sent to ISE. If your Authentication and Accounting servers are the same, ignore the errors that are logged in ISE.
Roaming Clients When Access Points are in Standalone Mode
When access points are in standalone mode, they are not aware the states and status of the clients associated with the access points. For example, consider a scenario where two clients (Client 1 and Client 2) are communicating with each other. Also, assume that both the clients are associated with same access point (say, AP1). Let us also assume that both AP1 and AP2 are in standalone mode. Now, if Client 1 roams to AP2, the packets sent from Client 2 do not reach Client 1.
Using Lightweight Access Points with NAT
You can place a lightweight access point under NAT. On the access point side, you can have any type of NAT configured. However, when you configure the controller, you can have only 1:1 (Static NAT) configured and the external NAT IP address configured on the dynamic AP management interface. This situation is applicable only for Cisco 5500 Series Controllers. NAT cannot be configured on the controller because LAPs cannot respond to controllers if the ports are translated to ports other than 5246 or 5247, which are meant for control and data messages.
Note
Important Notes for Controllers and Mesh Access Points
This section describes important information about controllers and mesh access points.
Features Not Supported on Mesh Networks
The following controller features are not supported on mesh networks:
•
•
•
•
•
•
•
Caveats
The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 7.1.91.0. For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
•
•
Note
http://tools.cisco.com/Support/BugToolKit/
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats
Table 1-5 lists open caveats in controller software release 7.1.91.0.
Resolved Caveats
Table 1-6 lists caveats resolved in controller software release 7.1.91.0.
If You Need More Information
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
http://tools.cisco.com/Support/BugToolKit/
(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.)
Troubleshooting
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at
http://www.cisco.com/en/US/support/index.html
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
Documentation Updates
This section lists updates to user documentation that has not yet been added to either printed or online documents.
Related Documentation
For additional information on the Cisco controllers and lightweight access points, see these documents:
•
•
•
•
You can access these documents from this link:
http://www.cisco.com/cisco/web/support/index.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, 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/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.
