Cisco Cisco 2106 Wireless LAN Controller
43
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.185.0
OL-31336-01
Caveats
•
CSCsj02690—When you use 1000 series access points, beacons might occur at irregular intervals
on the 2.4-GHz band.
on the 2.4-GHz band.
•
CSCsj02891—When the controller is running software release 4.1.181.0 or 4.1.171.0 and you
enable ARP padding using the config advanced dot11-padding enable CLI command, the 1131,
1231, and 1242 access points send 88-byte neighbor discovery packets instead of the normal 80-byte
packets. When this occurs, the neighbor access points drop the packets and never update their
neighbor access point list for either 802.11a or 802.11b/g radios. As a result, radio resource
management (RRM) sets all access points to full power and does not minimize channel interference.
enable ARP padding using the config advanced dot11-padding enable CLI command, the 1131,
1231, and 1242 access points send 88-byte neighbor discovery packets instead of the normal 80-byte
packets. When this occurs, the neighbor access points drop the packets and never update their
neighbor access point list for either 802.11a or 802.11b/g radios. As a result, radio resource
management (RRM) sets all access points to full power and does not minimize channel interference.
•
CSCsj09449—The public-safety CLI command for individual access points might cause stranding
issues for mesh access points. In controller software release 4.1.185.0 and later, public safety on
mesh access points can only be configured globally, using the following command: config mesh
public-safety {enable | disable} all.
issues for mesh access points. In controller software release 4.1.185.0 and later, public safety on
mesh access points can only be configured globally, using the following command: config mesh
public-safety {enable | disable} all.
•
CSCsj12053—MAC filtering is not supported for workgroup bridge (WGB) wired clients. However,
a wired client might be a terminal server that does not send any traffic but receives traffic instead
(through Telnet requests). As a result, the controller never learns its IP address and deletes the wired
client record.
a wired client might be a terminal server that does not send any traffic but receives traffic instead
(through Telnet requests). As a result, the controller never learns its IP address and deletes the wired
client record.
•
CSCsj12637—If you choose Authentication or Security Errors from the Message Log Level
drop-down box on the Syslog Configuration page of the controller GUI and click Apply, the
configuration is saved as Software Error.
drop-down box on the Syslog Configuration page of the controller GUI and click Apply, the
configuration is saved as Software Error.
•
CSCsj16292—After an upgrade to 12.2(18)SXF9, the following message is displayed:
%DATACORRUPTION-1-DATAINCONSISTENCY: copy error-Traceback=
•
CSCsj18014—The caller ID is received with extra characters.
•
CSCsj18577—A AAA-5-RADSERVER_NOT_FOUND message is logged when using PSK.
•
CSCsj18643—Neighbor packets might not be sent at the correct rates for 802.11a and 802.11b/g
radios.
radios.
•
CSCsj20381—When you run controller software release 4.1.171.0, the attributes sent to the
RADIUS server in debug commands are truncated. The output stops between 48 and 64 bytes. When
debug client is enabled, none of the attributes appear.
RADIUS server in debug commands are truncated. The output stops between 48 and 64 bytes. When
debug client is enabled, none of the attributes appear.
•
CSCsj21554—Lobby account users, after login in controller, can see WLC configuration by using
each section URL, instead of following the restricted web interface.
each section URL, instead of following the restricted web interface.
•
CSCsj26597—Regardless of whether an access point is in PSK or EAP mode, it can enter a state in
which it excludes potential parents, even if the parents are viable. A reboot of the child immediately
fixes the exclusion issue.
which it excludes potential parents, even if the parents are viable. A reboot of the child immediately
fixes the exclusion issue.
•
CSCsj31387—The Cisco WiSM might reboot and display the following error: “Software Failed on
instruction located at: 0x102eb4d4 (ewsCliDepth+100).”
instruction located at: 0x102eb4d4 (ewsCliDepth+100).”
•
CSCsj33058—The user configuration file for lobby ambassadors has not been checked in.
•
CSCsj37792—A Cisco Aironet 1000 Series Lightweight Access Point might reboot due to an error
in the apHandlePowerMgt function. This problem usually occurs when a large number of clients in
power save mode are continually forced to roam between two access points.
in the apHandlePowerMgt function. This problem usually occurs when a large number of clients in
power save mode are continually forced to roam between two access points.
•
CSCsj44081—Cisco IOS Software has been enhanced with the introduction of additional software
checks to signal improper use of data structures. This feature has been introduced in select Cisco
IOS Software releases published after April 5, 2007.
checks to signal improper use of data structures. This feature has been introduced in select Cisco
IOS Software releases published after April 5, 2007.
Details: The %DATACORRUPTION-1-DATAINCONSISTENCY error message is preceded by a
timestamp: May 17 10:01:27.815 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy
error. The error message is then followed by a traceback.
timestamp: May 17 10:01:27.815 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy
error. The error message is then followed by a traceback.