Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
30
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.2.193.0
OL-31336-01
Caveats
•
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—After a failed link aggregation (LAG) link recovers, you might lose connectivity for
approximately 30 seconds.
approximately 30 seconds.
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.
•
CSCsi27596—The controller lacks a supported way to configure the broadcast key rotation interval.
Instead, it is hardcoded to a group key rotation interval of 3600 seconds (1 hour).
Instead, it is hardcoded to a group key rotation interval of 3600 seconds (1 hour).
Workaround: On the console, configure the hidden command devshell
dot1xUpdateBroadcastRekeyTimer(seconds). This command does not work in an SSH or Telnet
session and does not survive a reboot.
dot1xUpdateBroadcastRekeyTimer(seconds). This command does not work in an SSH or Telnet
session and does not survive a reboot.
Example:
(Cisco Controller) >devshell dot1xUpdateBroadcastRekeyTimer(86400)
value = 0 = 0x0
•
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.
•
CSCsi54588—Some 802.1X error messages have inadequate descriptions or incorrect severity
levels. For example, the following messages, which can be caused by an incorrectly configured
client, have a severity level of 1 when they should have a severity level of 3. As a result, they are
logged even when the logging level is set to Critical.
levels. For example, the following messages, which can be caused by an incorrectly configured
client, have a severity level of 1 when they should have a severity level of 3. As a result, they are
logged even when the logging level is set to Critical.
–
DOT1X-1-MAX_EAPOL_KEY_RETRANS_FOR_MOBILE
–
DOT1X-1-ABORT_AUTH
Workaround: Make sure that clients are correctly configured to minimize error logging.
•
CSCsi62915—Static IP wireless devices are not shown on the controller until they send a packet.
The IP address information should appear on the MAC Filtering > Details page of the controller GUI
and in the output of the show run-config CLI command.
The IP address information should appear on the MAC Filtering > Details page of the controller GUI
and in the output of the show run-config CLI command.
Workaround: To see static IP wireless devices in the controller’s local MAC filter list, enter a CLI
command similar to the following:
command similar to the following:
config macfilter add 00:01:02:03:04:05 3 200 “test prt” 192.168.200.10
•
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.
•
CSCsi73129—When you attempt to upgrade the controller using an associated wireless client as the
TFTP or FTP server, the upgrade fails.
TFTP or FTP server, the upgrade fails.
Workaround: Place the server on a client that is not associated to the controller.