Cisco Cisco 2106 Wireless LAN Controller
33
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.0.148.0
OL-31336-01
Caveats
Workaround: Redesign the network or reconfigure the communications endpoints to eliminate any
points in which such a small fragment would be generated.
points in which such a small fragment would be generated.
•
CSCsi00003—If you enter the wrong username or password more than three times on the web login
page, the client is blacklisted. The Client Excluded page, which instructs you to contact the
administrator, does not appear, and the client disassociates from the network.
page, the client is blacklisted. The Client Excluded page, which instructs you to contact the
administrator, does not appear, and the client disassociates from the network.
Workaround: None.
•
CSCsi06191—Customers who have large deployments use master controller mode to easily locate
newly joined lightweight access points on the network so they can prime them and allow them to
join their respective controller. However, when the controller is rebooted, this feature is disabled.
newly joined lightweight access points on the network so they can prime them and allow them to
join their respective controller. However, when the controller is rebooted, this feature is disabled.
Workaround: None.
•
CSCsi15194—The controller might take a long time to respond to a message during a four-way
handshake.
handshake.
Workaround: None.
•
CSCsi15249—Hybrid-REAP access points perform an unnecessary channel scan when entering
standalone mode.
standalone mode.
Workaround: None.
•
CSCsi17242—The API osapiTimeMillisecondsGet() function returns a time value that wraps in less
than 50 days.
than 50 days.
Workaround: None.
•
CSCsi26248—You might lose connectivity when adding or recovering a second link aggregation
(LAG) link.
(LAG) link.
Workaround: None.
•
CSCsi29262—The access point does not beacon an overridden WLAN with a 32-character SSID.
Workaround: None.
•
CSCsi30541—Loss of connectivity to the management interface occurs when you add a new
dynamic interface and the configured DHCP server on all other interfaces is in the new dynamic
interface subnet and the new interface has a shorter mask than the other interfaces.
dynamic interface and the configured DHCP server on all other interfaces is in the new dynamic
interface subnet and the new interface has a shorter mask than the other interfaces.
Workaround: Configure a 10/24 interface or a different 10/16 subnet such that the new dynamic
interface does not contain the DHCP server IP address currently defined on all interfaces.
interface does not contain the DHCP server IP address currently defined on all interfaces.
•
CSCsi40354—Traffic stream metrics (TSM) information is not sorted chronologically on the
controller GUI.
controller GUI.
Workaround: None.
•
CSCsi57300—A controller running software release 4.1.158.x might reboot when you execute the
show running-config CLI command.
show running-config CLI command.
Workaround: None.
•
CSCsi72324—A service port with IP address 0.0.0.0 responds to an ARP for the AP-manager
interface.
interface.
Workaround: Unplug the service port and reconfigure it on the correct subnet.
•
CSCsi72578—After you set up the mobility anchor feature between two controllers, the client does
not successfully connect to the specified anchor controller if the WLAN QoS profile is set to Bronze.
not successfully connect to the specified anchor controller if the WLAN QoS profile is set to Bronze.
Workaround: Change the WLAN QoS profile on both the internal controller and the anchor
controller to Silver.
controller to Silver.