RF Domain Sensor Configuration

Controllers and service platforms support dedicated sensor devices, designed to actively detect and locate unauthorized AP devices. After detection, they use mitigation techniques to block devices using manual termination, air lockdown or port suppression.

To define ADSP server credentials for WiNG controller or service platform data exchanges:

  1. Select Sensor.
  2. Click + Add Row to populate the Sensor Appliance Configuration field with up to three rows for WIPS server credentials:
    Server Id 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 Specify the port of each ADSP sensor server utilized by RF member devices. The default port is 443.
  3. If the device selected is an access point, configure the following settings in addition to the Sensor Appliance Configuration.
    Sensor Policy Use the Sensor Policy drop-down menu to select a Sensor policy. If no Sensor policy exists, use the Create icon to create a new Sensor policy. Or, use the Edit icon to edit an existing Sensor policy if required.
    Note: If a dedicated sensor is utilized with WIPS 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.
  4. Enter the ExtremeLocation Tenant‘s account number in the Tenant Account field.Use this field to configure your ExtremeLocation Tenant account number. ExtremeLocation Tenants, at the time of registration, are communicated (via email) an account number uniquely identifying the Tenant. Configure this account number in the RF Domain context. When configured, RF Domain AP reports, pushed to the ExtremeLocation server, include the Tenant's account number along with the reporting AP's MAC address.
  5. Select the + Add Row button to populate the ExtremeLocation Appliance Configuration field with ExtremeLocation server details:
    Server Id Policy Use the spinner control to assign a numerical ID for the ExtremeLocation server resource.
    Note: As of now only one server is supported.
    IP Address/Hostname Provide the hostname of the ExtremeLocation server used by RF Domain member devices. A hostname cannot exceed 64 characters or contain an underscore.
    Note: Enter the ExtremeLocation server‘s hostname and not the IP address, as the IP address is likely to periodically change in order to balance load across multiple Location servers.
  6. Select the Enable NSight Sensor checkbox to enable the NSight module.
  7. Click OK to save the changes to the sensor configuration.
    Click Reset to revert to the last saved configuration.
  8. Select Client Name from the expanded list of RF Domain Overrides:
  9. Click + Add Row to add client name information to the table:
    MAC Address Enter the MAC address of the device assigned a client name for controller, service platform, or access point management.
    Name Enter the name assigned to this client.
  10. Click OK to save the changes to the client name configuration.
    Click Reset to revert to the last saved configuration.