AP will not connect properly to the primary controller but goes to the secondary
I have a strange situation in which I have 2 remote APs running HREAP that will not connect to the primary controller. It keeps going to what I designated to be my secondary controller. Yes, the name and IP address are correct ( double and triple checked) when I entered the information in the High availability fields for Primary and secondary. It's seems to ignore what I have for the Primary controller. I have 40 other remote APs and they all or not acting like this. I can test and totally remove the info from the secondary field and see what happens but was wondering has anybody seen this ?
Re: AP will not connect properly to the primary controller but g
The only time I have seen something similar to this TAC couldn't find a cause but rebooting the primary controller resolved the issue. No one is really sure why.. Some AP's could join the primary controller but others couldn't.. it was wierd.
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...