Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
29
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.112.0
OL-31336-01
Caveats
•
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.
•
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 may not be available for CCX clients on the controller.
association, the CCX Layer 2 roam history may not be available for CCX clients on the controller.
Workaround: None.
•
CSCsh31104—The word channel is misspelled in the message log.
Workaround: None.
•
CSCsh96186—Large IP packets that have been split into multiple fragments might fail to be
reassembled by a 4400 series controller.
reassembled by a 4400 series controller.
Workaround: Redesign the network and reconfigure the communication endpoints to eliminate any
points where such a small fragment could be generated.
points where such a small fragment could be generated.
•
CSCsi00003—If a user enters the wrong username or password more than three times on the Web
Login page, the client is blacklisted, but the Client Excluded page, which tells the user to contact
the administrator, does not appear, and the client disassociates from the network.
Login page, the client is blacklisted, but the Client Excluded page, which tells the user to contact
the administrator, does not appear, and the client disassociates from the network.
Workaround: None.
•
CSCsi06191—After you reboot the controller, the master controller mode is disabled.
Workaround: None.
•
CSCsi13399—The Expiration Timeout for Rogue AP Entries parameter on the Rogue Policies page
applies to both rogue access point entries and rogue client entries. The parameter name should be
changed to reflect both types of entries.
applies to both rogue access point entries and rogue client entries. The parameter name should be
changed to reflect both types of entries.
Workaround: None. This is a cosmetic issue.
•
CSCsi15194—The controller takes a long time to respond to the second message of a four-way
handshake.
handshake.
Workaround: None.
•
CSCsi17242—The API osapiTimeMillisecondsGet() function returns a time value that wraps in less
than 50 days.
than 50 days.
Workaround: None.