WLC-Best Practices-RF Management
WLC-Best Practices-RF Management
WLC-Best Practices-RF Management
html
RF Management
Auto Coverage Hole Detection
Description—Auto CHD should be enabled.
The controller uses the quality of client signal levels reported by the APs to determine if the power level of that AP needs to
be increased. Coverage Hole Detection (CHD) is controller independent, so the RF group leader is not involved in those
calculations. The controller knows how many clients are associated with a particular AP and what are the signal-to-noise
ratio (SNR) values for each client.
If a client SNR drops below the configured threshold value on the controller, the AP increases its power level to try to
compensate for the client. The SNR threshold is based on the transmit power of the AP and the coverage profile settings on
the controller.
For instructions on how to configure auto CHD, see the Cisco Wireless Controller Configuration Guide.
Status:
Compliant—CHD enabled
Non-Compliant— None or one enabled
Note For optimal performance, use the Automatic setting to allow best transmit power for each radio.
Status:
Compliant—TPC enabled for 802.11a/b
1 of 5 12/20/2022, 11:23 AM
RF Management https://wlc.mmki.co.id/bp/helpfiles/r-rf-mgmt.html
CleanAir Detection
Description—CleanAir should be enabled. Clicking Fix it Now enables CleanAir.
To effectively detect and mitigate RF interference, enable CleanAir whenever possible. There are recommendations to various
sources of interference to trigger security alerts, such as generic DECT phones, jammer, and so on.
Status:
Compliant—Enabled
Non-Compliant—Disabled
CLI Option:
Verify CleanAir configuration on a network by entering this command:
(Cisco Controller) >show 802.11{a|b} cleanair config
Enable CleanAir functionality on a network by entering this command:
(Cisco Controller) >config 802.11{a|b} cleanair enable network
Configure to enable interference detection for specifically jammer by entering this command:
(Cisco Controller) >config 802.11{a|b} cleanair device enable jammer
2 of 5 12/20/2022, 11:23 AM
RF Management https://wlc.mmki.co.id/bp/helpfiles/r-rf-mgmt.html
may remain with its current AP. In this case, if the CU on 2.4 GHz is low and the call quality is not poor, then disabling the
selected band is acceptable. However, the preferred design is to enable band selection on 5 GHz with all data rates enabled
and 6 Mbps as mandatory. Then, set the 5 GHz RRM minimum Tx power level 6 dBm higher than the average 2.4 GHz power
level set by RRM.
The goal of this configuration recommendation is to enable the client to obtain a band and channel with better SNR and Tx
power initially. As already stated, generally when a client decides to roam, it scans its current channel and band first. So, if
the client initially joins the 5 GHz band, then it is more likely to stay on the band if there are good power levels on 5 GHz.
SNR levels on 5 GHz are generally better than 2.4 GHz because 2.4 GHz has only three Wi-Fi channels and is more
susceptible to interference such as Bluetooth, iBeacons, and microwave signals.
802.11k is recommended to be enabled with dual-band reporting. This enables all 802.11k-enabled clients to have the
benefit of assisted roaming. With dual-band reporting enabled, the client receives a list of the best 2.4-GHz and 5-GHz APs
upon a directed request from the client. Here, the client most likely looks at the top of the list for an AP on the same
channel, and then on the same band as the client is currently on. This logic reduces scan times and saves battery power.
Having 802.11k enabled on the Cisco WLC does not have a downside effect for non-802.11k clients.
Status:
Compliant—Enabled on all WLANs
Non-Compliant—Disabled
CLI Option:
Verify Band Select by entering this command:
(Cisco Controller) >show band-select
Enable Band Select on a WLAN by entering this command:
(Cisco Controller) >config wlan band-select allow enable wlan-id
3 of 5 12/20/2022, 11:23 AM
RF Management https://wlc.mmki.co.id/bp/helpfiles/r-rf-mgmt.html
Wi-Fi Interference
Description—Triggers ED-RRM by Wi-Fi rogue interferences. Rogues are reported as Interference, with Duty Cycles and
threat value.
Status:
Compliant—Wi-Fi Interference Awareness is enabled on both bands and duty cycle is 80 percent or higher
Non-Compliant—Wi-Fi Interference Awareness is either not enabled on both bands or duty cycle is less than 80
percent
CLI Option: Enable Wi-Fi Interference by entering this command:
(Cisco Controller) >config advanced {802.11a|b} channel cleanair-event enable
(Cisco Controller) >config advanced {802.11a|b} channel cleanair-event rogue-contribution
enable
(Cisco Controller) >config advanced {802.11a|b} channel cleanair-event rogue-contribution
duty-cycle 80
FRA Enabled
Description—Flexible Radio Assignment (FRA) can automatically assign the XOR 2.4-GHz radios to other roles such as 5 GHz
and Monitor. We recommend that you enable FRA when you have APs such as Cisco Aironet 2800 and 3800 Series APs that
support XOR operation. Clicking Fix it Now enables FRA; clicking Restore Default disables FRA; clicking Ignore adds the
FRA Enabled to the ignored best practices list (if you want, you can add it back to the best practices list from the ignored
list).
Status:
Compliant—FRA is enabled.
Non-Compliant—FRA is disabled.
CLI Option: Enable FRA by entering this command:
(Cisco Controller) >config advanced fra enable
Note This should not be done for low density deployment where these low data rates are expected to be present.
CLI Option:
(Cisco Controller) >config 802.11a rate disabled 6
(Cisco Controller) >config 802.11a rate disabled 9
Note This should not be done for low density deployment where these low data rates are expected to be present.
CLI Option:
(Cisco Controller) >config 802.11b rate disabled 1
4 of 5 12/20/2022, 11:23 AM
RF Management https://wlc.mmki.co.id/bp/helpfiles/r-rf-mgmt.html
5 of 5 12/20/2022, 11:23 AM