Cisco Cisco 2106 Wireless LAN Controller
32
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.0.148.0
OL-31336-01
Caveats
Workaround: Use an external packet capture device to collect packets to and from the controller.
Send these packets to the Technical Assistance Center (TAC) for analysis.
Send these packets to the Technical Assistance Center (TAC) for analysis.
•
CSCsg66040—You might experience intermittent HTTPS access to the controller after a software
upgrade.
upgrade.
Workaround: Perform another software upgrade and downgrade.
•
CSCsg87111—If you create a WLAN with WPA1+WPA2 and conditional web redirect enabled and
then try to change it to 802.1X+conditional web redirect, the MIB browser shows a commit failed
error.
then try to change it to 802.1X+conditional web redirect, the MIB browser shows a commit failed
error.
Workaround: Do not change from WPA1+WPA2+conditional web redirect to 8021.X+conditional
web redirect in one step. Instead, do it in three steps: 1) Disable conditional web redirect and save.
2) Change Layer 2 to 802.1X and save. 3) Configure conditional web redirect and save.
web redirect in one step. Instead, do it in three steps: 1) Disable conditional web redirect and save.
2) Change Layer 2 to 802.1X and save. 3) Configure conditional web redirect and save.
•
CSCsg88704—When you use the default controller setting of 512 for the controller database size,
the following problems may occur:
the following problems may occur:
–
If you attempt to add a MAC address to a very long MAC filter list, the following error message
appears: “Error in creating MAC filter.”
appears: “Error in creating MAC filter.”
–
If you add a large number of users to the local database, some user entries might be silently
ignored.
ignored.
–
If you add SSCs for the access points, at some point no more entries can be added, and the
following error message appears: “Authorization entry does not exist in Controller’s AP
Authorization List.”
following error message appears: “Authorization entry does not exist in Controller’s AP
Authorization List.”
Workaround: Configure a larger value for the controller database, such as 2048.
•
CSCsg92043—The output of the show running-config CLI command cannot be pasted as is into a
different controller because the MAC filters are shown without colons (for example, macfilter add
000b85626640 0). As a result, an incorrect input error message appears when the output is copied
to another controller.
different controller because the MAC filters are shown without colons (for example, macfilter add
000b85626640 0). As a result, an incorrect input error message appears when the output is copied
to another controller.
Workaround: None.
•
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: None.
•
CSCsh15411—When an access point drops the IAPP packet from a CCX client just after
association, the CCX Layer 2 roam history might not be available for CCX clients on the controller.
association, the CCX Layer 2 roam history might not be available for CCX clients on the controller.
Workaround: None.
•
CSCsh31104—The word channel is misspelled in this message log:
Jan 03 16:03:34.699 WPS-4-SIG_ALARM_OFF: AP 00:15:C7:81:24:60 : Alarm OFF, standard
sig NULL probe resp 1, track=per-Mac preced=2 hits=1 slot=0 channle=1
Workaround: None.
•
CSCsh96186—When a 4400 series controller receives IP fragments with an IP payload that is
greater than 32 bytes, it may fail to reassemble the large IP packets that have been split into multiple
fragments.
greater than 32 bytes, it may fail to reassemble the large IP packets that have been split into multiple
fragments.