I have done an audit on the configuration group that our WiSMs are in, which shows up some differences. I would like to investigation on what the actual differences in the attribute values are between the controllers and the templates in each case. I get an error message shown in the first attachment (Failed to contact server. Please make sure you are logged in and have network connectivity).
The version of WCS is 126.96.36.199, and so is the software on the WiSM. The WCS can talk to the WiSM, and so can I. Can you please advise what how this issue can be fix.
I opened a TAC SR to check but the problem later disappeared without doing anything from my side. We got the TAC SR closed without doing anything. ( we captured traffic and collected logs but the problem is resolved before the engineer analyzes the traffic).
I suggest that you wait about a week and open a TAC cae if the issue persists.
One more thing I just remembered: in my case the configuration was identical but it shows is as mismatch and when try to audit it gives the error.
Btw, what is your WCS version?
Sent from Cisco Technical Support iPad App
Rating useful replies is more useful than saying "Thank you"
Everyone likes to go fast. The speed of your business, your network and your Wi-Fi is critical to how quickly you can move forward.
In this latest generation of wireless networking, Wi-Fi 6, speed is a focus, but it’s not about just individual devi...
My report tells you the experimental results of the performance of Cisco ClientLink supported on Cisco Aironet access points. You can remember the great performance of ClientLink forever.I have learned that new access points for IEEE802.11ax are Cisco ...
Join us live on Tuesday, March 3 at 10:00 am PT (and on demand after) to learn about how Wi-Fi 6 and 5G will change the wireless landscape in the enterprise? We'll be talking to Cisco's wireless CTO, Matt MacPherson, who will dive into each of t...
Join us live on Tuesday, March 3 at 10:00 am PT (and on demand after) to learn about how Wi-Fi 6 and 5G will change the wireless landscape in the enterprise? We'll be talking to Cisco's wireless CTO, Matt MacPherson, who will dive into each of these techn...
SymptomsWe deploy an SSO pair of 5520's in our DC and DR sites running 188.8.131.52 code.Our Enterprise WLAN had been somewhat reliable until several months back. Suddenly users began creating service tickets complaining that one or sometimes both...