Cisco Cisco 2106 Wireless LAN Controller
42
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.185.0
OL-31336-01
Caveats
•
CSCsi75918—A Windows client running WPA2 with LEAP or PEAP might not be pingable from
the controller when it is associated to a 1020 access point.
the controller when it is associated to a 1020 access point.
•
CSCsi77945—When a controller is running software release 4.1.171.0 with local EAP-FAST
enabled, Cisco 7920 IP phones might not join the network when using EAP-FAST WPA/TKIP and
local EAP authentication.
enabled, Cisco 7920 IP phones might not join the network when using EAP-FAST WPA/TKIP and
local EAP authentication.
Note
The 7920 phones also need to have a fix for CSCsj11323 in order to work with EAP-FAST.
•
CSCsi78460—The available admission capacity (AAC) of the QBSS Load IE is not set in beacons
or probe responses. The AAC is set to zero. Clients with call admission control (CAC) enabled might
not associate to an access point that sends an AAC value of zero because the clients might check the
AAC before sending ADDTS requests and associate/re-associate request. The clients might judge
that there are no more calls being admitted to the access point, even when the access point has the
capacity to admit new traffic. This issue occurs for wireless clients that check the AAC before
sending an ADDTS request.
or probe responses. The AAC is set to zero. Clients with call admission control (CAC) enabled might
not associate to an access point that sends an AAC value of zero because the clients might check the
AAC before sending ADDTS requests and associate/re-associate request. The clients might judge
that there are no more calls being admitted to the access point, even when the access point has the
capacity to admit new traffic. This issue occurs for wireless clients that check the AAC before
sending an ADDTS request.
•
CSCsi79857—Controllers sometimes report messages stating unable to add new rogue AP entry for
access points that are joined to controllers that are in the mobility group.
access points that are joined to controllers that are in the mobility group.
•
CSCsi80421—On some controllers, the debug lwapp packet enable CLI command does not show
any output.
any output.
•
CSCsi81630—2006 controllers sometimes reboot when RLDP is enabled.
•
CSCsi84524—Access points in HREAP mode sometimes send DHCP requests in LWAPP with local
switching enabled.
switching enabled.
•
CSCsi84986—Some mesh access points fail to join the root access point after upgrading to software
release 4.1.171.0.
release 4.1.171.0.
•
CSCsi86800—Controllers sometimes process LWAPP traffic on promiscuous mode.
•
CSCsi91600—Microsoft Internet Explorer sometimes redirects to the controller login page with
webauth.
webauth.
•
CSCsi95068—The controller GUI might report a value of zero for the signal-to-noise ratio (SNR)
while the show mesh neigh summary Cisco_AP CLI command reports the correct SNR value.
while the show mesh neigh summary Cisco_AP CLI command reports the correct SNR value.
•
CSCsi97452—When a Cisco 7921 phone associates to a WLAN or SSID that is configured on a
2006 controller, the controller might become unresponsive and eventually reboot.
2006 controller, the controller might become unresponsive and eventually reboot.
•
CSCsi99388—The config msglog level security CLI command has been removed in controller
software release 4.1.185.0. Only these config msglog level ? commands are now supported:
software release 4.1.185.0. Only these config msglog level ? commands are now supported:
–
critical—Critical hardware or software failure.
–
error—Noncritical software error.
–
warning—Unexpected software events.
–
verbose—Significant system events.
•
CSCsi99569—The Number of Clients field on the Rogue APs page of the controller GUI might not
accurately reflect the number of associated rogue clients.
accurately reflect the number of associated rogue clients.
•
CSCsj02639—Remote authentication does not work over wireless mesh network connections in
some situations. Authentication for mesh networks should always be done locally on the controller.
Enter the following CLI command to enable local authentication on the controller: config mesh
local-auth enable and verify that the MAC addresses for all mesh access points are entered into the
MAC filter list.
some situations. Authentication for mesh networks should always be done locally on the controller.
Enter the following CLI command to enable local authentication on the controller: config mesh
local-auth enable and verify that the MAC addresses for all mesh access points are entered into the
MAC filter list.