Cisco Cisco 2106 Wireless LAN Controller Release Notes

Page of 44
 
5
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 6.0.188.0
OL-31336-01
  New Features
Note
Off Chanel Scanning is essential to the operation of RRM, which gathers information about 
alternate channel choices such as noise and interference. Additionally, Off Channel Scanning is 
responsible for rogue detection. Devices that need to defer Of f Channel Scanning should use 
the same WLAN as often as possible. If there are many of these devices (and the possibility 
exists that off-channel scanning could be completely disabled by the use of this feature), you 
should implement an alternative to local AP Off Channel Scanning, such as monitor access 
points, or other access points in the same location that do not have this WLAN assigned.
Assignment of a QoS policy (bronze, silver, gold, and platinum) to a WLAN affects how packets are 
marked on the downlink connection from the access point regardless of how they where received on the 
uplink from the client. UP=1,2 is the lowest priority, and UP=0,3 is the next higher priority. These are 
the marking results of each QoS policy:
Bronze marks all downlink traffic to UP= 1.
Silver marks all downlink traffic to UP= 0.
Gold marks all downlink traffic to UP=4.
Platinum marks all downlink traffic to UP=6.
Inter-Release Controller Mobility (IRCM)
This feature supports seamless mobility and Cisco Unified wireless network (CUWN) services across 
controllers with different software versions.
Note
IRCM is supported on GD releases only; ED releases, such as 5.2.x, are not supported.
RRM is supported between controllers running different versions of code. However, different RF groups 
will form for the controllers running different code levels. Therefore, separate RF groups do not have 
the ability to interact with one another, resulting in two groups of radios calculating power and channel 
separately. 
The effect on the network depends on how close the two RF groups are to one another. For example, if 
you have two controllers, one running software release 4.2.X.X and one running software release 
6.0.X.X, and both controllers service access points that are on the same floor, there will be some impact 
at the boundary between the two groups of access points on channel and TX power decisions.  
CUWN Service
4.2.x.x
5.0.x.x
5.1.x.x 6.0.x.x
Layer 2 and Layer 3 Roaming
X
X
Guest Access/Termination
X
X
X
X
Rogue Detection
X
X
Fast Roaming (CCKM) in a mobility group
X
X
Location Services
X
X
Radio Resource Management (RRM)
X
X
Management Frame Protection (MFP)
X
X
AP Failover
X
X