I've recently had cause to move the WLC 4402 that acts as the anchor for our guest networks and I've ran into a few problems:
1. The Control Path is down for one of the local controllers, I can't see why the data path is up and both paths are up for all of the other controllers so it doesn't appear to be the f/w.
2. When I audit the local controler WCS tells me that my anchor address isn't present in the controller so I tried a restore from WCS to the WLC and I get the result shown on "WCS Screenshot.rtf"
The release notes for WCS 188.8.131.52 says there was a caveat that has been solved. I'm running WCS v184.108.40.206 and WLC v220.127.116.11, I've tried deleting the affected controller from WCS and adding it again with the same result.
I've tried that and it hasn't made any difference. I also tried reinstalling the software on the foreign WLC, no joy. I may try doing the same on the anchor but I don't hold out much hope.
It's odd that the control path is down between the two controllers and everything else is fine. I had no issues when the anchor was on the previous firewall. Is it just coincidence that the WCS is having problems with the config of the anchors of the guest WLANs on the same foreign controller?
Do I need to reboot or otherwise fix something on our WCS?
Do you have all the right ports and protocols configured/open on the new firewall? WLC's need certain ports and protocols in order to communicate with your anchor, and WCS needs other ports/protocols to communicate with the anchor.
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...