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.
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.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
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 ...
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.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...