The client will receive a pop-up (if I remembered correctly) three to four times. It will state that the maximum client association has been reached. You keep making attempt and the WLC will, grudgingly, allow the 13th and more client in.
If you are speaking about aggressive load balancing. The default wondow is 5, if i recall. But you can change it higher or lower. The problem with agressive load balacing is that it is client dependent and it really does work.
First, your client will not get a message.
When a ap is config for 5 clients agressive load kicks in when the 6th client send an association response to the access point. The access points response with a association response with a reason code of #17. 17 is an idication to the client that the AP is busy and it should find another AP. The problem is MOST clients dont honor code 17 and will contiue to pound the ap for access. The ap will then allow the client on..
So as you can tell there isnt a lot of load balancing going on ...
i hope this helps... Leo, myself and other work hard to anwser your post. If you find this post or anyones post helpful kindly rate them!
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...