IoT Operations

Aruba Central supports transporting IoT data over an enterprise WLAN Wireless Local Area Network. WLAN is a 802.11 standards-based LAN that the users access through a wireless connection.. IoT data from partners who provide access control systems, industrial manufacturing systems, hospital, healthcare management, hospitality, and building management systems is supported. APs receive data from the IoT devices and send the dashboard metadata to Aruba Central and the IoT data to external servers through IoT Connectors. The IoT Connector aggregates the device data, performs edge-compute, and runs business logic on the raw data before sending the dashboard metadata and IoT data. Partner-developed applications can be used to send the IoT data to external servers.

Aruba Central provides IoT Connector control, management, and dashboard visibility. The dashboard provides a view of the IoT Connectors, IoT devices, and installed applications. An application store that contains the applications from supported partners is integrated with Aruba Central. Aruba Central does not store the device data, display the device data, or derive insights from the device data. The following is an illustration of IoT Operations architecture.

Figure 1  IoT Operations Architecture

Licensing

IoT Operations is available to Aruba Central customers using ArubaOS 10, with Foundation and/or Advanced AP licenses. Separate licenses are not required for IoT Operations.

IoT Operations utilizes an IoT Connector to receive IoT data from APs and sends IoT device metadata to Aruba Central and IoT data to partner cloud servers. The APs that are assigned to an IoT Connector utilize their IoT radios to act as IoT gateways for myriad IoT devices in the physical environment.

Aruba uses the license tier of APs assigned to your IoT Connector to determine the user experience. Currently, that user experience is differentiated in the IoT Operations Application Store. You will either have access to all apps in the IoT Operations Application Store or some of the apps in the IoT Operations Application Store. Regardless of license tier, the supported scale and base functionality of IoT Operations are the same. In the future, Aruba may add new capabilities to IoT Operations which may extend across apps or even be offered independently of the apps themselves. The user experience is currently determined in IoT Operations as:

• When all APs assigned to an IoT Connector have an Advanced AP license, you have access to all apps in the IoT Operations Application Store.
• When at least one AP assigned to an IoT Connector has a Foundation AP license, you have access to a subset of apps in the IoT Operations Application Store. The apps that are available are shown in full color, while the apps that are unavailable are shaded gray.

Filters can be used in the IoT Operations App Store user interface to further refine your app search.

Terminology

IoT Operations uses the following terminology:

Table 1: IoT Operations Terminology

Term	Description
Data Collector	A Data Collector is a platform that processes network data. A Data Collector is available both as a physical appliance or a virtual appliance.
IoT Connector	An IoT Connector is an application that runs on the Data Collector platform. The IoT Connector receives IoT data from APs through a secure tunnel. An IoT Connector sends the IoT metadata to Aruba Central and the IoT device details to the endpoints of third party partners.
IoT Transport Profile	An IoT transport profile allows an IoT Connector to send the collected IoT data to a partner server.
IoT Radio Profile	An IoT radio profile runs on an AP and it allows an AP to collect IoT data from the IoT devices.
Apps	Apps are developed by partners and are available on the App Store. Apps are deployed on IoT Connectors and run inside the IoT Connector.
Applications	Applications is an element in the Aruba Central web user interface.
IoT Devices	IoT devices are client devices using BLE Bluetooth Low Energy. The BLE functionality is offered by Bluetooth® to enable devices to run for long durations with low power consumption., Zigbee, or other protocols to communicate with Aruba APs.

Specifications

IoT Operations supports the following specifications:

Table 2: IoT Operations Specifications

Parameter	Mini VM Virtual Machine. A VM is an emulation of a computer system. VMs are based on computer architectures and provide functionality of a physical computer.	Small VM	Medium VM	DC-2000
APs	50	250	1000	1000
BLE Devices	2000	5000	20000	20000
Zigbee Devices	200	500	2000	2000

The IoT Connectors support the following specifications:

Table 3: IoT Connector Specifications

Parameter	Mini VM	Small VM	Medium VM	DC-2000
CPU Central Processing Unit. A CPU is an electronic circuitry in a computer for processing instructions. (cores)	4	8	24	24
Memory (GB)	4	16	64	64
Storage (GB)	256	256	480	512

IoT Connectors are available as virtual appliances or physical appliances. Before you can use an IoT Connector, you need to set up appliances. To setup virtual appliances, see Set Up Virtual Appliances.

Configuring IoT Operations

The Applications > IoT Operations page displays the IoT Connectors, IoT devices, and apps. The page also allows to configure the IoT Connectors, IoT transport profiles, and install the apps.

Pre-requisites

Ensure that the following pre-requisites are met before configuring IoT Operations:

• An x86-based ESXi server for VMs is available.
• Aruba APs run ArubaOS 10.

Configuring IoT Operations involves:

• Opening Firewall Ports for IoT Connector Communication
• Downloading IoT Connector
• Deploying IoT Connector
• Creating IoT Connector
• Viewing IoT Connector
• Updating IoT Connector
• Deleting IoT Connector
• Resetting CLI Password of IoT Connector
• Opening Remote Console Session for IoT Connector
• Creating IoT Radio Profile
• Enabling IoT Radio Profile
• Assigning AP to IoT Connector
• Installing Partner-Developed App
• Configuring IoT Transport Profile
• Synchronizing CA Certificate

