Cisco Cisco 2106 Wireless LAN Controller

Página de 52
 
47
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.112.0
OL-31336-01
  Caveats
CSCsj97747—When using web authentication for guest user access, if the user enters an incorrect 
password and does not disconnect from the access point, the login attempt counts against the number 
allowed for that user ID.
CSCsk14045—The voice TSPEC with TSRS is always rejected by the controller for the Cisco 1010 
access point.
CSCsk14331—QoS profiles and QoS roles cannot be configured for clients that have been 
authenticated using TACACS+.
CSCsk18471—A wireless client associated to a controller sometimes fails to communicate in one 
direction to another client, when the clients are roaming. Therefore, users of voice communication 
clients might experience one-way voice sessions.
CSCsk21287—Wired guest access does not work when an ingress interface IP address is not configured.
CSCsk24403—The following problems might occur when you upgrade the controller to software 
release 4.1.185.0:
When the access points are downloading software from the primary controller, they might be 
misidentified by the controller as rogue access points.
The following message is logged in the controller and the WCS trap logs: “Fake AP or other 
attack may be in progress. Rogue AP count on AP with Base Radio MAC xx:xx:xx:xx:xx:xx 
has exceeded the security warning threshold of (30).” The trap message is usually logged after 
all access points have finished downloading the new software.
CSCsk24974—You cannot use the controller GUI to configure a hexadecimal password for a 
TACACS+ server. Only ASCII passwords are supported.
CSCsk26900—Wireless AppleTalk clients do not get information from wired AppleTalk network 
resources.
CSCsk36855—The controller should not display the IP address, netmask, default gateway, and 
DHCP addresses for guest LAN interfaces.
CSCsk38779—The controller does not respond to a third-party SNMP manager’s snmpbulkwalk 
request.
CSCsk41891—After you upgrade the controller to software release 4.1.171.0 or later, the following 
message is logged by the controller: “CCX-4-MSGTAG012: Mobile xx:xx:xx:xx:xx:xx has 
unsupported CCX version.” This message is misleading. The actual cause of the message is that the 
controller cannot find the access point to which the client is associated.
CSCsk42233—The controller reboots when you open the CDP AP Neighbors page on the controller 
GUI.
CSCsk45030—The controller might generate periodic tracebacks due to unknown phone activity. 
The tracebacks occur for both Cisco 7920 and 7921 IP phones.
CSCsk55844—The class attribute is not sent in an accounting request.
CSCsk61063—A guest LAN with a VLAN interface as ingress can be enabled as an anchor.
CSCsk62403—A controller running software release 4.1.185.0 or 4.0.217.0 might reboot due to a 
failure with the sshpmMainTask.
CSCsk71405—The controller should not set the DF bit when sending packets to WCS. This behavior 
prevents WCS from adding the controller.
CSCsk72885—The controller returns a zero value instead of one or greater for the service port or 
virtual interface.