The Rogue AP made as Acknowledged AP error message is due to Cisco bug ID CSCse80700. The rogue access point (AP) alarms can initially appear with a non-zero received-signal-strength-indication (RSSI) value and a Service Set Identifier (SSID) set to a non-empty name, but eventually, the RSSI value updates to zero with no SSID.
This problem first occurs in the Wireless Control System (WCS) version 4.0(66). An AP is reported as a rogue until that AP joins the neighbor list, and the list verifies that the AP is safe. If that AP never joins the controller with those APs, it is reported as a rogue until the other APs in their neighbor group acknowledge it.
The only workaround available is to disable the rogue AP poll and rely completely on traps to detect rogues. In this case, rogue alarms contain a non-zero RSSI value. But, over time, due to lost traps and inaccurate detection counts, the rogue AP alarm information drifts and becomes inaccurate. In addition, if the rogues move, the RSSI value never revises downward.
In order to resolve this issue, upgrade all controllers to version 18.104.22.168. Refer to Cisco Downloads in order to download the firmware.
Can you configure a RF Profile to disable 2.4 GHZ only on a 8540 WLC version 22.214.171.124? I have configured a global setting to lower the 2.4 GHz radio to 5 but I'm finding that some area's I would like to disable the 2.4 GHz per radio AP group.&...
Hi, I have WLC + Lightweight APs running in my office which has one single SSID for 2.4Ghz and 5Ghz spectrum.My laptop's wireless adapter supports up to 802.11ac. I would like to know how my Windows laptop choose which radio frequency's SSID to ...
I'm trying to troubleshoot a roaming problem, where some of our client sometimes experience a 20 second interruption of connectivity. The problem occurs about once in every 50 times the clients roams.All involved access-points are connected to the same, l...