Cisco Cisco 2106 Wireless LAN Controller Release Notes
27
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 6.0.182.0
OL-31336-01
Important Notes for Controllers and Non-Mesh Access Points
EDCA CLI Commands
The following enhanced distributed channel access (EDCA) CLI command appears in controller
software release 6.0.182.0, but this command is not configurable and cannot be used:
software release 6.0.182.0, but this command is not configurable and cannot be used:
config advanced {802.11a | 802.11b} edca-parameters custom profile_name {aifs | ecwmin | ecwmax
| txop} value
| txop} value
Band Select and Load Balancing CLI Commands
The config band-select and config wlan band-select CLI commands appear in controller software
release 6.0.182.0, but they are not supported and should not be used. Also, you can ignore the Band
Select Stats information in the output of the show ap stats {802.11a | 802.11b} Cisco_AP command.
release 6.0.182.0, but they are not supported and should not be used. Also, you can ignore the Band
Select Stats information in the output of the show ap stats {802.11a | 802.11b} Cisco_AP command.
The config load-balancing denial and config wlan load-balance CLI commands appear in controller
software release 6.0.182.0, but they are not supported and should not be used. Also, you can ignore the
Denial Count information in the output of the show load-balancing command.
software release 6.0.182.0, but they are not supported and should not be used. Also, you can ignore the
Denial Count information in the output of the show load-balancing command.
Inter-Release Controller Mobility
When controllers in the mobility list are running different software releases (such as 4.2, 5.0, 5.1, 5.2,
and 6.0), Layer 2 or Layer 3 client roaming is not supported between them. It is supported only between
controllers running the same release.
and 6.0), Layer 2 or Layer 3 client roaming is not supported between them. It is supported only between
controllers running the same release.
Guest tunneling works only between controllers running the same software release or between
controllers running software release 4.2 and controllers running any later software release (for example,
4.2 to 5.0, 4.2 to 5.1, 4.2 to 5.2, or 4.2 to 6.0). Guest tunneling does not work among controllers running
other combinations of software.
controllers running software release 4.2 and controllers running any later software release (for example,
4.2 to 5.0, 4.2 to 5.1, 4.2 to 5.2, or 4.2 to 6.0). Guest tunneling does not work among controllers running
other combinations of software.
RLDP Limitations in This Release
Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue
access points that are connected to your wired network. In this software release, RLDP operates with
these limitations:
access points that are connected to your wired network. In this software release, RLDP operates with
these limitations:
•
RLDP detects rogue access points that are configured for open authentication.
•
RLDP detects rogue access points that use a broadcast BSSID (that is, the access point broadcasts
its SSID in beacons).
its SSID in beacons).
•
RLDP detects only rogue access points that are on the same network. In other words, if an access
list in the network prevents the sending of RLDP traffic from the rogue access point to the controller,
RLDP does not work.
list in the network prevents the sending of RLDP traffic from the rogue access point to the controller,
RLDP does not work.
•
RLDP does not work on 5-GHz dynamic frequency selection (DFS) channels.
•
If the automatic RLDP attempt does not detect the rogue (due to a noisy RF environment, for
example), the controller does not retry. However, you can initiate RLDP manually on a rogue at any
time.
example), the controller does not retry. However, you can initiate RLDP manually on a rogue at any
time.
Also, in controller software release 6.0, the rogue containment packet transmission times have changed
as follows:
as follows:
•
For monitor mode, rogue containment deauthentication packets are still sent at 100-msec intervals.