Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Configuring IoT Transport Stream
An IoT Internet of Things. IoT refers to the internetworking of devices that are embedded with electronics, software, sensors, and network connectivity features allowing data exchange over the Internet. transport stream can be created for an AP group with APs running AOS-8.
To create an IoT transport stream for an AOS 8.x AP group, complete the following procedure:
- In the WebUI, set the filter to an AOS-8 AP group.
- Under , click .
- Click the Config icon.
- Click .
- Click tab.
- In the table, click icon.
- Configure the following IoT transport stream parameters and click .
| Parameter | Description |
|---|---|
|
|
Name of the IoT transport stream. |
|
|
URL Uniform Resource Locator. URL is a global address used for locating web resources on the Internet. of the server to send the data stream. |
|
|
Type of the server. Available options are:
|
|
|
Class of the device. |
|
|
Time interval, in seconds, to report the data stream. Default value is 600 seconds. |
|
|
Define the zone in which the IoT transport stream works. |
|
|
Enable periodic BLE Bluetooth Low Energy. The BLE functionality is offered by Bluetooth® to enable devices to run for long durations with low power consumption. telemetry. |
|
|
Enable BLE data forwarding. |
|
|
Enable per frame filtering. |
|
|
Enable reporting of only device count. |
|
|
Cipher list to use when sending data stream. Available options are:
|
|
|
|
|
|
Use credentials for authentication with authentication server. |
|
|
Use token for authentication with authentication server. |
|
|
Use credentials of client for authentication with authentication server. |
|
|
URL of the authentication server. This parameter is available when using credentials or client credentials for authentication. |
|
|
Username to use for authentication with authentication server. This parameter is available when using credentials for authentication. |
|
|
Password to use for authentication with authentication server. This parameter is available when using credentials for authentication. |
|
|
ID of the client for authentication with authentication server. |
|
|
Token for authentication with the authentication server. This parameter is available when using token for authentication. |
|
|
Token for authentication with the authentication server. This parameter is available when using client credentials for authentication. |
|
|
|
|
|
|
|
|
|
|
|
URL of the proxy server. |
|
|
Port of the proxy server. |
|
|
Username to use with proxy server. |
|
|
Password to use with proxy server. |
|
|
Define which devices are reported. Available options are:
|
|
|
|
|
|
Report devices that are within defined meters of the beacon. |
|
|
Report devices that have had activity in the last defined meters since last reported. |
|
|
Report devices that have had activity in the last defined time period. |
|
|
Report devices by defined RSSI Received Signal Strength Indicator. RSSI is a mechanism by which RF energy is measured by the circuitry on a wireless NIC (0-255). The RSSI is not standard across vendors. Each vendor determines its own RSSI scale/values. reporting format. Available options are:
|
|
|
Type of device environment. Available options are:
|
|
|
Value of fading factor. This parameter is available when filtering devices in custom environment. |
