I'm having an academic debate with a colleague regarding the fail-over behavior amongst RADIUS servers configured on a WLAN controller. My understanding is that unlike the autonomous APs, there is no such thing as a 'dead' timer and that the failover behavior is like this:
1. Primary AAA server available and ALL requests go to this server (unless you manually change the order of primary, secondary, tertiary on a per-WLAN basis to effectively 'load-balance').
2. The primary AAA server is used until it goes down, at which time the secondary AAA server will be used until it cannot be contacted. Once this goes down, the controller will use the tertiary, and then back to the primary.
My argument is that there is no pre-emptive recovery of the AAA server back to the previous one when it comes back online. I have not actually played with this in the lab, but I don't see any parameters in the GUI or the CLI that would allow me to effect the failover behavior. I have also referenced the full CLI guide for all controller releases and have not found anything useful in this situation.
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...