"I would request you get in touch with you network team and verify the existence of the mapped controllers in the network and any changes made recently. In case you are the only person handling the devices then I would request you to remove the entry of the controllers that you know should not be there and save the configuration. Then monitor the devices and see if this repeats (very unlikely) to clear you doubts.
The possibility is that maybe there were configuration changes made on the controller previously and not saved so in case the WLC was rebooted the old entries have popped up."
In other words, tell your people to stop screwing up your WLC configurations. Not one of Cisco's better responses, but after pointing out that I am the only one who makes these sorts of changes and indicating that I have spoken to other wireless engineers who have run afoul of this issue the TAC engineer did some more digging. What he found was Cisco bug CSCuc19950.
Here is a screen capture from Cisco's bug search tool. You will need a valid CCO login in order to view this for yourself:
Although undocumented, I believe this issue actually predates WLC code version 7.3.101.0. I have experienced this sort of thing in the past and dismissed it as a faulty configuration without ever reporting it to Cisco and I suspect I am not the only one. I have also spoken with other wireless engineers who reported seeing the issue prior to the 7.3 code release.
Here is what the issue actually looks like:
In testing with more that 20 Cisco 5508 wirless lan controllers I was able to create the behavior in three of them. Interestingly, the issue occurred multiple times on these same three WLCs, but never on any of the others.
Here is what the issue actually looks like:
In testing with more that 20 Cisco 5508 wirless lan controllers I was able to create the behavior in three of them. Interestingly, the issue occurred multiple times on these same three WLCs, but never on any of the others.
