Cisco Cisco 2125 Wireless LAN Controller Leaflet
SNMP Trap Enhancements
The SNMP trap generated in the event of a channel change has been enhanced to provide detailed
information as to explain the reason for implementing a new channel plan. As evident from this image, the
enhanced trap includes the before and after metrics used in the DCA algorithm and which one of those metrics
contributed to the channel change for the given AP.
information as to explain the reason for implementing a new channel plan. As evident from this image, the
enhanced trap includes the before and after metrics used in the DCA algorithm and which one of those metrics
contributed to the channel change for the given AP.
Figure 20: Improved DCA Trap displays the reason behind a channel change
Cosmetic/Other Enhancements
As an undertaking to simplify configuration and improve usability, a new sub-section for the CHA was
created, which separates it from the Profile Thresholds sub-section that directly controls the triggers for
SNMP Trap generation.
created, which separates it from the Profile Thresholds sub-section that directly controls the triggers for
SNMP Trap generation.
The terms Signal and Coverage measurements under the Monitor Intervals sub-sections have also
been modified to reflect their appropriate meanings: Neighbor Packet Frequency and Channel Scan
Duration respectively.
been modified to reflect their appropriate meanings: Neighbor Packet Frequency and Channel Scan
Duration respectively.
Load-Balancing Changes
The default setting for load-balancing with 4.1.185.0 and later is OFF. When enabled, the load-balancing
window will default to 5 clients.
window will default to 5 clients.
(Cisco Controller) >show load-balancing
Aggressive Load Balancing........................ Disabled
Aggressive Load Balancing Window................. 5 clients
Aggressive Load Balancing........................ Disabled
Aggressive Load Balancing Window................. 5 clients
APPENDIX B: WLC Release 6.0.188.0 – RRM Enhancements
RRM Fixes for Medical Devices
This feature improves the way that QoS interacts with the RRM scan defer feature. In deployments with certain
power-save clients, you sometimes need to defer RRM normal off-channel scanning in order to avoid missing
critical information from low-volume clients, such as medical devices that use power-save mode and
periodically send telemetry information.
power-save clients, you sometimes need to defer RRM normal off-channel scanning in order to avoid missing
critical information from low-volume clients, such as medical devices that use power-save mode and
periodically send telemetry information.
You can use the WMM UP marking of a client in order to tell the access point to defer off-channel scanning for
a configurable period of time if it receives a packet marked UP. Use this controller CLI command in order to
configure this feature for a sepcific WLAN:
a configurable period of time if it receives a packet marked UP. Use this controller CLI command in order to
configure this feature for a sepcific WLAN:
config wlan channel-scan defer-priority priority [enable | disable] WLAN-id
where priority = 0 through 7 for user priority. This value must be set to 6 on the client and on the WLAN.
Use this command in order to configure the amount of time that scanning is deferred after an UP packet in the
queue:
queue:
config wlan channel-scan defer-time msec WLAN-id
Enter the time value in miliseconds (ms). The valid range is 100 (default) to 60000 (60 seconds). This setting
must match the requirements of the equipment on your wireless LAN.
must match the requirements of the equipment on your wireless LAN.
You can also configure this feature on the controller GUI. Select WLANs, and either edit an existing WLAN or
create a new one. On the WLANs > Edit page, click the Advanced tab. Under Off Channel Scanning Defer,
select the scan defer priorities, and enter the defer time in milliseconds.
create a new one. On the WLANs > Edit page, click the Advanced tab. Under Off Channel Scanning Defer,
select the scan defer priorities, and enter the defer time in milliseconds.
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 off-channel scanning must 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 must 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.
detection. Devices that need to defer off-channel scanning must 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 must 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 were 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:
the downlink connection from the access point, regardless of how they were 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