A rogue containment policy is being initiated against my organization's APs and I do not have the tools/knowledge necessary to track down its point of origin. What tools or steps are required to identify who is containing an AP?Thanks
At this point the containment has ceased, but the cause has not yet been determined. The intermittent nature of the issue is making it very difficult to troubleshoot.Cisco TAC has yet to respond to my inquiry.
If that is true, then our system is indeed containing its own APs for the MAC address listed is that of one it manages.leolaohoo mentioned a firmware bug in the controller could be causing this in a previous post. It sounds as though I need to take ...
Thank you, Mr. Scholmes.I see that message quite often in the log entries and knew they were caused by a software bug, but I did not know it was associated with containment entries looking like this:"AP '00:00:00:00:0:00' with protocol '802.11b/g' on...
Mr. Scholmes,This is where I show how much I DON'T know about the wireless controller. None of the log entries pertaining to this issue (that I can identify) indicate a MAC address of any kind. Would you mind providing a sample entry so I can get a...
leolaohoo,To which platform and software version are you referring with regards to the bug? We have a 4402 running IOS version 4.2.x and a WCS server running 5.1.xI've verified that auto-containment has been disabled and there are no disabled APs. A...
