For the lwapp based APs (10x0) series, you can run the controller in L3 mode and have the APs pull ip addresses. As of 4.1.x, they are now pingable.
You can then change them from dhcp to static ips and then use a monitoring tool such as Cacti or nagios to monitor them.
With a mesh, it is theoretically possible to monitor ping latency to each mesh AP and then that as a guide to determine if the pole top APs have switched to a root that more hops away: assuming that more hops would result in increased latency. Many NMS systems can kick back uptime based on icmp results
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...