Cisco Cisco 2106 Wireless LAN Controller
33
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.185.0
OL-31336-01
Caveats
•
CSCsh73171—When you enable CCKM on the controller for use with CB21AG client adapters,
some CCKM configuration settings cause the client to send an association request in the middle of
CCKM, thereby resulting in full authentication rather than CCKM. See the
some CCKM configuration settings cause the client to send an association request in the middle of
CCKM, thereby resulting in full authentication rather than CCKM. See the
for details on which CCKM configuration settings do
and do not operate properly.
Workaround: Configure WPA + TKIP + authentication key management CCKM. This setting allows
the client to roam successfully without performing full RADIUS authentication.
the client to roam successfully without performing full RADIUS authentication.
•
CSCsh98559—CPU ACLs do not work for EoIP packets and DHCP received on the distribution
system port.
system port.
Workaround: None.
•
CSCsi05147—Path loss reports are not appearing on the controller.
Workaround: None.
•
CSCsi06037—You can configure peer-to-peer blocking mode only globally. You cannot configure
it on a per-WLAN basis. In addition, this feature does not block ARP packets between wireless
clients on the same WLAN, only IP packets.
it on a per-WLAN basis. In addition, this feature does not block ARP packets between wireless
clients on the same WLAN, only IP packets.
Workaround: None.
•
CSCsi06381—The mesh link test produces no results or returns 0 or infinity as values. This problem
happens when the test is being performed on a heavily congested link or in a noisy environment.
happens when the test is being performed on a heavily congested link or in a noisy environment.
Workaround: Rerun the link test. If this does not help, rerun the test at a lower packet or data rate.
•
CSCsi06849—When the available bandwidth becomes a negative number and the corresponding
voice bandwidth in use is above 100%, roam calls [with 7921 traffic specifications (TSPECs) sent
as part of the re-association packets] are accepted even when the roam bandwidth is exhausted.
voice bandwidth in use is above 100%, roam calls [with 7921 traffic specifications (TSPECs) sent
as part of the re-association packets] are accepted even when the roam bandwidth is exhausted.
Workaround: None.
•
CSCsi07934—Efficient multicast to 802.11 clients is not supported on mesh access points.
Therefore, you should not turn on multicast mode on the controller when it needs to service mesh
access points. If you do, the mesh access points may start disconnecting due to issues with queue
overflow at the MAPs. This issue applies to all controller commands starting with:
Therefore, you should not turn on multicast mode on the controller when it needs to service mesh
access points. If you do, the mesh access points may start disconnecting due to issues with queue
overflow at the MAPs. This issue applies to all controller commands starting with:
config network multicast
Workaround: If you need to turn on the controller multicast mode for non-mesh access points,
service mesh access points on a different controller than the one used for non-mesh access points.
service mesh access points on a different controller than the one used for non-mesh access points.
•
CSCsi11229—Clients may disassociate from a mesh access point even though the access point
seems to be up and running. This problem happens when client entries on the access point are not
being aged out in a timely manner, resulting in a high client count (greater than 100) and client
association problems.
seems to be up and running. This problem happens when client entries on the access point are not
being aged out in a timely manner, resulting in a high client count (greater than 100) and client
association problems.
Use the following commands on the controller to display the number of users on each radio on an
access point:
access point:
show ap stats 802.11b Cisco_AP
show ap stats 802.11a Cisco_AP
Workaround: None.
•
CSCsi15588—Wireless-to-wireless calls made using a 7921 phone may become disconnected after
a few minutes. This issue occurs when bidirectional traffic specifications (TSPECs) are present and
the inactivity timer becomes activated due to inactivity in any one direction.
a few minutes. This issue occurs when bidirectional traffic specifications (TSPECs) are present and
the inactivity timer becomes activated due to inactivity in any one direction.
Workaround: Change the default state of the inactivity timer to Off.