Opening Firewall Ports for IoT Connector Communication

Most of the communication between IoT Connector and Aruba Central server in the cloud is carried out through HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. (TCP Transmission Control Protocol. TCP is a communication protocol that defines the standards for establishing and maintaining network connection for applications to exchange data. 443). To allow IoT Connector to communicate over a network firewall Firewall is a network security system used for preventing unauthorized access to or from a private network., ensure that the following domain names and ports are open:

Network Requirements for IoT Connector

The network requirements for IoT connector include:

• Static IP address
• Outbound Internet Access on TCP port 443

Network Services (Internal or External) from IoT Connector

The network services (internal or external) requirements from the IoT Connector include:

• TCP/UDP User Datagram Protocol. UDP is a part of the TCP/IP family of protocols used for data transfer. UDP is typically used for streaming media. UDP is a stateless protocol, which means it does not acknowledge that the packets being sent have been received. 53 (DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.)
• UDP 123 (NTP Network Time Protocol. NTP is a protocol for synchronizing the clocks of computers over a network.)
• Production Core Update Server and Port: coreupdate-prod.central.arubanetworks.com and https tcp port 443
• Container Registry URL Uniform Resource Locator. URL is a global address used for locating web resources on the Internet. and Port: quay.io (allow subdomains also)and https tcp 443
• Aruba Cloud URL Discovery Server and Port: api-csp.central.arubanetworks.com and https tcp 443
• Domain Names for Aruba Central
• Domain Names for Hybrid Endpoints
• Domain Names for RCS

Domain Names for Aruba Central

Aruba Central supports the following domain names:

Table 4: Domain Names for Aruba Central

Region	Domain Name	Protocol
US-1	app.central.arubanetworks.com	HTTPS TCP port 443
US-2	app-prod2.central.arubanetworks.com	HTTPS TCP port 443
US-WEST-4	app-uswest4.central.arubanetworks.com	HTTPS TCP port 443
EU-1	app2-eu.central.arubanetworks.com	HTTPS TCP port 443
EU-Central	app-eucentral3.central.arubanetworks.com	HTTPS TCP port 443
CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate.-Central	app-ca.central.arubanetworks.com	HTTPS TCP port 443
CN Common Name. CN is the primary name used to identify a certificate. -North	app.central.arubanetworks.com.cn	HTTPS TCP port 443
AP-South	app2-ap.central.arubanetworks.com	HTTPS TCP port 443
AP-Northeast	app-apaceast.central.arubanetworks.com	HTTPS TCP port 443
AP-Southeast	app-apacsouth.central.arubanetworks.com	HTTPS TCP port 443
UAE-North	app-uaenorth1.central.arubanetworks.com	HTTPS TCP port 443

Domain Names for Hybrid Endpoints

Aruba Central supports the following hybrid endpoints:

Table 5: Domain Names for Hybrid Endpoints

Region	Domain Name	Protocol
US-1	app1-hybrid.central.arubanetworks.com	HTTPS TCP port 443
US-2	hc-prod2.central.arubanetworks.com	HTTPS TCP port 443
US-WEST-4	uswest4-hc.central.arubanetworks.com	HTTPS TCP port 443
EU-1	central-eu-hc.central.arubanetworks.com	HTTPS TCP port 443
EU-3	eucentral3-hc.central.arubanetworks.com	HTTPS TCP port 443
Canada-1	ca-hc.central.arubanetworks.com	HTTPS TCP port 443
APAC-1	apac-hc.central.arubanetworks.com	HTTPS TCP port 443
APAC-EAST1	apaceast-hc.central.arubanetworks.com	HTTPS TCP port 443
APAC-SOUTH1	apacsouth-hc.central.arubanetworks.com	HTTPS TCP port 443
UAENORTH1	uaenorth1-hc.central.arubanetworks.com	HTTPS TCP port 443

Domain Names for RCS

Aruba Central supports the following domain names for RCS:

Table 6: Domain Names for RCS

Region	Domain Name	Protocol
US-1	rcs-ng-prod.central.arubanetworks.com	SSH Secure Shell. SSH is a network protocol that provides secure access to a remote device. port 443
	rcs-ng-xp-prod.central.arubanetworks.com
US-2	rcs-ng-central-prod2.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-central-prod2.central.arubanetworks.com
US-WEST-4	rcs-ng-uswest4.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-uswest4.central.arubanetworks.com
EU-1	rcs-ng-eu.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-eu.central.arubanetworks.com
EU-3	rcs-ng-eucentral3.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-eucentral3.central.arubanetworks.com
Canada-1	rcs-ng-starman.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-starman.central.arubanetworks.com
China-1	rcs-ng-china-prod.central.arubanetworks.com.cn	SSH port 443
APAC-1	rcs-ng-apac.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-apac.central.arubanetworks.com
APAC-EAST1	rcs-ng-apaceast.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-apaceast.central.arubanetworks.com
APAC-SOUTH1	rcs-ng-apacsouth.central.arubanetworks.com	SSH port 443
	rcs-ng-xp-apacsouth.central.arubanetworks.com
