These caveats are open in operating system release 220.127.116.11:
- CSCar13192—In Cisco 2000 Series Wireless LAN Controllers, the trap message for SNMP authentication failure contains a reversed IP address. If an SNMP query is made to a Cisco 2000 Series Wireless LAN Controller, and if the query results in an authentication failure, the IP address of the querying machine appears reversed on the trap log message.
- CSCar13259—Clients are not excluded on Cisco Aironet 1030 remote edge lightweight access points in REAP mode.
- CSCar13330—When using the web configuration wizard to complete the initial configuration on a Cisco 2000 Series Wireless LAN Controller, on the RADIUS configuration page, after enabling the server, an error message is returned saying “Error in enabling the server.”
Workaround: The RADIUS server may be enabled after the configuration wizard is complete and the wireless LAN controller UI is in regular mode. To go to the RADIUS server details, click the Security tab and then select RADIUS Authentication under the AAA menu. Then, click the edit link for the RADIUS server entry. On the RADIUS edit page, enable the server state and click Apply.
- CSCei65293—The 5-GHz, RM-21A radio module on Cisco Aironet 1200 series lightweight access points has an articulating antenna with a dual function: diversity omni or patch antenna. When the antenna is folded flat to the access point housing it is in 9-dBi patch mode, and when it is in any other position it is in 5-dBi omni mode. When you change the antenna position to switch antenna modes you must reset the Cisco Aironet 1200 series lightweight access point to apply the change.
- CSCsa95763—The wireless LAN controller Web UI cannot display more than 80 local net users on the page Security > AAA > Local Net Users.
Workaround: Use the wireless LAN controller CLI to view all the Local Net User entries.
- CSCsb01980—When using the web configuration wizard on a wireless LAN controller, when the operator enters incorrect data for the management interface, error messages are shown only at the end of the wizard and therefore the user must return to the management interface page for correction. The data entered in the management interface page, such as the port number, is not validated immediately but at the end of the wizard. As a result any error messages are shown only at the end.
Workaround: This problem can cause some inconvenience and the user may prefer to use the CLI configuration wizard instead to avoid it.
- CSCsb01983—The wireless LAN controller Web Configuration wizard is not reachable after making repeated invalid entries for the management interface port.
If an operator connects to the wireless LAN controller Web Configuration wizard on address 192.168.1.1 and enters an invalid port number on the Management Interface configuration page, the operator is redirected at the end of the wizard to the management interface page to correct the port. If the operator enters an incorrect port and submits, the configuration wizard becomes inaccessible.
Workaround: Reboot the wireless LAN controller through the CLI to access the web wizard again.
- CSCsb09699—ACL rules with specified source or destination IP addresses are not working. For instance, if you create a permit ACL with source as 18.104.22.168/255.255.255.255 and all other parameters as any, the wireless client from this IP address cannot ping the server.
- CSCsb30211—Cisco Aironet lightweight access points continue rebooting when WMM mode is enabled. Cisco Aironet lightweight access points may not be able to join the wireless LAN controller if WMM is enabled on any of the wireless LANs.
Workaround: Make sure that the port to which the Cisco Aironet lightweight access point is connected is configured as trunk port and not an access port if any wireless LAN has WMM enabled.
- CSCsb34149—Disabling or deleting a wireless LAN on which a large number of clients exists may not result in deletion of all of the clients. This occurs when a large number (several thousand) clients are using a wireless LAN when the wireless LAN is disabled or deleted.
Workaround: Make sure that wireless LANs with a large number of clients associated are not deleted or disabled.
- CSCsb37605—When the admin status of Cisco Aironet 1000 series lightweight access point radio A is disabled, toggling the 802.11a network status flag re-enables radio A; however, the admin status of radio A is still disabled.
Workaround: Disabling radio A and reapply.
- CSCsb42133—If you enter an invalid value for session timeout when editing a wireless LAN, an incorrect range is shown in an error message.
This bug appears when you select the edit option for a wireless LAN on the wireless LAN controller user interface, set the wireless LAN for 802.1x security, and then enter an invalid value for session timeout. The error message shown when you click Apply incorrectly states that the correct range is 0 to 86400.
Workaround: The correct range for the wireless LAN session timeout is: 300-86400 for 802.1x and 0-65535 for all other security types.
- CSCsa47748—RLDP protocol is not supported in Cisco Aironet 1130 series lightweight access points, Cisco Aironet 1200 series lightweight access points, and Cisco Aironet 1240 series lightweight access points.
Workaround: Use Rogue Detector AP to detect rogue access points.
- CSCsb52557—Cisco Aironet lightweight access points do not connect to the Cisco 4400 Series Wireless LAN Controller if the time is not set first.
Workaround: Set the time on the Cisco 4400 Series Wireless LAN Controller before allowing the Cisco Aironet lightweight access points to connect.
- CSCsb53746—A 350 or CB20A client running ACU 6.4 or ACU 6.5 and configured for LEAP authentication with WPAv1 encryption can authenticate to a Cisco Aironet lightweight access point but does not receive an IP address. This problem does not affect clients running ACU 6.3, which does not use WME data frames.
To check for this problem enter the following command on the wireless LAN controller:
debug dot1x events enable
In the body of the trace that follows authentication by an affected client, the following messages appear:
Fri Jun 3 07:29:59 2005: Received EAPOL-Key from mobile xx:xx:xx:xx:xx:xx
Fri Jun 3 07:29:59 2005: Received EAPOL-key message with invalid version number from mobile xx:xx:xx:xx:xx:xx
Workaround: Configure WME policy to be allowed for the wireless LAN on the wireless LAN controller. To do this on the GUI, browse to the WLANs > Edit page for the appropriate WPAv1 wireless LAN, and in the drop-down menu next to WME policy, select Allowed or Required.
The allowed option means that both WME and non-WME clients can authenticate and receive an IP address; for example, both Aironet ACU 6.4/6.5 and 6.3 clients could authenticate and receive an IP address. The required option means that only WME clients can authenticate; that is, only ACU 6.4/6.5 clients.
- CSCsb54444—RLDP does not work for regulatory domain -E. This condition applies only to countries which require DFS (radar detection) support.
Workaround: Do not enable RLDP in these countries.
- CSCsb55937—VLAN-tagged large ICMP packets that need to be fragmented are not sent by Cisco Aironet 1000 series lightweight access points in direct-connection mode. Ping replies never come back when the Cisco Aironet 1000 series lightweight access point is sending requests to a gateway from a wireless client using large 1500-byte packets, and with RADIUS override configured with any 1p tag. This condition exists for Cisco 4400 Series Wireless LAN Controllers using direct-connect mode, with RADIUS override enabled, the override parameter set to 1p with any VLAN number, and Cisco Aironet 1000 series lightweight access points.
- CSCsb57305—Some Cisco Aironet lightweight access points transmit beacons after the associated wireless LAN is deleted from the wireless LAN controller. This happens only for wireless LANs with radio policy set to 802.11g only and when 802.11g support is globally disabled.
Workaround: If you have a wireless LAN with radio policy 802.11g only, do not disable 802.11g support.
- CSCsb62289—The displayed dBm for Cisco Aironet 1500 series lightweight outdoor access points appears lower than it actually is.
Workaround: In the CLI, the correct values can be up to 6 dBm higher for 2.4-GHz channels and up to 13 dBm higher for 802.11a channels 149 to 165.
- CSCsb63479—Clicking the Refresh link on the Cisco APs page sometimes results in a Page Not Found error. This generally occurs when there are more than 80 Cisco Aironet lightweight access points connected to the wireless LAN controller.
Workaround: Click the Wireless tab at the top of the page and click the Cisco APs link on the left. This causes Cisco WCS to list all the Cisco Aironet lightweight access points on the page.
- CSCsb65096—After changing the bridging shared secret key, the shared secret keys may not be uniformly distributed across the bridge or mesh network. This can cause some Cisco Aironet lightweight access points to fail to connect to the wireless LAN controller using LWAPP, and the Cisco Aironet lightweight access points to time out their connections.
Workaround: Upgrade to the latest code. Ensure that the wireless LAN controller is configured as follows: config network allow-old-bridge-aps disable.
- CSCsb65731—Cisco Aironet 1500 series lightweight outdoor access points are sometimes slow to fail over to a new wireless LAN controller when the primary wireless LAN controller fails.
Workaround: Upgrade to the latest code.
- CSCsb68069—When all eight Wireless LANs are defined on 1130AG, 1200AG, and 1240AG access points converted to lightweight mode, and the radio environment is very busy, transmission attempts can be delayed. The 802.11g radios sometimes report this error:
%DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - Radio command failed, cmd 121 (FF80,0,0) status 7F21 (5,0,0)
When the failure occurs, the radio restarts, all clients are disassociated, the failure is logged, and normal operation resumes.
Workaround: Reduce the number of Wireless LANs in use.
- CSCsb77161—Cisco Aironet 1500 series lightweight outdoor access points are out of compliance with the IEEE 802.11a requirement for maximum receive input level, that is receiver saturation, at data rates of 24, 36, 48, and 54 Mbps. Cisco Aironet lightweight access points can experience increased packet error rates when they are located too close to one another.
Workaround: Mount the Cisco Aironet 1500 series lightweight outdoor access points at least 50 feet (15 m) apart from one another. The software roadmap has a release planned that will enable a gain bypass feature which will correct this performance limitation.
- CSCsb98213—When Cisco Aironet 1030 remote edge lightweight access points and Cisco Aironet 1500 series lightweight outdoor access points in bridging mode are to be used as pole-top access points, they be should be configured as pole-top access points before they are deployed in the network. Not configuring the Cisco Aironet lightweight access points as pole-top access points may result in a longer than normal loss of data connectivity if the roof-top access point loses connection to the wireless LAN controller.
Workaround: Use the CLI commands from a wireless LAN controller to configure the Cisco Aironet lightweight access points as pole-top access points before deploying them.
- CSCsc07129—Cisco Aironet 1500 series lightweight outdoor access points do not forward DHCP broadcast replies, such as those from Microsoft Windows DHCP servers. Pole-top access points do not obtain an IP address if the DHCP server sends the DHCP response to a broadcast address.
Workaround: Either configure the Cisco Aironet 1500 series lightweight outdoor access points with a static IP address or use a DHCP server that sends its response to a unicast address.
- CSCsc17827—For Cisco Aironet 1500 series lightweight outdoor access points and Cisco Aironet 1030 remote edge lightweight access points, channel 165 for the 802.11a radio is only available for the -A SKU when the country code is set to USX. Channel 165 is not available for the -N SKU for any of the countries that use this SKU.
Workaround: In order to set the 802.11a radio to channel 165 when using the -A SKU, set the country code of the wireless LAN controller to USX. For the -N SKU, please select one of the available channels.
- CSCsc35784—The transmit power control adjustment levels 3, 4 and 5 are not supported on Cisco Aironet 1500 series lightweight outdoor access points; these levels correspond to -6, -9, and -12 dB from the maximum power, respectively. Power levels 1 and 2 are supported, which correspond to maximum power for the particular data rate and channel, and -3 dB relative to this maximum. Both the 2.4- and 5.8-GHz bands are affected, at which these adjustment levels provide little or no further reduction in transmit power output.
Workaround: Set the transmit power level to either 1 or 2.
- (NEW CAVEAT)—Over the temperature extremes of the product specification, primarily at the cold temperature extreme of -40 degrees Celsius, the Cisco Aironet 1500 series lightweight outdoor access point does not meet the IEEE 802.11a/b/g transmitter linearity parameter of error vector magnitude (EVM) of the product specification. The software roadmap has a release planned that will enable temperature compensation of the transmit gain, which will address the EVM corner cases over the temperature range.