Cisco Cisco 2106 Wireless LAN Controller
44
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.185.0
OL-31336-01
Caveats
•
CSCsj47539—Controllers sometimes log the following message:
APF-1-ROGUE_AP_ADD_FAILED: Failed to add the rogue AP xx:xx:xx:xx:xx:xx. insertion
failed.
failed.
•
CSCsj50374—When you enter the config network arpunicast enable command on the controller
CLI, a broadcast ARP frame may be forwarded back and forth at a very high rate between two or
more controllers in a mobility group, resulting in a broadcast storm.
CLI, a broadcast ARP frame may be forwarded back and forth at a very high rate between two or
more controllers in a mobility group, resulting in a broadcast storm.
•
CSCsj56145—4400 series controllers sometimes crash after upgrding to the 4.1.171.0 release.
•
CSCsj57115—If the controller fails with multicast enabled, access points might enter an infinite
debug loop.
debug loop.
•
CSCsj67514—The virtual interface of the Cisco WiSM accepts connections on ports 22, 23, and
443. ACLs cannot be used to block this traffic, which makes it possible for remote attackers to
conduct brute-force password cracking or denial-of-service attacks. This problem occurs on WiSMs
running controller software release 4.1.170 with Mgmt Via Wireless disabled.
443. ACLs cannot be used to block this traffic, which makes it possible for remote attackers to
conduct brute-force password cracking or denial-of-service attacks. This problem occurs on WiSMs
running controller software release 4.1.170 with Mgmt Via Wireless disabled.
•
CSCsj69233—Cisco Wireless LAN Controllers (WLC) contain multiple vulnerabilities in the
handling of Address Resolution Protocol (ARP) packets that could result in a denial of service (DoS)
in certain environments.
handling of Address Resolution Protocol (ARP) packets that could result in a denial of service (DoS)
in certain environments.
Cisco is notifying customers and partners and has made free software available to address these
vulnerabilities for affected customers. There are workarounds available to mitigate the effects of
these vulnerabilities.
vulnerabilities for affected customers. There are workarounds available to mitigate the effects of
these vulnerabilities.
An advisory is posted at this URL:
•
CSCsj75211—Changing the rate of the mesh backhaul affects the 4.9-GHz throughput of the
workgroup bridge (WGB). The default rate for the mesh backhaul is 18 Mbps, which results in
11.4-Mbps throughput for the WGB. As the mesh backhaul rate increases, the WGB throughput also
increases.
workgroup bridge (WGB). The default rate for the mesh backhaul is 18 Mbps, which results in
11.4-Mbps throughput for the WGB. As the mesh backhaul rate increases, the WGB throughput also
increases.
•
CSCsj78813—A mobility anchor event occurs when an unauthenticated client with web
authentication enabled roams among controllers using the same WLAN. The VLAN to which the
WLAN is associated is different on the controllers. After the client roams, it never receives a login
prompt, and the browser times out.
authentication enabled roams among controllers using the same WLAN. The VLAN to which the
WLAN is associated is different on the controllers. After the client roams, it never receives a login
prompt, and the browser times out.
•
CSCsj82564—The 7921 phone does not work with the AP1000 when WPA2-AES security and
WMM are enabled on the WLAN.
WMM are enabled on the WLAN.
•
CSCsj83371—After you upgrade a controller to software release 4.1.181.0 or reboot a controller
that is running this version of software, the RF signals in the coverage area might be unusually weak
for some time because RRM initializes radios to their lowest transmit level rather than to their
highest level. This problem occurs when the controller is configured for the RRM automatic power
level assignment. In controller software release 4.1.185.0, RRM initializes radios to the previous
power level.
that is running this version of software, the RF signals in the coverage area might be unusually weak
for some time because RRM initializes radios to their lowest transmit level rather than to their
highest level. This problem occurs when the controller is configured for the RRM automatic power
level assignment. In controller software release 4.1.185.0, RRM initializes radios to the previous
power level.
•
CSCsj90453—Clients sometimes fail to associate to controllers running software release 4.1.181.