UAENORTH1	rcs-ng-uaenorth1.central.arubanetworks.com	SSH port 443

Downloading IoT Connector

IoT Connectors are available as OVA Open Virtualization Archive. OVA contains a compressed installable version of a virtual machine. files. To download an OVA file, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Maintain, click Organization > Platform Integration.
3. If an IoT Connector has not been deployed, the Data Collector card displays the number of deployed IoT connectors as 0. Click 0 and in the Get Started card, click the Virtual Appliance link.
4. If IoT Connectors have been deployed, the Data Collector card displays the number of deployed IoT Connectors. Click the displayed number and in the Configure Appliance card, click the Download Virtual Appliance link.
5. In the Download Virtual Appliance dialog, click Mini, Small, or Medium. For additional information, see Specifications.
6. Click Close.

Deploying IoT Connector

Before deploying an OVA file, download the OVA file. For additional information, see Downloading IoT Connector.

To deploy an IoT connector on a VMWare server, complete the following procedure:

1. Log in to the VMware server.
2. Click File > Deploy OVF Template.
3. Click Browse and select the OVA file.
4. Click Next.
5. After the OVA file is deployed, click Console.
6. Log in to the console with the following credentials:
   • Username as aruba
   • Password as aruba
7. Change the password. For additional information, see Performing Advanced Options.
8. Configure the hostname. For additional information, see Configuring Hostname.
9. Configure the network with static IP address, mask, gateway, and DNS server. For additional information, see Using Command Line Interface Options.
10. Test the network connectivity. For additional information, see Using Command Line Interface Options.
11. Configure the timezone. For additional information, see Using Command Line Interface Options.
12. Register the IoT Connector to Aruba Central by using a registration token. For additional information, see Creating Registration Tokens.

Creating IoT Connector

Before creating an IoT Connector, you should download and deploy an IoT Connector. For additional information, see Downloading IoT Connector and Deploying IoT Connector.

To create an IoT Connector, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. The Connectors card displays a graph of configured IoT connectors. Click Show Connectors.

   If an IoT Connector is not configured, the Connectors card displays Add Connector. Click Add Connector to create an IoT Connector.

4. In the Connectors table, click the Add Connector icon.
5. In the Data Collectors page, click the graph in the Managed Collectors card.
6. In the Managed Collectors page, click Create Collector.

   Ensure that an IoT Connector is deployed and registered in Aruba Central. For additional information, see Deploying IoT Connector.

7. In Give collector a name, enter an IoT Connector name.
8. In Select an application to install on collector, select IoT Connector.
9. Click Next.
10. Select the collector and click Create.

    It takes at least 30 min for a newly created IoT Connector to come online.

Creating IoT Radio Profile

An IoT radio profile allows an AP to collect IoT data from IoT devices. An IoT radio profile can be created for an AP group with APs running ArubaOS 10 or an AP group with APs running ArubaOS 8.x.

Creating IoT Radio Profile for ArubaOS 10 Group

To create an IoT radio profile for an ArubaOS 10 group, complete the following procedure:

1. In the Aruba Central app, set the filter to an ArubaOS 10 group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the IoT Radio Profiles table, click the Add icon.
7. Configure the following parameters and click Save Settings.

Table 7: IoT Radio Profile for 10.x Group

Parameter	Description
Name	Name of the radio profile.
Radio	Type of radio. Select a radio type from the drop-down list:  Internal—Use internal radio. External—Use external radio.
Radio mode	Mode of radio. Select a radio mode from the drop-down list:  None—Do not use radio. BLE—Use BLE radio. Zigbee—Use Zigbee radio. BLE & Zigbee—Use BLE and Zigbee radio. SD-Radio—Use software defined radio. NOTE: When the radio mode is set to BLE & Zigbee, BLE-Tx and Zigbee work together, but BLE-Rx and Zigbee do not work together.
BLE operation mode	Operation mode of BLE. Select a BLE operation mode from the drop-down list: Beaconing—Use beaconing mode. Scanning—Use scanning mode. Both—Use both beaconing and scanning modes. This parameter is available only when radio mode is BLE or BLE & Zigbee. NOTE: When the radio mode is set to BLE & Zigbee, the BLE operation mode can only be set to Beaconing.
Console	Mode of BLE console. Select a BLE console from the drop-down list: Auto—Use automatic BLE console. On—Use BLE console. Off—Do not use BLE console. This parameter is available only when the radio mode is BLE or BLE & Zigbee.
Tx power	Transmission power. Enter a value from the range: -40, -20, -16, -12, -8, -4, 0, 2, 3, 4, 5, 6, 7, 8, 20. APs with Gen-2 BLE/IoT radios adjust the calibrated 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. values for iBeacon advertisements when the BLE transmission power level is modified. The calibrated values can be verified using the show ap debug ble-advertisement-info command. NOTE: This parameter is available only when the radio mode is BLE or BLE & Zigbee.
Zigbee operation mode	Operation mode of Zigbee coordinator. This parameter is available only when the radio mode is Zigbee or BLE & Zigbee.
Channel	Zigbee channel assignment. Select one of the following Zigbee channel assignments from the drop-down list: Automatic—Automatically assign Zigbee channel. Manual—Manually assign Zigbee channel. This parameter is available only when the radio mode is Zigbee or BLE & Zigbee.

