rest <URL>
rest <URL>
rest <URL> | Configures the third-party server's URL
|
ap8432-070235(config-ble-data-export-policy-test)#rest https://test.com/12/
ap8432-070235(config-ble-data-export-policy-test)#show context ble-data-export-policy test rest https://test.com/12/ ap8432-070235(config-ble-data-export-policy-test)#
The following example shows the configurations will have to configure the following parameters to enable BLE data forwarding:
On the WiNG AP‘s profile/device context, configure the following Bluetooth parameters:
ap8432-070235(config-profile-test-if-bluetooth1)#mode le-sensor
ap8432-070235(config-profile-test-if-bluetooth1)#no shutdown
ap8432-070235(config-profile-test-if-bluetooth1)#show context interface bluetooth1 no shutdown mode le-sensor ap8432-070235(config-profile-test-if-bluetooth1)#
This enables the AP as a BLE sensor.
On the APs‘ controller,
Configure a BLE data export policy, pointing to the external, third-party, REST end-point.
NOC-NX9500(config-ble-data-export-policy-test)#rest https://test.com/12/
Configure a sensor policy.
NOC-NX9500((config-sensor-policy-test)#rssi-interval-duration 30
Navigate to the BLE-enabled, WiNG AP‘s RF Domain context and:
Use the BLE data export policy, configured in step 2a.
NOC-NX9500(config-rf-domain-ble)#use ble-data-export-policy test
This enables BLE data forwarding to the external, third-party server specified in the policy.
Use the sensor policy, configured in step 2b.
NOC-NX9500(config-rf-domain-ble)#use sensor-policy test
When applied, BLE data is forwarded at the interval specified in the sensor policy.
Removes the REST endpoint URL configuration |
|
Documents the Sensor policy configuration commands |