Cisco Cisco 2000 Series Wireless LAN Controller Release Notes
23
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.116.21
OL-9542-01
Caveats
•
CSCsc38093—Wireless clients experience poor performance when associated to a 4400 series
controller.
controller.
Workaround: Under investigation.
•
CSCsc40648—Rooftop access points are displayed in the web interface as poletop access points for
more than four minutes, which prevents them from being configured.
more than four minutes, which prevents them from being configured.
Workaround: Configure the access point as a rooftop access point using the controller CLI.
•
CSCsc41313—The Cisco Aironet 1500 Series Lightweight Outdoor Access Points are configured
by default to allow old bridges. When this configuration is enabled, the shared secret key set on the
controller is not passed to the access points, so a few access points might be running on the old key.
If these access points reset or new access points are waiting to join the running network, they may
take a very long time to connect to the network or might not join at all. The default value has been
changed to not allow old bridges to authenticate.
by default to allow old bridges. When this configuration is enabled, the shared secret key set on the
controller is not passed to the access points, so a few access points might be running on the old key.
If these access points reset or new access points are waiting to join the running network, they may
take a very long time to connect to the network or might not join at all. The default value has been
changed to not allow old bridges to authenticate.
Workaround: Configure the controller using this command: config network allow-old-bridge-aps
disable.
disable.
•
CSCsc61004—Poletop access points (PAPs) may not be able to move from one rooftop access point
(RAP) to another if the first RAP goes down. This problem usually occurs if the RAPs are configured
statically at “rooftop” and the PAPs are configured at “poletop.”
(RAP) to another if the first RAP goes down. This problem usually occurs if the RAPs are configured
statically at “rooftop” and the PAPs are configured at “poletop.”
Workaround: Configure Auto mode on all RAPs and PAPs.
•
CSCsd34555—The PC350 client adapter is unable to pass traffic when the access point is not in
protection mode.
protection mode.
Workaround: None at this time.
•
CSCsd35492—The client exclusion feature does not operate correctly when aek keywrap is configured.
Workaround: Use the non-keywrap method.
•
CSCsd36689—Access points in monitor mode do not detect probing clients. These access points do
not track the clients’ RSSI values and do not contribute location information to the Location
Appliance.
not track the clients’ RSSI values and do not contribute location information to the Location
Appliance.
Workaround: Configure the access points for local mode.
•
CSCsd48466—Unless WMM policy is set to Allowed or Required on the WLAN, the 1200 series
access point does not set the DSCP value in the outer LWAPP header for packets that it forwards to
the controller. As a result, the controller cannot set the 1p tag on upstream packets.
access point does not set the DSCP value in the outer LWAPP header for packets that it forwards to
the controller. As a result, the controller cannot set the 1p tag on upstream packets.
Workaround: Set the WMM Policy parameter to either Allowed or Required.
•
CSCse58195—When you upgrade from controller software release 3.0.x.x to 3.2.x.x, any access
control lists (ACLs) that were previously configured or applied to interfaces are removed or
disabled.
control lists (ACLs) that were previously configured or applied to interfaces are removed or
disabled.
Workaround: Before upgrading the controller software, enter the show acl detailed acl_name
command on the controller CLI to see the details of the configured ACL. Then manually apply the
ACL after the upgrade.
command on the controller CLI to see the details of the configured ACL. Then manually apply the
ACL after the upgrade.