By default, a new IoT radio mode is in disabled state. To enable a new IoT radio profile, see Enabling IoT Radio Profile.

Creating IoT Radio Profile for 8.x Group

To create an IoT radio profile for an 8.x group, complete the following procedure:

1. In the Aruba Central app, set the filter to an 8.x group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the IoT Radio Profiles table, click the Add icon.
7. Configure the following parameters and click Save Settings.

Table 8: IoT Radio Profile for 8.x Group

Parameter	Description
Name	Name of the radio profile.
Radio	Type of radio. Select a radio type from the drop-down list:  Internal—Use internal radio. External—Use external radio.
Radio mode	Mode of radio. Select a radio mode from the drop-down list:  None—Do not use radio. BLE—Use BLE radio. Zigbee—Use Zigbee radio. BLE & Zigbee—Use BLE and Zigbee radio. NOTE: When the radio mode is set to BLE & Zigbee, BLE-Tx and Zigbee work together, but BLE-Rx and Zigbee do not work together.
Zone	Zone in which the IoT radio profile works.
BLE operation mode	Operation mode of BLE. Select a BLE operation mode from the drop-down list: Beaconing—Use beaconing mode. Scanning—Use scanning mode. Both—Use both beaconing and scanning modes. This parameter is available only when radio mode is BLE or BLE & Zigbee. NOTE: When the radio mode is set to BLE & Zigbee, the BLE operation mode can only be set to Beaconing.
Console	Mode of BLE console. Select a BLE console from the drop-down list: Auto—Use automatic BLE console. On—Use BLE console. Off—Do not use BLE console. This parameter is available only when Radio mode is BLE or BLE & Zigbee.
Tx power	Transmission power. Enter a value from the range: -40, -20, -16, -12, -8, -4, 0, 2, 3, 4, 5, 6, 7, 8, 20. APs with Gen-2 BLE/IoT radios adjust the calibrated RSSI values for iBeacon advertisements when the BLE transmission power level is modified. The calibrated values can be verified using the show ap debug ble-advertisement-info command. NOTE: This parameter is available only when the radio mode is BLE or BLE & Zigbee.
Zigbee operation mode	Operation mode of Zigbee coordinator. This parameter is available only when the radio mode is Zigbee or BLE & Zigbee.
Channel	Zigbee channel assignment. Select one of the following Zigbee channel assignments from the drop-down list: Automatic—Automatically assign Zigbee channel. Manual—Manually assign Zigbee channel. This parameter is available only when the radio mode is Zigbee or BLE & Zigbee.

By default, a new IoT radio mode is in disabled state. To enable a new IoT radio profile, see Enabling IoT Radio Profile.

Enabling IoT Radio Profile

To enable an IoT radio profile, complete the following procedure:

1. In the Aruba Central app, set the filter to a group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the IoT Radio Profiles table, hover over an IoT radio profile.
7. Click the WiFi icon.

Creating Zigbee Service Profile

A Zigbee service profile can be created for an AP group with APs running ArubaOS 10.x or an AP group with APs running ArubaOS 8.x.

To create a Zigbee service profile, complete the following procedure:

1. In the Aruba Central app, set the filter to a group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the Zigbee Service Profiles table, click the Add icon.
7. Configure the following parameters and click Save Settings.

Table 9: Zigbee Service Profile

Parameter	Description
Name	Name of the Zigbee service profile.
Security	Use security in the Zigbee network.
PAN ID	Hexadecimal Personal Area Network (PAN) identifier of the Zigbee network. Select one of the following options from the drop-down list: Automatic—Use automatic PAN ID. Manual—Use manual PAN ID.
Radio	Type of radio. Select a radio type from the drop-down list:  Internal—Use internal radio. External—Use external radio.
Allow device to join	Permits the Zigbee devices to join the network. Select one of the following options from the drop-down list: On-demand—Allow devices to join on demand. Always—Always allow deices to join.
Trust center link key	Link key of the trust center.

Configuring BLE Beacon Service Profile

The BLE Beacon Service (BBS) profile manages the BLE beacons as iBeacons or custom beacons. These beacons may be configured on Aruba Central or Aruba Central API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software.. The BBS profile automatically assigns the beacons to the APs and allows Aruba Central to monitor them. A BBS profile can be created for an AP group with APs running ArubaOS 10.x or an AP group with APs running ArubaOS 8.x.

Creating BBS Profile for 10.x Group

To create a BBS profile for a 10.x group, complete the following procedure:

1. In the Aruba Central app, set the filter to a 10.x group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the BLE Beacon Service Profile table, click the Add icon.
7. Configure the following parameters and click Save Settings.

Table 10: BBS Profile for 10.x Group

