Cisco Cisco 2106 Wireless LAN Controller

CSCsm32845—The Guest LAN parameter on the Interfaces > Edit page of the controller GUI might 
cause confusion for users because the guest LAN is used for interfaces involved in wired guest 
LANs, not for wireless guest WLANs.

CSCso88340—A lightweight IOS access point that has not been configured with a default domain 
suffix (for example, from its DHCP server) might attempt to resolve the CISCO-LWAPP-
CONTROLLER domain name when it boots up by first attempting to resolve CISCO-LWAPP-
CONTROLLER and then attempting to resolve CISCO-LWAPP-CONTROLLER.cisco.com.

CSCsq06451—If you configure a guest LAN and map the ingress interface to a guest LAN interface, 
you cannot change the mapping to None using the controller GUI.

CSCsq13610—WCS allows special characters in the primary, secondary, and tertiary controller 
names and access point names, but the controller does not, making the overall behavior inconsistent. 

CSCsr89694—On Cisco WiSM controllers running software release 4.2.130.0, trap logs are 
generated indicating that the control path between two random mobility members is down. About 
10 to 20 minutes later the control path comes back up.

CSCsu52837—Preauthenticated clients cannot reach web-authenticated clients on the same WLAN.

CSCsv42697—The radio interface in an 1140 or 1250 series access point might intermittently 
display one or more of the following symptoms:

The show controller CLI command might show that beacons and probes are disabled.

This syslog message might appear with tracebacks: “Transmitter seems to have stopped.”

This syslog message might appear with tracebacks: “Command 16 timeout.”

Radio core dumps might be left in the flash.

CSCsv67671—When an 1140 series access point is in autonomous or hybrid-REAP mode and 
SSIDs are mapped to VLANs that do not exist on the controller, the access point produces tracebacks 
and reboots continuously. 

CSCsv77658—A 1250 or 1520 series access point no longer reboots because the watchdog timer 
expired.

CSCsw27841—The controller allows you to configure multiple untagged VLAN interfaces on the 
same physical port.

CSCsw75392—If you configure a WLAN to simultaneously support WPA+TKIP, WPA+AES, and 
WPA2+AES, 802.11n clients that are configured for WPA2+PSK or WPA2+802.1X can now 
associate at all available data rates.

CSCsw84822—An snmpWalk of the clcrRoamReasonReportTable to any controller connected with 
some clients returns an infinite number of records and the following error message: “Error: OID not 
increasing.”

CSCsx41062—Controllers sometimes reject valid NTP packets and label them spurious.

CSCsx49415—After some time, 1230 series access points stop servicing clients, and the following 
message appears on the controller: “%CAPWAP-3-ERRORLOG: Could not allocate buffer for 
sending data transfer request.”

CSCsx52830—A 1250 series access point radio might stop providing client access. The radio seems 
to lose client connectivity, and a reboot of the access point brings the clients back up.

CSCsx57611—The 2.4-GHz radio transmitter in a 1250 series access point might fail, stop, and 
reset.

CSCsx70686—When Rogue Location Detection Protocol (RLDP) and rogue containment are 
enabled with a large number of rogues, the beacons and the probes on a 1250 series access point 
become disabled, and the access point must be rebooted.