In addition to dedicated AirDefense sensors, an access point radio can function as a sensor and upload information to an external WIPS server. Unique WIPS server configurations can be used by RF Domains to ensure a WIPS server configuration is available to support the unique data protection needs of individual RF Domains.
WIPS is not supported on a WLAN basis, rather sensor functionality is supported on the access point radio(s) available to each managed WLAN. When an access point radio is functioning as a WIPS sensor, it's able to scan (in sensor mode) across all legal channels within the 2.4 and 5.0 GHz radio bands. Sensor support requires an AirDefense WIPS Server on the network. Sensor functionality is not provided by the access point alone. The access point works in conjunction with a dedicated WIPS server.
In addition to WIPS support, sensor functionality has been added for Extreme Networks‘ ExtremeLocation system. locationing system. The ExtremeLocation system for Wi-Fi locationing includes WiNG controllers and access points functioning as sensors. Within the ExtremeLocation architecture, sensors scan for RSSI data on an administrator defined interval and send to a dedicated ExtremeLocation Server resource, as opposed to an ADSP server. The ExtremeLocation Server collects the RSSI data from WiNG sensor devices, and calculates the location of Wi-Fi devices.
To define a WIPS server configuration used with a RF Domain:
If a dedicated sensor is utilized with ADSP for rogue detection, any sensor policy selected from the Sensor Policy drop-down menu is discarded and not utilized by the sensor. To avoid this situation, use ADSP channel settings exclusively to configure the sensor and not the WiNG interface.
Within the ExtremeLocation Appliance architecture, sensors scan for RSSI data and send to a dedicated ExtremeLocation server resource, as opposed to an ADSP server.
ExtremeLocation is a highly scalable indoor locationing platform that gathers location-related analytics, such as visitor trends, peak and off-peak times, dwell time, heat-maps, etc. to enable entrepreneurs deeper visibility at a venue. To enable the location tracking system, the ExtremeLocation server should be up and running and the RF Domain configuration should point to the ExtremeLocation server.
Server Id | Use the spinner control to assign a DNS hostname of the ExtremeLocation resource. As of now only one (1) ExtremeLocation sever can be configured. |
IP Address/Hostname | Provide the ExtremeLocation server's hostname. When configured, access points within the RF Domain post location-related analytics to the specified ExtremeLocation server. Note: Enter the server‘s
hostname and not the IP address, as the IP address is likely to
change periodically in order to balance load across multiple
Location server instances.
|
Port | Use the spinner control to specify the port for the ExtremeLocation server. This is the port on which the ExtremeLocation server is reachable. The default port is 443. |
Note
Ensure that the access points in the RF Domain have at least one radio configured in the 'radio-share' or sensor mode.Note
Starting with WiNG 7.2.0 release, the AP5XX model access points are capable of capturing WPA3 frames in the sensor mode.Server Id | Use the spinner control to assign a numerical ID for up to three ADSP server resources. The server with the lowest defined ID is the first reached by the controller or service platform. The default ID is 1. |
IP Address/Hostname | Provide the numerical (non DNS) IP address or hostname of each server used as a ADSP sensor server by RF Domain member devices. A hostname cannot exceed 64 characters or contain an underscore. |
Port | Use the spinner control to specify the port of each ADSP sensor server utilized by RF member devices. The default port is 443. |