Parameter	Description
Name	Name of the BLE beacon service profile.
Radio	Type of radio. Select a radio type from the drop-down list:  Internal—Use internal radio. External—Use external radio. All—Use both internal and external radios.
Beacon Configuration Method	Method for beacon configuration. Select a method from the drop-down list: Auto Generated—Use an automatically generated beacon configuration method. Aruba Central API—Use a beacon configuration method generated by Aruba Central API. IoT Operations App—Use a beacon configuration method generated by Aruba Central.
Profile Identifier	Identifier of the beacon profile.
Advertising Format	Format to use while advertising the BLE beacon. Select a BLE beacon advertising format from the drop-down list: iBeacon—Use iBeacon advertising format. Custom—Use custom advertising format. If Beacon Configuration Method is set to Auto Generated, select iBeacon as the BLE beacon advertising format. If Beacon Configuration Method is set to Aruba Central API or IoT Operations App, configure the API gateway.
Advertising Interval	Time interval in milliseconds to advertise the beacon. This parameter has a range from 100 ms to 30000 ms in increments of 100 ms. If Beacon Configuration Method is set to Auto Generated, select iBeacon as the BLE beacon advertising format. If Beacon Configuration Method is set to Aruba Central API or IoT Operations App, configure the API gateway.
UUID	Ibeacon UUID in xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx format. This parameter is available only when the Advertising Format is set to iBeacon.
Major Range	Ibeacon major range as either a single number or range from 0 to 65535. This parameter is available only when the Advertising Format is set to iBeacon.
Minor Range	Ibeacon minor range as either a single number or range from 0 to 65535. This parameter is available only when the Advertising Format is set to iBeacon.
Custom Value	Custom value with 3 to 31 bytes hexadecimal string and may include BTMAC or BTMACR macro. This parameter is available only when the Advertising Format is set to Custom.

Creating BBS Profile for 8.x Group

To create a BBS profile for an 8.x group, complete the following procedure:

1. In the Aruba Central app, set the filter to an 8.x group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the BLE Beacon Service Profile table, click the Add icon.
7. Configure the following parameters and click Save Settings.

Table 11: BBS Profile for 8.x Group

Parameter	Description
Name	Name of the BLE beacon service profile.
Radio	Type of radio. Select a radio type from the drop-down list:  Internal—Use internal radio. External—Use external radio. All—Use both internal and external radios.
Beacon Configuration Method	Method for beacon configuration. Select a method from the drop-down list: Auto Generated—Use an automatically generated beacon configuration method. Aruba Central API—Use a beacon configuration method generated by Aruba Central API.
Profile Identifier	Identifier of the beacon profile.
Advertising Format	Format to use while advertising the BLE beacon. Select a BLE beacon advertising format from the drop-down list: iBeacon—Use iBeacon advertising format. Custom—Use custom advertising format. If Beacon Configuration Method is set to Auto Generated, select iBeacon as the BLE beacon advertising format. If Beacon Configuration Method is set to Aruba Central API, configure the API gateway.
Advertising Interval	Time interval in milliseconds to advertise the beacon. This parameter has a range from 100 ms to 30000 ms in increments of 100 ms. If Beacon Configuration Method is set to Auto Generated, select iBeacon as the BLE beacon advertising format. If Beacon Configuration Method is set to Aruba Central API, configure the API gateway.
UUID	Ibeacon UUID in xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx format. This parameter is available only when the Advertising Format is set to iBeacon.
Major Range	Ibeacon major range as either a single number or range from 0 to 65535. This parameter is available only when the Advertising Format is set to iBeacon.
Minor Range	Ibeacon minor range as either a single number or range from 0 to 65535. This parameter is available only when the Advertising Format is set to iBeacon.
Custom Value	Custom value with 3 to 31 bytes hexadecimal string and may include BTMAC or BTMACR macro. This parameter is available only when the Advertising Format is set to Custom.

Assigning AP to IoT Connector

Assigning an AP to an IoT Connector allows an AP to send the collected data to an IoT Connector. One or more unassigned APs can be assigned to an IoT Connector. An unassigned AP is an AP that is not assigned to any IoT Connector.

To assign an AP to an IoT Connector, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. In the Connectors graph, click Show Connectors.
4. In the Connectors page, click the AP Collector Association icon.
5. Click the Expand icon on the left side of the required Connector ID.
6. In the Assigned Access Points table, click the Assign to Connector icon.
7. In the <Connector-name> Assigned AP's (Unassigned) table, select one or more APs, and ensure that the firmware version of the APs is 10.

   Only unassigned APs can be assigned to an IoT Connector. The Connector > Assigned AP's table lists the ArubaOS version running on the AP in the Firmware Version column.

8. Click Confirm.

Installing Partner-Developed App

To install a partner-developed app from the App Store, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. Click on an IoT Connector listed in the IoT Applications graph.
4. In the Available Apps card, click an available App.

   The Available Apps list displays all available IoT applications.

5. In the App Details page, click Install.

Uninstalling Partner-Developed App

