Radar Commands

Radar provides: a radio frequency (RF) scanning task that runs on Wireless APs, an RF Data Collector (RFDC) to receive and manage RF scan messages sent by Wireless APs, and an Analysis Engine to process data from RFDCs generated by APs managed locally by the controller and also those from other controllers. The Analysis Engine participates with Radar in generating historical reports and reporting active threats. APs participating in In-service scanning must be added to in-service scan profiles, so they can be processed and managed by the Radar WIDS-WIPS system. See the ExtremeWireless User Guide for detailed information about Radar (WIPS).

Guardian APs must be added to Guardian scan profiles. (That is any AP except the 3705.)

The AP integrates with the AirDefense Service Platform (ADSP), offering an additional profile option that allows the AP to function as an AirDefense sensor or to act as a sensor and retain the ability to forward traffic. When the AP is configured with a AirDefense dedicated sensor profile, the functionality of the AP is controlled by the ADSP server. When the AP is configured as a AirDefense Radio Share profile, it continues to forward traffic for adjacent APs while sending packets to an ADSP server. To ensure rate performance, an AP configured with a Radio Share profile does not forward its own Tx/Rx data to the ADSP server.

This chapter describes the commands that enable and configure the Radar (WIPS) options for the controller. These commands are located in the mitigator context of the CLI.

All CLI commands cache changes. For this reason, sometimes when you make a change in a particular context, the change may not be visible immediately. If this happens, you must exit and re-enter the context in order to ensure that the database is synchronized with the latest change.