Cisco Cisco 2106 Wireless LAN Controller

CSCsu04143–In some cases, the radio resource manager (RRM) would over allocate timers, not 
allowing new timers to be allocated. Client association and rogue detection were affected.

Controller often would report the following message:

Aug 14 07:05:37.297 timerlib.c:460 OSAPI-0-TIMER_CREATE_FAILED: Failed to create a 

timer.

CSCsv04340–When a 1510 configured as a MAP, was deployed in a multi-hop mesh network 
operating with 4.1.192.22M, it would reset after several days of uptime.

CSCsw73052–Ease calculation did not work correctly causing a 1510 MAP to remain with a 
secondary parent with a lower linkSNR and higher hop count than its original parent after 
connectivity to its original parent was restored. Release 4.1.192.35M was operating in the network.

For DFS channels, the off channel adjacencies that are updated depend on the map receiving a 
beacon in the 60 ms interval, that it stays off channel when 802.11b/g scanning is enabled. If the 
adjacencies are not updated, the map might not roam to neighbors on a different channel.

CSCsx31684–The 802.11a radio was shown as disabled for the -N domain (Brazil) even though the 
controller was configured to work in the Brazil country code. Problem was resolved by updating 
country code tables in the software.

CSCsy31659–A 1510 did not send a beacon from the 5GHz band when client access was enables on 
the backhaul. However, the 1510 did respond to probe requests and clients that were actively 
scanning were able to associate. Problem was seen in release 4.1.192.35M.

CSCsy52216–A 1510 was not able to authenticate with a local controller or external RADIUS server 
when using a MAC address to authenticate.

CSCsy55568–When the access point unicast syslog feature was configured, mesh access points 
would disassociate from the controller.

CSCsz32172– The LockAsset error could occur on WiSM blades that were heavily loaded with 
access points and clients.

The following caveats represent those bugs that are closed and not actively being investigated but might 
still represent active conditions in a product. Workarounds are provided. 

CSCsm80803–When a wired client is connected to a workgroup bridge using WPAv1+TKIP (PSK), 
it loses its association with a 1510. 

Bug was closed because workaround is effective. Code changes would be substantial.

Workaround: Configure WPAv2+AES.

If you need information about a specific caveat that does not appear in these release notes, you can use 
the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:

(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not 
yet have a customer-visible description, or the defect might be marked Cisco Confidential.)