To uninstall a partner-developed app, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. Click on an IoT Connector listed in the IoT Applications graph.
4. Click on an installed IoT application.
5. Click Uninstall.

Configuring IoT Transport Profile

Aruba recommends to use partner-developed apps from the App Store. If you do not want to use a partner-developed app, configure an IoT transport profile. Configuring an IoT transport profile allows an IoT Connector to send the collected data to a partner server.

To configure an IoT transport profile, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. In the Connectors graph, click Show Connectors.
4. In the Connectors table, click on the Name of an IoT Connector.
5. In Transports card, click Manage.
6. In the Transport Profiles on Connector <Connector-name> table, click the Add Transport Profile icon.
7. Configure the following IoT transport profile parameters and click Create.

   If an IoT transport profile is not configured, the Transport Profile on Connector table displays Add. Click Add to configure an IoT transport profile.

Table 12: IoT Transport Profile

Parameter	Description
Profile
Name	Name of the IoT transport profile.
Description	Description of the IoT transport profile.
Stream Type	Type of the data stream. Available options are: Periodic Telemetry—Send the data stream periodically. Data Frames—Send each data frame when the data is available.
Aggregation
Reporting Interval (seconds)	Period to aggregate the data stream. This parameter is available when Stream Type is set to Periodic telemetry. This parameter does not have a default value and takes any value in the range of 30 seconds to 3600 seconds.
RSSI Aggregation Type	Type of RSSI aggregation. This parameter is available when Stream Type is set to Periodic telemetry. Available options are: Average—Use average value when aggregating the data stream. Latest—Use the latest value when aggregating the data stream. Max—Use the maximum value when aggregating the data stream.
Subscriptions
Type	Type of subscription. A subscription consists of a type and value. Device class is the supported type. Multiple subscriptions are allowed with an OR operator between subscriptions. Use the Add icon to add subscriptions.
Value	Available device classes. Multiple subscriptions are allowed with an OR operator between subscriptions. Use the Add icon to add subscriptions.
Filters
Filters	Type of filter. A filter consists of type and value. The supported type is Ibeacon UUID and the value is a UUID. Multiple filters are allowed with an OR operator between filters. Use the Add icon to add filters.
Destination
Protocol Type	WSS protocol is used when sending data. Custom CA certificates can be uploaded and synchronized when using WSS protocol. For more information on uploading CA certificate, see Certificates. For more information on synchronizing CA certificates, see Synchronizing CA Certificate.
URL	URL of the destination server.
Format Type	Format of the data. Available options are: JSON—Format the data in JSON JavaScript Object Notation. JSON is an open-standard, language-independent, lightweight data-interchange format used to transmit data objects consisting of attribute–value pairs. JSON uses a "self-describing" text format that is easy for humans to read and write, and that can be used as a data format by any programming language. format. PROTOBUF—Format the data in PROTOBUF.
Authentication
Use Credentials	Use the configured credentials as authentication method. Credentials include: Authentication URL—URL of the authentication server. Client ID—Identify of the client. Username—Username for authentication. Password—Password for authentication.
Use Token	Use the configured token as the authentication method.

Deleting an IoT Transport Profile

To delete an IoT transport profile, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations.
3. In the Connectors graph, click Show Connectors.
4. In the Connectors table, click on the Name of an IoT Connector.
5. In the Transports card, click Manage.
6. In the Transport Profiles on Connector <Connector-name> table, hover over an IoT transport profile.
7. Click the Delete icon.
8. In the Delete Transport Profile on Connector <Connector-name> dialog, click Delete.

Assigning a Certificate

Aruba Central includes a default certificate that is not signed by a root Certificate Authority (CA). For devices to validate and authorize Aruba Central, upload a valid certificate that is signed by a root CA. For additional information, see Certificates.

To assign a certificate, complete the following procedure:

1. In the Aruba Central app, set the filter to a group that contains an AP.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click Security.
6. Click Certificate Usage.
7. Select a CA certificate from the WebCC CA Cert drop-down list. A CA certificate is automatically selected in the IOT CA Cert table.
8. Click Save Settings.

Synchronizing CA Certificate

CA certificates are synchronized to collectors automatically when they are uploaded in Aruba Central.

Configuring SES Imagotag

To configure SES Imagotag, complete the following procedure:

1. In the Aruba Central app, set the filter to an ArubaOS 10 group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. Expand SES Imagotag.
7. Configure the following parameters and click Save Settings.

Table 13: SES Imagotag Parameters

Parameter	Description
SES Imagotag server name or IP	Name or IP address of SES Imagotag server. NOTE: Name can have up to 127 characters.
SES Imagotag channel	Channel to use when communicating with SES Imagotag server.
SES Imagotag authentication	Enable authentication with SES Imagotag server.
SES Imagotag FQDN verify	Enable FQDN Fully Qualified Domain Name. FQDN is a complete domain name that identifies a computer or host on the Internet. check of SES Imagotag server.

Creating IoT Transport Stream

An IoT transport stream can be created for an AP group with APs running ArubaOS 8.x.

To create an IoT transport stream for an AP group, complete the following procedure:

