How does WLSE detect rogue APs?
A. Here is a brief summary of the rogue AP detection logic: a. A rogue AP appears and starts sending out beacons and responding to probe-requests. b. A nearby managed and RM-enabled AP or client detects the beacon (same channel or off-channel) or probe response (off-channel). The AP or client sends back a beacon report of the rogue AP in the next scheduled RM report. The scheduled internal RM reporting interval is 90 seconds, so this step can take up to 90 seconds to complete. c. The WLSE Radio Manager (RM) receives the beacon report, recognizes that this AP is not in the system (not a managed AP, and not a previously detected radio), and triggers the rogue AP switch-port tracing logic. The WLSE RM does not issue a rogue AP fault at this time. d. The WLSE RM waits for 3 measurement intervals (3×90, or 270 seconds) for other surrounding APs or clients to report the same radio.
A. Here is a brief summary of the rogue AP detection logic: a. A rogue AP appears and starts sending out beacons and responding to probe-requests. b. A nearby managed and RM-enabled AP or client detects the beacon (same channel or off-channel) or probe response (off-channel). The AP or client sends back a beacon report of the rogue AP in the next scheduled RM report. The scheduled internal RM reporting interval is 90 seconds, so this step can take up to 90 seconds to complete. c. The WLSE Radio Manager (RM) receives the beacon report, recognizes that this AP is not in the system (not a managed AP, and not a previously detected radio), and triggers the rogue AP switch-port tracing logic. The WLSE RM does not issue a rogue AP fault at this time. d. The WLSE RM waits for 3 measurement intervals (3×90, or 270 seconds) for other surrounding APs or clients to report the same radio. This delay allows as many APs as possible to detect the rogue and helps pinpoint the rogue’s location (which is
