Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
25
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.176.0
OL-31336-01
Caveats
Workaround: Configure a larger value for the controller database, such as 2048.
•
CSCsg95474—Lightweight access points do not queue disassociation messages, causing the Cisco
7921 phone to remain in a registering loop. This problem occurs when you change the data rate on
the access point.
7921 phone to remain in a registering loop. This problem occurs when you change the data rate on
the access point.
Workaround: Power cycle the 7921 phone.
•
CSCsh11086—If you press Ctrl-S and Ctrl-Q to pause and restart the output of a command such
as debug dot1x event enable, the controller reboots.
as debug dot1x event enable, the controller reboots.
Workaround: Do not stop the console using Ctrl-S.
•
CSCsh15411—When an access point drops the IAPP packet from a CCX client just after
association, the CCX Layer 2 roam history may not be available for CCX clients on the controller.
association, the CCX Layer 2 roam history may not be available for CCX clients on the controller.
Workaround: None.
•
CSCsh31104—The word channel is misspelled in the message log.
Workaround: None.
•
CSCsi06191—After you reboot the controller, the master controller mode is disabled.
Workaround: None.
•
CSCsi13399—The Expiration Timeout for Rogue AP Entries parameter on the Rogue Policies page
applies to both rogue access point entries and rogue client entries. The parameter name should be
changed to reflect both types of entries.
applies to both rogue access point entries and rogue client entries. The parameter name should be
changed to reflect both types of entries.
Workaround: None. This is a cosmetic issue.
•
CSCsi17242—If a controller starts a timer (such as reauthentication or keylife time) after running
for approximately 52 days, the timer might take a long time to fire (up to another 52 days).
for approximately 52 days, the timer might take a long time to fire (up to another 52 days).
Workaround: Clean up the timers. If the problem is related to the client, deauthenticate the client to
clean the timer. If the problem is related to the WLAN, such as a broadcast key update, disable and
then re-enable the WLAN.
clean the timer. If the problem is related to the WLAN, such as a broadcast key update, disable and
then re-enable the WLAN.
•
CSCsi26248—You might lose connectivity when adding or recovering a second link aggregation
(LAG) link.
(LAG) link.
Workaround: Recover the LAG link when service is not in use. You might also want to consider not
using this type of configuration.
using this type of configuration.
•
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.
•
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 when the WLAN QoS profile is set to
bronze.
not successfully connect to the specified anchor controller when the WLAN QoS profile is set to
bronze.