1. In the Aruba Central app, set the filter to an 8.x group.
2. Under Manage, click Devices.
3. Click the Config icon.
4. Click Show Advanced.
5. Click IoT tab.
6. In the IoT Transport Streams table, click Add IoT Transport Stream icon.
7. Configure the following IoT transport stream parameters and click Save Settings.

Table 14: IoT Transport Stream

Parameter	Description
Name	Name of the IoT transport stream.
Server URL	URL of the server to send the data stream.
Server Type	Type of the server. Available options are: Meridian Beacon Management—Send the data stream to a Meridian beacon management server. Meridian Asset Management—Send the data stream to a a Meridian asset management server. Telemetry Https—Send the data stream to a telemetry server over HTTPS. Telemetry Websocket—Send the data a telemetry server over websocket. Assa Abloy—Send the data stream to an Assa Abloy server. Azure IoT Hub—Send the data stream to an Azure IoT hub.
Device class	Class of the device.
Reporting Interval	Time interval, in seconds, to report the data stream. Default value is 600 seconds.
Zone	Define the zone in which the IoT transport stream works.
BLE Periodic Telemetry	Enable periodic BLE telemetry.
BLE Data Forwarding	Enable BLE data forwarding.
Per Frame Filtering	Enable per frame filtering.
Report device counts only	Enable reporting of only device count.
Cipher List	Cipher list to use when sending data stream. Available options are: Standard—Use standard ciphers. FIPS—Use FIPS Federal Information Processing Standards. FIPS refers to a set of standards that describe document processing, encryption algorithms, and other information technology standards for use within non-military government agencies, and by government contractors and vendors who work with these agencies. compliant ciphers. Compatible—Use compatible ciphers.
Authentication
Use Credentials	Use credentials for authentication with authentication server.
Use Token	Use token for authentication with authentication server.
Client Credentials	Use credentials of client for authentication with authentication server.
Authentication URL	URL of the authentication server. This parameter is available when using credentials or client credentials for authentication.
Username	Username to use for authentication with authentication server. This parameter is available when using credentials for authentication.
Password	Password to use for authentication with authentication server. This parameter is available when using credentials for authentication.
Client ID	ID of the client for authentication with authentication server.
Access Token	Token for authentication with the authentication server. This parameter is available when using token for authentication.
Client Secret	Token for authentication with the authentication server. This parameter is available when using client credentials for authentication.
VLAN
VLAN ID	VLAN Virtual Local Area Network. In computer networking, a single Layer 2 network may be partitioned to create multiple distinct broadcast domains, which are mutually isolated so that packets can only pass between them through one or more routers; such a domain is referred to as a Virtual Local Area Network, Virtual LAN, or VLAN. ID to use when sending data stream.
Proxy
Server	URL of the proxy server.
Port	Port of the proxy server.
Username	Username to use with proxy server.
Password	Password to use with proxy server.
Report devices using following parameters	Define which devices are reported. Available options are: Company Identifier—Report devices matching company identifier. Vendor—Report devices matching vendor. Local Name—Report devices matching local name. Service UUID—Report devices matching service UUID. MAC OUI—Report devices matching MAC Media Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.  OUI Organizationally Unique Identifier. Synonymous with company ID or vendor ID, an OUI is a 24-bit, globally unique assigned number, referenced by various standards. The first half of a MAC address is OUI..
Devices Filters
Report devices that are within meters of the beacon	Report devices that are within defined meters of the beacon.
Report devices that have had activity in the last meters since last reported	Report devices that have had activity in the last defined meters since last reported.
Report devices that have had activity in the last	Report devices that have had activity in the last defined time period.
RSSI reporting format	Report devices by defined RSSI reporting format. Available options are: Average—Report devices filtered by average RSSI value. Max—Report devices filtered by maximum RSSI value. Last—Report devices filtered by last RSSI value. Smooth—Report devices filtered by smooth RSSI value. Bulk—Report devices filtered by bulk RSSI value.
Environment Type	Type of device environment. Available options are: Office—Report devices in office environment. Warehouse—Report devices in warehouse environment. Auditorium—Report devices in auditorium environment. Shipboard—Report devices in shipboard environment. Outdoor—Report devices in outdoor environment. Custom—Report devices in custom environment.
Fading Factor	Value of fading factor. This parameter is available when filtering devices in custom environment.

Monitoring IoT Operations

The Applications > IoT Operations page provides a variety of charts (Summary view) and lists (List view) that allow you to assess the status of the IoT Connectors, IoT apps, and IoT devices.

To view the status of the IoT Connectors, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations. The Connectors graph displays a graph of the online and offline IoT Connectors.
3. Click Show Connectors to view the list of IoT Connectors. The Connectors table lists the following additional information:

Table 15: IoT Connectors

Parameter	Description
Name	Name of the connector.
Status	Status of the IoT Connector.
IP Address	IP address of the IoT Connector.
Reported Access Points	Number of access points collecting the data.
IoT Applications	Number of applications running on the IoT Connector.
IoT Devices	Number of IoT devices connected to the IoT Connector.
Classified Devices	Number of IoT devices classified by the IoT Connector.

