IoT radio profile

Table of contents

IoT radio profile

iot radio-profile’s are used to configure the Aruba IoT radio mode, BLE and/or ZigBee, and the respective mode settings. An iot radio-profile can either be applied to an internal or external radio instance.

The iot radio-profile also controls the AP’ BLE console settings.

The following table lists the available iot radio-profile parameters and their description:

ArubaOS	Aruba Instant	Description
`iot radio-profile <iot-profile-name>`	`iot radio-profile <iot-profile-name>`	Name of the radio profile
`radio-instance <internal, external>`	`radio-instance <internal, external>`	Type of the radio the profile applies to. Available options are: - *internal* - applies to the internal radio of the AP (default) - *external* - applies to the external radio that is connected over the USB port of the AP
`radio-firmware <firmware>`	`radio-firmware <firmware>`	Firmware that is applied to the radio. Available options: - *default* - default firmware gets applied
`radio-mode <mode>`	`radio-mode <mode>`	Radio mode to be enabled. Available options are: - *None* - Radio disabled (default) - *ble* - BLE (tx/rx) enabled - *zigbee* - ZigBee enabled - *“ble zigbee”* - BLE (tx-only) and ZigBee enabled concurrently
`ble-opmode <opmode>`	`ble-opmode <opmode>`	BLE operation mode to be enabled. This parameter is available only when `radio-mode` is set to *ble* or *“ble zigbee”. Available options are: - beaconing* - BLE (tx) beaconing enabled using the iBeacon protocol (default) - *scanning* - BLE (rx) scanning enabled - *“beaconing scanning”* - BLE (tx/rx) beaconing and scanning enabled concurrently (default - does not show up in the configuration!)
`ble-console <console-mode>`	`ble-console <console-mode>`	BLE console mode to be enabled. BLE console provides console access to the AP over BLE. This parameter is available only when `radio-mode` is set to *ble* or *“ble zigbee”. Available options are: - dynamic* - Enables BLE console automatically - on - BLE console enabled - *off* - BLE console disabled (default)
`ble-txpower <txpower>`	`ble-txpower <txpower>`	BLE tx power in dBm to be used. This parameter is available only when `radio-mode` is set to *ble* or *“ble zigbee”. - Value range: -20 … 4*, (default: 0)
`zigbee-opmode <opmode>`	`zigbee-opmode <opmode>`	ZigBee operation mode to be used. This parameter is available only when `radio-mode` is set to *zigbee* or *“ble zigbee”. Available options are: - coordinator* - Radio works as ZigBee coordinator (default)
`zigbee-channel <channel>`	`zigbee-channel <channel>`	Channel to be used. This parameter is available only when `radio-mode` is set to *zigbee* or *“ble zigbee”. Available options are: - auto* - Selects the channel automatically (default) - *Value range: 11 … 26* - Specifies the channel manually

Additional CLI parameters:

clone - Copy data from another iot radio profile (ArubaOS only)

no - Delete a command from the profile

Note:
The default ble-opmode beaconing scanning does not show up in the configuration. Using the “beaconing scanning” parameter is only required to change the configuration form ble-opmode beaconing or ble-opmode scanning back to the default.

If the radio-mode is set to “ble zigbee” only BLE (tx) beaconing is supported, regardless of the ble-opmode setting.

An iot radio-profile is enabled using the following command:

ArubaOS	Aruba Instant
`iot useTransportProfile <iot-profile-name>`	`iot use-radio-profile <iot-profile-name>`

In addition to enabling the iot radio-profile it has to be assigned to an AP group in ArubaOS/controller based deployments using the following configuration:

ap-group <ap-group-name>
    iot radio-profile <iot-profile-name>

For details about the ap-group configuration refer to the ArubaOS CLI Reference - ap-group.

Note:
Multiple iot radio-profile’s can be configured but a maximum of two, one internal and one external can be enabled per access point (Aruba Instant) or access point group (ArubaOS).