I have a situation where I am trying to locate a rogue AP in one of my office buildings. When I bring a laptop over there with NetStumbler or Inssider, I get no response from any access points or clients. Its like that throughout the entire building. However when I leave the building, the AP start to come up but I cant get near them.
I have another build that we have as well and the probing works just fine. Would there be a controller template or access point template that would be causing this problem?
Here is what I am running:
Cisco 4400 controller with firmware 188.8.131.52
Cisco 4400 controller with firmware 184.108.40.206
Cisco WCS 220.127.116.11
The access points that are connected to the controller with a firmware of 18.104.22.168 is the one that seems to be stopping my attempts with probing. So far my searching for causes has not turned up anything=(
Looks like its to late to see my logs from when I was last testing. I will try it again and see what the logs tell me.
The reason we are running two different firmwares is because we have recently added Cisco 7921 phones and the 22.214.171.124 firmware has a bug where it will lock up the 7921 phones. So we have one controller running older firmware for testing.
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...