There are two feature enhancements to load balance clients on the Cisco Wireless LAN Controllers in software release 6.x and higher. Although there are similarities, both features work independently of each other and can be enabled or disabled independently. These are:rn1. Aggressive Load Balancing - Enhancement from previous version.rn2. Band Select or Band Direction - New feature that encourages dual band clients to connect to 5 G-Hz networks.
Aggressive Load Balancing (Legacy)
The previous version of aggressive load balancing was sometimes not reliable as it relied on the client NICs? implementation to balance client connections across multiple access points. The feature used a reason code 17 as a part of the association response to a client to indicate that an AP is unable to handle any more STAs and that the STA should try another AP. While the 802.11 specification does define what the reason code 17 is, it does not define how a STA must respond to one ? as long as they process it. The previous version of load balancing only denied a client once at maximum and eventually allowed the client to associate on the second attempt. Moreover, the configuration was globally defined per controller (Controller > General)and there was no way to disable it (selectively) for time sensitive voice clients. CLI options on the legacy ABL feature
config load-balancing enable
config load-balancing window
Advanced Load Balancing (a.k.a Load Balancing +)
The enhancement to Aggressive Load Balancing (in 6.x and 7.x software) allows you to configure load balancing per WLAN. The feature is disabled by default. The configurable options are defined globally(Wireless > Advanced > Load Balancing), but the feature itself can be enabled per WLAN (WLAN > Advanced > Client Load Balancing).
Use the following CLI command to configure load balancing for a specific WLAN:
Client Window Size: This was previously available through CLI only. Client Window size is interpreted as the minimum number of clients that should be on the AP before the load-balancing mechanism kicks in. The default value is 5. Internal research and observation has shown that this default should be changed to a more practical value, such as 10 or 12. Naturally, every deployment presents a different need and the window should therefore be set appropriately. This is the command-line syntax:-
(WLC) >config load-balancing window ?
Number of clients (0 to 20)
In dense production networks, the controllers have been verified to function optimally with load-balancing ON and window size set at 10. In practical terms, this means load-balancing behavior is only enabled when, for example, a large group of people congregate in a conference room or open area (meeting or class). Load-balancing is very useful to spread these users between various available APs in such scenarios.
Maximum Denial Count: This is a new option that allows the controller to set the number of times a client will be denied association before finally accepting it (persistent client).
(WLC) >config load-balancing denial ?
Number of denials <1-10>
Note: Users are never "thrown off" the wireless network. Load-balancing only occurs upon association and the system will try to encourage a client towards a more lightly loaded AP. If the client is persistent, it will be allowed to join (after passing the number of denials count) and will never be left stranded.
Recommendation for Load Balancing
It's recommended not to enable this feature for the voice WLAN as it can cause roaming issues. For other WLANs, it should be enabled only after testing.
Band Select or Band Direction
The 2.4-GHz band is often congested. Clients on this band typically experience interference from Bluetooth devices, microwave ovens, and cordless phones as well as co-channel interference from other access points because of the 802.11b/g limit of three non-overlapping channels. You can use this feature to combat these sources of interference and improve overall network performance. Band direction enables client radios that are capable of dual-band (2.4- and 5-GHz) operation to move to a less congested 5-GHz access point.
Band selection works by regulating/suppressing probe responses from the clients? 2.4 GHz radio. It makes 5-GHz channels more attractive to clients by delaying probe responses on the 2.4-GHz channels. The feature is disabled by default. The configurable options are defined globally (Wireless > Advanced > Band Select), but the feature itself can be enabled per WLAN (WLAN > Advanced > Client Band Select). This is useful if you want to disable band selection for a select group of clients (such as time-sensitive voice clients).
Use the following CLI to enable this feature on the WLAN:
(WLC) >config wlan band-select allow enable
The global configuration options are:
(WLC) >config band-select ?
cycle-count Sets the Band Select probe cycle count.
cycle-threshold Sets the time threshold for a new scanning cycle.
expire Sets the entry expire.
client-rssi Sets the client RSSI threshold.
Description of Global Options
Probe Cycle Count --> Number of times a client probe (2.4 G-Hz) is suppressed before allowing it.
Scan Cycle Period Threshold (milliseconds) à The time an AP waits before it increments the Probe Cycle Count. AP only increments the count if the difference of time between the latest and the last probe is more than the configured value (default is 200 milliseconds).
Age Out Suppression (seconds) --> Suppressed client age-out entries on the WLC (default is 20 seconds). For eg. if a client at maximum stays on a channel for 300 milliseconds during initial scanning and if there are a total of 40 channels to scan, the client will come back to the same channel about every 12 seconds. If the AP does not receive a probe from the same client within that time period, the AP assumes that the client has gone or associated to a different AP on a different channel.
Age Out Dual Band (seconds) --> The AP will not respond to a 2.4 G-Hz probe until a (dual-band) client is no longer marked as dual-band (default is 60 seconds). This is to prevent clients associated on 5 G-Hz radio from switching back to 2.4 G-Hz radio.
Acceptable Client RSSI (dBm) --> This setting allows filtering out far away clients with low signal strength to be excluded from the Band Select feature (default is -80dBm).
Recommendations for Band Select
Although this feature is designed to help 802.11n capable dual band clients to select the 5Ghz band (and utilize the bonded/40MHz wide channels on the 5Ghz frequencies), it has to be used with caution on voice enabled WLANs (with time-sensitive voice clients) as it can cause roaming delays or dropped calls. Please make sure you test it thoroughly in your environment with the dual band clients before enabling it.
Limitations for Band Select and Load Balancing
Please note some of the limitations of these enhancements:-
Band Select and Load Balancing work independently. They are global configurations per WLC and can be individually enabled/disabled per WLAN. They are disabled by default.
Load balancing uses the existing association denial mechanism based on the number of clients on the radio and Band Select uses probe response suppression on the AP.
Band Select is only performed on the controller connected AP. H-REAP AP without WLC connection (standalone mode) will not perform Band Select after reboot.
The load balancing feature only load balances clients between APs on the same controller. It does not support load balancing of clients between APs on different controllers.
Band Select and Load Balancing should be used with caution and only after testing with time sensitive applications like voice and video because they can cause roaming delays.
Currently Band Select is supported only on Marvell chipset based Cisco Unified AP platforms, viz. AP 1140, AP 1250/60 and AP 3500.
Adding information shared by George Stefanick:-
Kevin -- This is because not all clients will honour code 17 from the access point telling the client that the ap is busy. While some client do.
It is the responsibility of the client to honour, process or discard that association response frame with reason code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it tries. Many clients do not do this and send the association request again. The client in question is allowed on to the wireless network upon subsequent attempts to associate.
Q. The client load balancing feature for a Cisco WLC. Basically, if Client Load Balancing is enabled on a WLAN, will clients in that particular WLAN be balanced based on the total client count on the AP or the client count on that AP in the specified WLAN? A. Using Aggressive load balancing the LAP can be configured to load balance clients among AP on a per WLAN basis.
Hello;I have few 2802/3802 AP that will not convert to bridge mode. I have tried several firmware using 3504 and ME. This is the message that I get on the controller: (Cisco Controller) >config ap mode flex+bridge MAP4-3802EThis AP doe...
Hello.There are 2 controllers:1. Software version 8.1 with legacy APs.2. Software version 8.10 with new access points.1st controller does not support the access points of 2nd controller, and vice versa.Is it possible to configure roaming between them...
Not sure if anybody has the same issue or if I should open a TAC?The network includes:2 x C9800-40-K9 WLCs running Gibraltar 16.2.1 in HA cluster10 x AIR-AP1572EAC-E-K9 Mesh APs in local mode registered successfully with the WLC4 x AIR-AP1572EAC-E-K9 APs ...
HI I have a pair of controllers connecting to a pair of mobility anchors.While one controller establishes connection to both controllers, the second has both controller and path down for both anchors.Checked the firewall and found incomplete arp entr...