IoT Operations

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. Operations works with Aruba APs running ArubaOS 10. If a Template Group is used, ensure that the APs in the Template Group run ArubaOS 10.

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.x, 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:

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 1: 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 DC-2000 is a physical appliance.

The IoT Connectors support the following specifications:

Table 2: 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

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

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:

Domain Names for Aruba Central

See the following table for domain names for Aruba Central:

Table 3: 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

See the following table for domain names for hybrid endpoints:

Table 4: 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

See the following table for domain names for RCS:

Table 5: 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 File

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:

This topic describes the installation of the mini, small, or medium VM on a VMWare server. Skip this topic if the IoT Connector is a DC-2000 appliance.

  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 File

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

The following procedure describes how to deploy a downloaded OVA file on a VMware server:

For detailed instructions on deploying an IoT Connector OVA appliance, see Setting Up Virtual Appliances.

This topic describes the installation of the mini, small, or medium VM on a VMWare server. Skip this topic if the IoT Connector is a DC-2000 appliance.

  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 file. For additional information, see Downloading IoT Connector File and Deploying IoT Connector File.

To create an IoT Connector, complete the following procedure:

Wait at least 30 min between deploying an IoT Connector file and creating an IoT Connector. After 30 min, if Create Collector is not available in Aruba Central, reboot the IoT Connector in the VMware server. The Create Collector is disabled till a new IoT Connector is available.

  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 file is deployed and registered in Aruba Central. For additional information, see Deploying IoT Connector File.

  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

A radio profile allows an AP to collect IoT data from IoT devices. After a radio profile is created, it is in disabled state, by default. To enable a radio profile, see Enabling IoT Radio Profile.

To create a radio profile, complete the following procedure:

  1. In the Aruba Central app, set the filter to a group that contains the required AP.

    IoT Operations works with Aruba APs running ArubaOS 10.

  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 and configure the following parameters:

    Table 6: IoT Devices

    ParameterDescription

    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.

    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. 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.

  7. Click Save Settings.
  8. In the Zigbee Service Profiles table, click the Add icon and configure the following parameters:

    Table 7: IoT Devices

    ParameterDescription

    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.

  9. Click Save Settings

Enabling IoT Radio Profile

A newly created radio profile is in disabled state, by default. To enable a radio profile, complete the following procedure:

  1. In the Aruba Central app, set the filter to a group that contains the required AP.

    IoT Operations works with Aruba APs running ArubaOS 10.

  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.

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.

IoT Operations works with Aruba APs running ArubaOS 10.

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 and configure the following IoT transport profile parameters.

    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 8: IoT Transport Profile

    ParameterDescription

    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.

    RSSI Aggregation Type

    Type of 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. 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:

    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.

  7. Click Create.

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

To synchronize a CA certificate, 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 on an IoT transport profile.
  7. Click the Sync certs to all Connectors icon.

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.

In any chart, hover over any spot or segment to view additional information.

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.
  3. The Connectors graph displays a graph of the online and offline IoT Connectors. Click Show Connectors to view the list of IoT Connectors. The Connectors table lists the following additional information:

    Table 9: IoT Connectors

    ParameterDescription

    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.
  3. The IoT Devices graph displays a graph of the IoT devices filtered by By Network Communication Type and By Device Class. Click Show Devices to view the list of IoT devices. The Devices on all Connectors table lists the following additional information:

    Table 10: IoT Devices

    ParameterDescription

    Status

    Online or offline status of the devices.

    Address

    MAC Media Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network. 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.
  3. The IoT Applications graph displays a graph of the installed apps. Click Show App Store to view the list of apps.