The load threshold violation is generated because of client count on a given AP, I am not aware of any bugs or features that would cause this to occurr in correctly. basically this alarm is triggered when the client count exceeds the preset threshold value which I believe is 12. You can find this threshold under Wireless> 802.11a> RRM>General (on WLC 220.127.116.11 code, it'll be in the same general area on 4.2; Don't confuse it with the coverage hole threshold which is usually 3). Definitely check the client counts on the access points have the issues.
If you are violating this threshold there are a couple of options: 1) raise the threshold to a higher value; the downside to this is if you get too many clients on a single AP it can have adverse effects on all the clients. 2) add more access points to lower the possibility of all clients being on 1 AP..
Wireless> 802.11a> RRM>Auto RF (Profile Threshold For Traps)
12 is default
Great response btw !
"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...