Cisco Cisco 2106 Wireless LAN Controller

The following caveats are resolved in 4.2.176.51M.

CSCsk68719–On the controller GUI, when you changed and applied data rates on a mesh access 
point radio you were prompted with a window that warned you of a pending reboot. When using the 
CLI, no reboot was necessary and no reboot prompt appeared. Workaround was to use the CLI to 
change the data rates to avoid the reboot.

CSCsl15370–Mesh access points were unable to associate with controllers whose names were of 
varying string lengths. The workaround was to have the same name length for the primary, 
secondary, and tertiary controllers.

CSCsl40587–Channel 192 could not be set on a 1510.

CSCsl90654–When background scanning was enabled, sometimes RAPs would get into a state in 
which they could not transmit, and network would not be able to communicate. This occurred only 
in large networks.

CSCsl91623–The 1510 was not properly advertising its SSID. There was confusion as to which 
radio (802.11a or 802.11b/g) it was transmitted on.

CSCsl91679–A reboot of mesh access points was often required to reset adjacency counters or the 
adjacency. Changes were added to the code 

CSCsm25938–The 1510 could not be deployed in South Africa (country code-ZA). The 802.11a 
radio was in a disabled state.

CSCsm62772–A controller running 4.1.190.5 or 4.1.191.24M software might crash unexpectedly 
due to an SNMPTask.

CSCsm73147– When a configured country code did not support the 5-GHz band (802.11a), an UP 
condition for both the 2.4Ghz and 5Ghz radio of a 1510 mistakenly displayed. As an unsupported 
band, no data should display for the 5-GHz band and MAPs could not join the RAP via that band.

CSCso17430–In some cases, mesh networks with workgroup bridges (WGB) connections might 
experience lower throughput. This lower throughput is mostly seen when a series 1300 access point 
is configured as the WGB and its first connection within the mesh network is a 1510 mesh access 
point.

CSCso28047–In release 04.1.191.24M, a controller might display the following message when 
polled by SNMP (generally Cisco WCS) instead of generating an error message for each access 
point every five minutes:

/tmp/gate/lvl7dev/src/mgmt/snmp/snmp_sr/src/snmpd/unix/k_mib_cisco_lwapp_ap.c:144 

SNMP-4-MSGTAG008: Failed to get cLLwappJoinTakenTime for AP XX:XX:XX:XX:XX, API return 

code: 1.

XX:XX:XX:XX:XX would be the mac address of each AP.

The problem was not service affecting and could be ignored.

CSCsq15736–All 1510s were advertising an incorrect transmit power (through their dynamic 
transmit power control (DTPC) information element (IE) beacons) to clients. (Clients use this 
information to automatically adjust their transmit power to the same level as the access point). This 
caused the client to set their power too low. Software was modified to report the correct transmit 
power of the access point in the DTPC IE beacon.

CSCsq17074–When a user was using the controller GUI to access or modify an access point that 
was unreachable, a crash on the emWebtask occurred. No crash file was generated.