To view the status of the IoT devices, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations. The IoT Devices graph displays a graph of the IoT devices filtered by By Network Communication Type and By Device Class.
3. Click Show Devices to view the list of IoT devices. The Devices on all Connectors table lists the following additional information:

Table 16: IoT Devices

Parameter	Description
Status	Online or offline status of the devices.
Address	MAC address of the device.
Connector	Name of the IoT Connector assigned to the device.
Classes	Device class of the device.
Last Reported By	MAC address or name of the AP that last reported the device. This is applicable only to BLE devices.
Local Name	Local name of the device.
Company Identifier	BT-SIG registered company identifier of the device.
Last Seen	Date and time when the device was last seen.

To view the status of the IoT apps, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Applications > IoT Operations. The IoT Applications graph displays a graph of the installed apps.
3. Click Show App Store to view the list of apps.

To view the BLE beacons, complete the following procedure:

1. In the Aruba Central app, set the filter to global.
2. Under Manage, click Devices.
3. Under Access Points, click BLE Beacons. The BLE Radios table lists the following additional information:

Table 17: BLE Beacons

Parameter	Description
Access Points	MAC address of AP.
BLE MAC Address	BLE MAC address of AP.
Configuration Profile	BLE beacon service profile identifier.
Radio Instance	Radio of AP.
Advertisement Format	Format of BLE beacon advertised.
Advertisement Format (ms)	Interval of advertising BLE beacon.
Status	Status of BLE beacon.
Major	Ibeacon major UUID.
Minor	Ibeacon minor UUID.

Debug Commands

The following commands are available to debug IoT Operations:

Table 18: Debug Commands

Command	Description	Minimum ArubaOS Version Required
show iot radio-profile	Shows radio profile for BLE and/or Zigbee	10.3.0.0
show ap debug iot-radio-devices	Shows radios for IoT	10.3.0.0
show ap debug iot-radio-counters	Shows counters for radios	10.3.0.0
show ap debug ble-config	Shows configuration/status on AP side	10.3.0.0
show ap debug ble-firmware-upgrade-info	Shows BLE upgrade info	10.3.0.0
show ap debug ble-table all	Shows BLE table of devices	10.3.0.0
show ap debug ble-counters	Shows BLE packet counter	10.3.0.0
show ap debug ble-session-status	Shows BLE session information	10.4.0.0
show ap debug ble-action-status	Shows action status for BLE devices	10.3.0.0
show ap debug ble-input-filter-stats	Shows input filter on BLE table	10.3.0.0
show ap debug ble-advertisement-info	Shows BLE advertisement info	10.4.0.0
show ap debug ble-daemon	Shows BLE daemon logs	10.3.0.0
show ap debug ble-relay iot-profile	Shows IoT Transport details	10.3.0.0
show ap debug ble-relay report	Shows BLE relay logs	10.3.0.0
sshow ap debug zigbee radio-table	Shows ZigBee radio table	10.3.0.0
show ap debug zigbee client-table	Shows ZigBeeclient table	10.3.0.0
show ap debug zigbee client-table stats	Shows ZigBee statistics for clients	10.3.0.0
show ap debug zigbee socket-table	Shows socket created by ZSD or Assa Abloy if configured	10.3.0.0
show ap debug zigbee packet-trail	Shows ZigBee packet trail	10.3.0.0
show ap debug zigbee event-trail	Shows ZigBee event trail	10.4.0.0
show ap debug zigbee topology	Shows ZigBee topology	10.4.0.0
show zigbee service-profile <name>	Shows ZigBee service configuration	10.3.0.0
show ap debug usb-device-mgmt device all	Shows all USB Universal Serial Bus. USB is a connection standard that offers a common interface for communication between the external devices and a computer. USB is the most common port used in the client devices. devices connected to this AP	10.3.0.0
show ap debug usb-device-mgmt device detail <device-id, from above output>	Shows detail for USB devices	10.4.0.0
show ap debug usb-device-mgmt device detail interface <iface-id, from above output>	Shows interface for USB devices	10.4.0.0
show ap debug usb-device-mgmt rule all	Shows rule debugging for USB devices	10.3.0.0
show ap debug usb-device-mgmt plugin all	Shows plugin information for USB devices	10.3.0.0
show ap debug usb-enet	Shows device details for Ethernet Ethernet is a network protocol for data transmission over LAN.-over-USB dongles	10.4.0.0
show ap debug usb-enet client	Shows client details for Ethernet-over-USB dongles	10.3.0.0
show usb-enet client table	Shows client details for Ethernet-over-USB dongles (core module)	10.3.0.0
show iot transportProfile	Shows details of IoT Transport Profiles	10.3.0.0
show ap debug iot-audit-trail command-history	Shows trail for commands executed	10.5.0.0
show ap debug iot-audit-trail ble-action	Shows audit trail for BLE SB APIs	10.5.0.0

To issue the debug command, complete the following steps:

1. In the Aruba Central app, set the filter to Global.
2. Under Analyze, click Tools.
3. Click Commands.
4. Use the Commands filter to select the required command.
5. Click Add.
6. Click Run.