1130AG AP through WCS load balancing

licopeland · ‎10-15-2007

Currently using Cisco WCS for wireless, all 1130AG access points. I know the system is built for load balancing and that the threshold for load balancing is based on number of client connections to the AP (or this is what I've been told). Does anyone know the number of connections to one access point before it starts load balancing, or where I can find this information?

Rob Huffman · ‎10-15-2007

Hi Lillie,

Here is some info related to Load Balancing;

Load Balancing Window

TIP:

The default setting for load-balancing is ON, with the load-balancing window set to 0. This window should be changed to a higher number, such as 10 or 12.

Note: In release 4.1 MR1 and later, the default setting for load-balancing is OFF and if enabled, the window size defaults to 5.

WHY:

Although not related to RRM, aggressive load-balancing can result in sub-optimal client roaming results for legacy clients with poor roaming logic, which makes them sticky clients. This can have adverse effects on the CHA. The default load-balancing window setting on the WLC is set to 0, which is not a good thing. This is interpreted as the minimum number of clients that should be on the AP before the load-balancing mechanism kicks in. 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.

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 and never left stranded.

Load-Balancing Changes

The default setting for load-balancing with 4.1.184.3 and later is OFF. When enabled, the load-balancing window will default to 5 clients.

(Cisco Controller) >show load-balancing

Aggressive Load Balancing........................ Disabled

Aggressive Load Balancing Window................. 5 clients

From this doc;

Radio Resource Management under Unified Wireless Networks

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072c759.shtml#app7

Hope this helps!

Rob