I have about 80 AP's that we added when we converted from Autonomous to LWAPP.
Today, i see a new AP in the list that I didnt add - it stands out because the name is so different from our naming standard, and its not "associated" with the controller.
My question is this - why would WCS see that as a "valid" AP instead of a rouge? Is it common for WCS to add an AP automatically if it is "LWAPP" enabled? I thought we had to actually import the device?
The AP appears to be a Cisco AP (by the mac address database search) AND shows to be using LWAPP. It currently seems to be shutdown/offline, so im having a hard time actually finding the thing. Also, I do not see this ap listed on any of my controllers (which i am not really suprised by - since its not "associated".)
WCS shows any AP that associated with a controller. Not just the APs that are currently associated.
So the simplest explanation is that the AP in question temporarily registered with one of your controllers, and therefor WCS added it to the database.
With that said, APs automatically register with controllers. So anyone could bring in an AP, plug it in, auto register (assuming DHCP/DNS/ or any other method of controller discovery) and then even if they remove the AP forever more, the AP will still be listed in WCS.
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...