Cisco Cisco 2106 Wireless LAN Controller Release Notes
31
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.181.0
OL-31336-01
Caveats
•
CSCsg77609—A mesh access point may disconnect from the controller during a TCP or UDP
stream from a wireless or Ethernet client in a hidden node situation. This disconnect can occur when
a mesh access point is a hidden node to another node. Even though the LWAPP control packets that
maintain the LWAPP connection between the controller and access point are attempted with a higher
802.11 priority, the hidden node may interfere with a node’s traffic and subsequent LWAPP control
packets.
stream from a wireless or Ethernet client in a hidden node situation. This disconnect can occur when
a mesh access point is a hidden node to another node. Even though the LWAPP control packets that
maintain the LWAPP connection between the controller and access point are attempted with a higher
802.11 priority, the hidden node may interfere with a node’s traffic and subsequent LWAPP control
packets.
Workaround: Use the new routing around interference feature to create a secondary backhaul to
reduce the hidden node problem. The appropriate CLI command is config mesh
secondary-backhaul enable force-same-secondary-channel.
reduce the hidden node problem. The appropriate CLI command is config mesh
secondary-backhaul enable force-same-secondary-channel.
•
CSCsg88380—When the source access point is connected to one controller and the destination
access point is connected to a second controller and both controllers have the same MAC filter list,
the mesh link test fails to run between the two access points.
access point is connected to a second controller and both controllers have the same MAC filter list,
the mesh link test fails to run between the two access points.
Workaround: Move both access points to one controller by setting the same primary controller on
both access points.
both access points.
•
CSCsh13494—If you set the session timeout for an 802.1x WLAN to some value and then check the
session timeout through the controller CLI, the timeout always shows as infinity. However, the
controller GUI displays the correct value.
session timeout through the controller CLI, the timeout always shows as infinity. However, the
controller GUI displays the correct value.
Workaround: None. The functionality is not affected as the session times out after the specified
value.
value.
•
CSCsh13928—In busy RF environments in large deployments, access points may disconnect from
the controller intermittently.
the controller intermittently.
Workaround: Disable radio resource management (RRM) and statically set the channels and power
levels.
levels.
•
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.
•
CSCsh29597—Reauthentication occurs if you click any link on the controller GUI after using a
one-time password to authenticate management users.
one-time password to authenticate management users.
Workaround: Do not use a one-time password to authenticate management users.
•
CSCsh31104—The word channel is misspelled in the message log.
Workaround: None.
•
CSCsh54247—You cannot perform the following logging functions on the controller:
–
Setting the system logging severity to filter out-going syslog messages
–
Setting the syslog facility
–
Configuring multiple syslog servers on the controller
Workaround: None.
•
CSCsh61934—A client connecting to the LWAPP architecture using reverse-ARP may fail to obtain
an IP address.
an IP address.
Workaround: None.