location-server

Configures the ExtremeLocation server‘s hostname on the RF Domain. When configured, RF Domain access points use a Websocket to forward 802.11 frames and BLE beacons to the specified ExtremeLocation 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.

Supported in the following platforms:

Syntax

location-server 1 ip <EL-SERVER-IP/HOSTNAME> {port <1-65535>}

Parameters

location-server 1 ip <IP/HOSTNAME> {port <1-65535>}
location-server 1 ip <IP/HOSTNAME> Identifies the ExtremeLocation server by its hostname
  • 1 – Sets the server ID as 1. As of now only one ExtremeLocation server is configurable.
    • ip <IP/HOSTNAME> – Enter ExtremeLocation server‘s hostname. This is the ExtremeLocation server designated to receive RSSI scan data from a WiNG dedicated sensor.
      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 <1-65535> Optional. Configures the port where the ExtremeLocation server is reachable.
  • <1-65535> – Specify a port from 1 - 65535.
    Note: By default, the ExtremeLocation server is reachable on port 443.

Examples

nx9500-6C8809(config-rf-domain-test)#location-server 1 ip feeds.extremelocation.com port 200
nx9500-6C8809(config-rf-domain-test)#show context
rf-domain test
 no country-code
 location-server 1 ip feeds.extremelocation.com port 200
nx9500-6C8809(config-rf-domain-test)#

Enabling Data (WiFi and BLE) forwarding to the ExtremeLocation Server

  1. Enable AP radio as sensor.
    ap510-133B38(config-device-94-9B-2C-13-3B-38-if-radio2)#rf-mode sensor

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#mode le-sensor

    OR

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#mode le-dual
    Note

    Note

    The 'le-dual' mode is supported only on the following IoT enabled APs: AP3xx, AP4xx, and AP5xx series. The APs should be running on WiNG 7.3.1 or later version.
  2. Configure the BLE beacon pattern and corresponding parameters.

    Eddyston Beacon Configuration

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#beacon pattern eddystone-url1

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#eddystone url 1 https://abc.com

    iBeacon Configuration

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#beacon pattern ibeacon

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#ibeacon major 455767788

    ap510-137E40(config-device-94-9B-2C-13-7E-40-if-bluetooth1)#ibeacon minor 2334688
  3. Configure sensor policy.
    nx9500-6C8809(config-sensor-policy-ble)#rssi-interval-duration 35
  4. In the AP's RF Domain context:
    1. Use the sensor policy.
      nx9500-6C8809(config-rf-domain-test)#use sensor-policy ble
    2. Configure the ExtremeLocation server hostname.
      nx9500-6C8809(config-rf-domain-test)#location-server 1 ip feeds.extremelocation.com
    3. Configure the ExtremeLocation TenantID.
      nx9500-6C8809(config-rf-domain-test)#location-tenantid 1234

Related Commands

no (rf-domain-config-mode) Removes the ExtremeLocation server configurations
9036514-01 Rev AA