Unfortunately there is no standard way to do that.
The association process and the roaming process is a client decision. Which means that the client hardware and driver will scan for available AP and then select the "right" AP depending on its own algorithm. (Generally based on RSSI). If an AP decide to disassociate a client to have him connected to an other AP, this might not occur because the client might reassociate to the same AP.
Autonomous Cisco AP deliver "load" indicator in probe messages as of CCX specification. However only clients which understand CCX will be able to load balance using this information.
Cisco Unified Wireless (lightweight AP) as a load balancing feature that can do better by refusing client association on a specific AP and waiting for the client to use on other one. If the client still tries to associate with the first AP, the controller will accept the client (to ensure connectivity).
You just have to make sure you don't have more clients than what you specify in the max-association on both ap's. You can probably get away with setting one ap with max-association (the ap that always has more clients) and leaving the other ap as-is.
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...