Cisco Cisco 2106 Wireless LAN Controller Release Notes

Page of 88
 
86
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 6.0.182.0
OL-31336-01
  Caveats
CSCsy06689—The controller might reboot because of an out-of-memory situation, and 
memory-related messages appear in the crash file or message log of the controller.
CSCsy13739—Hybrid-REAP access points might disconnect during the DTLS tunnel with a 
certificate validation error, but the controller shows them as connected with all zeroes in the Time 
Joined field.
CSCsy13791—Cisco 1142 access points send out spurious error messages on initial bootup.
CSCsy16331—The controller network module reboots when the Rogue Access Point Rule Group 
template is pushed from WCS.
CSCsy17668—Cisco 1231 access point radios do not respond to the cmd 1 (0,0,0) core dump 
command.
CSCsy18634—The controller might reboot because of a software failure of the apfOpenDtlSocket 
task.
CSCsy20914—When 802.11 client association and disassociation traps are enabled, the controller 
sends multiple client association traps to WCS for the same client with the same timestamp, which 
causes WCS performance and processing issues.
CSCsy23704—During heavy traffic conditions, 1242 and 1252 access points in hybrid-REAP, 
monitor, or wIPS mode might become stuck in the configuration, image, or join state.
CSCsy24245—WLAN access point group configuration is missing from the output of the show 
run-config
 CLI command.
CSCsy27502—Clients do not get DHCP IP addresses because of the following mobility message 
from the debug mobility handoff enable command: “Mon Mar  9 11:08:03 2009: 
xx:xx:xx:xx:xx:xx Mobility Response: IP 0.0.0.0 code 1, reason 5, PEM State DHCP_REQD, Role 
Unassociated(0).”
CSCsy38629—A 5500 series controller with multiple TACACS+ servers configured might reboot 
when using remote debug commands and if one of the TACACS+ servers goes offline.
CSCsy40717—A controller running software release 5.2 produces the following traceback when the 
service port IP address is changed:
*Mar 13 12:05:02.386: %SIM-6-MACADDR_GET_FAIL: sim.c:1165 Interface 255 source MAC 
address is not found. Using the system MAC FF:FF:FF:00:00:01 instead.
-Traceback:  104e8570 104f10f8 10579a64 108bd698 107a8cc0 10485134 1047a034 10476cc4 
1046940c 10491d64 104be944 10e42470 11033dec
CSCsy48084—Cisco 1220 and 1250 series access points with a single radio in the D1 slot (5 GHz) 
are unable to join a controller running software release 5.2.
CSCsy50654—A controller running software release 4.2.176.0 might experience a slow memory 
leak over a period of 60 days.
CSCsy57573—A controller running software release 5.2.178.0 might reboot because of a software 
failure of the spamReceiveTask.
CSCsy65347—When you configure the QoS profile for a WLAN, the downstream traffic is not 
restricted to the values configured for the per-user bandwidth contracts.
CSCsy65401—A controller running software release 5.2 does not retain the customized web 
authentication settings configured for WLAN Layer 3 security across a reboot. 
CSCsy65598—A controller running software release 5.2.178.0 might experience a decrease in free 
system memory (of less than 15 MB) when a 1000 series access point tries to join.
CSCsy76154—When link aggregation (LAG) is not enabled, packets might be sent on the wrong 
controller port using the wrong port MAC address, which can cause the packets to be lost.