cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2817
Views
4
Helpful
2
Replies

WLC Load Balancing Threshold

pmchandler
Level 1
Level 1

I am trying to understand how the load balancing threshold is calculated but I am finding conflicting information, even withing Cisco's own documentation. I would be grateful if anyone could help.

Cisco's latest Wireless LAN Controller Configuration Guide for software release 7.0.116.0 (April 2011) contains the following information for configuring Wireless > Advanced > Load Balancing Page (emphasis mine):

In the Client Window Size text box, enter a value between 1 and 20. The window size becomes part of the algorithm that determines whether an access point is too heavily loaded to accept more client associations:

load-balancing window + client associations on AP with highest load = load-balancing threshold

In the group of access points accessible to a client device, each access point has a different number of client associations. The access point with the lowest number of clients has the lightest load. The client window size plus the number of clients on the access point with the lightest load forms the threshold. Access points with more client associations than this threshold is considered busy, and clients can associate only to access points with client counts lower than the threshold.

Option 1

The formula shown is correct (load-balancing window + client associations on AP with highest load = load-balancing threshold). If so, this would mean that if you had a window size of 5 and the AP with the highest load at the time of calculation was 15, the threshold would be 18. However, as no APs have 18 associations then this threshold would never be reached. Even if an AP reach 18 associations, the next client trying to associate would trigger another calculation for the threshold which would be 21 (3 + 18) and so still, this threshold would never be hit.

Option 2

The description in the paragraph below is correct (The access point with the lowest number of clients has the lightest load. The client window size plus the number of clients on the access point with the lightest load forms the threshold). This sounds much more sensible to me. In this case, the window size was 3 and the AP with the lowest number of associations already had 7 clients associated, the load balancing threshold would be 10 i.e. no load balancing would occur until a client tried to associate with an AP which already had at least 10 clients associated.

Option 3

I have seen many descriptions on forums etc of the load balancing threshold being essentially the Client window size, i.e. if the client window size is 3 then load balancing will kick in when a client tries to associate to an AP with at least 3 clients already associated. This doesnt match the above documentation unless the AP with the least number of clients associated doesnt have any associated clients i.e. 0 clients.

Questions

  1. I think Option 2 is the correct description of load balancing and the formula given stating use of the AP with the highest load is a typo (albeit still not corrected in the latest documentation). Am I correct?
  2. The problem with using the option 2 method of calculating the load threshold is that you will be unnecessarily performing load balancing in an environment where some of your APs do actually have zero clients associated, unless you set the window size to somehing close to 10.
  3. I read here http://www.perihel.at/wlan/wlan-wlc.html#aggressive-load-balancing that when calculating the load threshold, it only accounts for the 8 'best' APs for a given client. In other words, if you have 60 APs on your campus but only 20 are visible to the client, the controller will only perform its load threshold calculations bases on the 8 APs which have the best signal to the client. This would ,ake sense as there is no point setting a load threshold based on the lightest loaded AP which is not even within 'reach' of the client. Is this correct as I can not find any other documentation which supports this?

Thanks in advance for your help with this.

2 Replies 2

weterry
Level 4
Level 4

Interesting, the config guide contradicts itself in the same paragraph.....    I thought maybe we had two different documents with different explanations.  I don't see any open documentation bugs asking to correct this, but I swear I've heard discussion on this in the past.......

First off:  Option #3 was the "old way". I think it changed in 6.0.    If you had a threshold of 5, then as soon as you had 5 clients on an AP it would reject the association (3 times and then let them on the 4th attempt).  Now its a sliding window/scale.

Option #1 I think is completely wrong. As you described, how in the world would you ever surpass the threshold if the highest AP + the window is what you have to beat to load-balance....?    RIght, that just doesn't make any sense to me.....

Option #2, the way you explain it is correct to my understanding...

Your question #3 is also correct (not sure if it is Top 8 or based on an RSSI threshold though.)

The idea is that you don't want some AP in a remote office with 0 clients being your starting point.   So I believe that it is based on the top X candidate for your client.    If your client has 4 viable candidates (lets just say -70 or better), and one of those APs has 5 clients and the rest have 15, I'd expect loadbalancing to try to get you to the 5 client AP if your window size was ~10......  something like that anyhow... 

Thanks weterry for providing some much needed clarity.

Your explanation certainly helps to clarify the issue in my mind, althugh there are clearly still some details we lack in our knowledge:

  • Are candidate APs a list of Top X or RSSI threshold, or both?
  • If Top X, then what does X equal?
  • If RSSI threshold, what is that figure?

If anyone else can shed light on these questions, that would be great!

Finally, where would I log a documentation bug to get this corrected?

Review Cisco Networking products for a $25 gift card