Cisco Cisco 2106 Wireless LAN Controller
68
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.1.151.0
OL-31336-01
Caveats
•
CSCso71603—When a client moves from one controller to a 2106 controller on the same subnet,
the client cannot pass traffic for 5 minutes.
the client cannot pass traffic for 5 minutes.
•
CSCso81687—A forwarding failure occurs when an orphan packet is sent to the CPU using the slow
path. The following message appears on the console: “NP3400_interrupt.c 3663: In
‘NP3400_BSN_process_frame_rx’ Unknown packet type 0.”
path. The following message appears on the console: “NP3400_interrupt.c 3663: In
‘NP3400_BSN_process_frame_rx’ Unknown packet type 0.”
•
CSCso81725—The controller’s broadcast module is replicating CDP packets to all connected access
points even if multicast is disabled. In addition, the controller is replicating broadcast orphan
packets from a client even when multicast and broadcast are disabled.
points even if multicast is disabled. In addition, the controller is replicating broadcast orphan
packets from a client even when multicast and broadcast are disabled.
•
CSCso84256—During CCKM roaming, the following misleading debug message might appear:
“Creating a new PMK Cache Entry for station.”
“Creating a new PMK Cache Entry for station.”
•
CSCso89810—When you downgrade a controller from software release 5.0.148.x to 4.2.112.0, the
LWAPP mode automatically changes from Layer 3 to Layer 2, and the AP-manager disappears and
cannot be recreated. This problem is resolved in controller software release 4.2.130.0, so you can
successfully downgrade from software release 5.0.148.x to 4.2.130.0.
LWAPP mode automatically changes from Layer 3 to Layer 2, and the AP-manager disappears and
cannot be recreated. This problem is resolved in controller software release 4.2.130.0, so you can
successfully downgrade from software release 5.0.148.x to 4.2.130.0.
•
CSCso90721—When the controllers in a Cisco WiSM are running software release 4.1.112.0, they
might reboot three times due to a software failure of the dtlArpTask software watchdog.
might reboot three times due to a software failure of the dtlArpTask software watchdog.
•
CSCso95257—Clients might time out during WPA2-PSK roaming.
•
CSCso97157—A memory leak might occur in the mobility code of controller software release 4.2.
•
CSCso98021—The software watchdog needs to be implemented in the 2106 controller.
•
CSCso98915—A controller running software release 4.0.219.0 or 4.2.112.0 might reboot during the
emweb process.
emweb process.
•
CSCsq08062—A TACACS+ connection initiated from the controller to the TACACS+ server
sometimes times out in 0.5 seconds.
sometimes times out in 0.5 seconds.
•
CSCsq13407—The dot1x tree might become corrupted as the tree lock is not being acquired prior
to entries being deleted from the tree.
to entries being deleted from the tree.
•
CSCsq31662—The controller reboots after you upgrade from software release 4.2.61.0 to 4.2.112.0.
•
CSCsq51733—The controller drops BOOTP packets from the wireless client.
•
CSCsq59283—The controller SNMP does not allow an access point group name or description of
32 characters.
32 characters.
If You Need More Information
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:
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.)
yet have a customer-visible description, or the defect might be marked Cisco Confidential.)