Aggressive load balancing

[Peter Nugent]

Is there a way to limit the total number of client on and ap?

We have a client with a small school using the 526 controller.

Aggressive load balancing enabled but we cannot change the window size, not that it matters a great deal as the clients seem to ignore reason 17 code anyway?

Should

config advanced 802.11b profile clients global

set a hard limit on the number of clients that can associate to and ap?

[dancampb]

Currently there isn't a way to limit the number of associations per AP in an controller environment. Aggressive load balancing tries to encourage a client to associate to a less loaded AP but it won't stop the client from associating.

[Peter Nugent]

Thanks very much for that its as I thought, is there a way to debug to ensure we are getting reason code 17 out and prove its the client not the AP?

[weterry]

your other post about 'debug client' I believe is showing you the status 17. You'll see something like 'sending assoc response..... (status 17)' in the debug client.

[Peter Nugent]

Many thanks the debug client is a different issue but we will see what we get

[George Stefanick]

You want to be careful with Aggressive load balance on your WLC, If you have sensitive applications. You may experience issues. All VOIP deployments, ALB is always recommended to be disable.

[dennischolmes]

Aggressive load balancing breaks applications that are "dropped packet" sensitive as there is a momentary disconnect due to the use of deauth packets to force the client to a less crowded AP. I don't suggest using it. If you are having issues with too many clients per AP or more that 60 clients (20 per channel in b/g) I would strongly suggest looking at moving to 5ghz to allow for multiple APs covering the area with less channel reutilization. This will result in a larger number of clients being able to associate with the least amount of cochannel interference.