According to the N+1 deployment guide, when the primary controller comes back up/online, the APs on the secundary (HA SKU) controllers should fallback to the primary. During my tests, this did not work. I enabled "AP Fallback" on both primary and secundary (HA SKU) controllers, but the APs remain on the secundary (while the primary was back online). Only after a boot of the secundary, did the APs go back to the primary. Is this normal ?
How long can it take for an AP to fallback ? I waited 10 minutes.
NOTE: the HA SKU is going to server multiple controllers, so he is not configured with the IP or name of any primary controller. I guess it is the AP itself that needs to remember what his primary controller was....
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...