Our step-by-step guide to configure Aruba AP & compute infrastructure with Pareto Anywhere.
Configure (AOS 10.x) APs as IoT infrastructure for reelyActive's open source middleware
Tutorials to consider instead
One or more HPE Aruba Networking access points.
Instantiate an IoT Connector on the AP(s) or on an external server.
In Aruba Central:
A Manage Connector dialog should appear.
In the Manage Connector dialog:
Then click Confirm to create the connector on each AP.
For larger-scale deployments, a Data Collector is the preferred platform. Consult the Aruba documentation should you choose this option.
The IoT Connector will begin to deploy to the AP(s).
Observe the IoT Operations dashboard update as the IoT Connector is deployed.
The number of Bluetooth Low Energy (BLE) devices in range of the APs will appear in the IoT Devices card. The APs are already collecting ambient data! Classifying, filtering and interpreting this ambient data is covered in the next step.
Choose IoT Applications to classify the devices of interest.
In Aruba Central, browse to the IoT Operations dashboard by selecting the target AP Group, Applications menu item and IoT Operations tab.
Click Manage in the IoT Applications card.
The list of available apps should appear, where each card represents an IoT Application.
Browse through the IoT Applications to determine which may be of interest in the context of your deployment.
IoT Applications are regularly added. It's worth checking the list periodically to discover new possibilities.
Select the card of any IoT Application of interest and click Install to deploy it to the IoT Connector(s).
The IoT Applications card in the IoT Operations dashboard will update to show the status of each app across all IoT Connectors.
As required, again click Manage in the IoT Applications card to install, update or remove apps.
reelyActive maintains IoT Applications both for technology partners and for our own open source IoT technologies.
From the IoT Operations dashboard, in the IoT Devices card, click View to see the list of devices detected—and classified— by the AP(s).
Click on the Address of any device to see additional data collected by the AP and processed by any corresponding IoT Apps.
Create an IoT Transport Profile.
In Aruba Central, browse to the IoT Operations dashboard by selecting the target AP Group, Applications menu item and IoT Operations tab.
Click Manage in the Transports card.
Click + in the transports table to create a new transport profile. An Add Transport Profile dialog should appear. Complete the fields as follows:
Parameter | Value | Notes |
---|---|---|
Name | reelyActive | User-defined |
Description | Pareto Anywhere | User-defined |
Stream Type | Data Frames | Forwards payload/sensor data |
Subscriptions | ... | Application-specific device class filters |
Protocol Type | WSS | Only secure WebSockets are supported |
URL | wss://xxx.xxx.xxx.xxx:3001/aruba/aos10 | Specify the target IP & port |
Format Type | protobuf | Efficient data encoding for transport |
Authentication | Use token | Currently ignored by Pareto Anywhere |
Click Create to create the IoT transport profile.
The IoT transport profile will deploy to the IoT Connector. A certificate will be required to establish a secure WebSocket connection, which is covered next.
In Aruba Central:
Click + in the certificates table to add a new certificate. An Add Certificate dialog should appear. Complete the fields as follows:
Parameter | Value | Notes |
---|---|---|
Name | Pareto Anywhere | User-defined |
Type | CA Certificate | Certification Authority (CA) certificate |
Format | PEM | Privacy Enhanced Mail (PEM) |
Certificate File | certificate.pem | User-generated |
The generation of the certificate file is outside the scope of this tutorial. For instructions to create a self-signed certificate for testing on a local network see the Creating Certificates for Secure WebSockets on Local Network section of our barnowl-aruba module documentation.
Click Add to upload the certificate.
The certificate will automatically be deployed to the IoT Controller, and the secure WebSocket connection will be attempted. Observing data in Pareto Anywhere requires no additional action if an instance based on the pareto-anywhere package is running, or, for quick-and-dirty validation, run barnowl-aruba as described below.
If a Pareto Anywhere installation based on the pareto-anywhere package is already present and running on the target computer on the host network, the data forwarded by the IoT Transport Profile should be available in both the web apps and APIs.
Add the corresponding certificate.pem and key.pem files to the /config folder of pareto-anywhere. Pareto Anywhere will automatically detect these files on boot and use HTTPS & WSS for secure operation, which is required by IoT Operations.
To quickly validate that data is correctly received on the target computer on the host network, it is possible to run barnowl-aruba standalone to initiate a WebSocket server on port 3001 using the /aruba/aos10 route as follows:
git clone https://github.com/reelyactive/barnowl-aruba.git npm install npm start
If the access point is correctly configured, and at least one compatible Bluetooth Low Energy device is advertising in range, raddec data should appear in the console.
AOS 10 requires secure WebSockets (wss://): consult the barnowl-aruba documentation regarding the npm run secure option.
Our cheatsheet details the raddec, dynamb and spatem JSON output from the open source IoT middleware.
Tutorial prepared with ♥ by jeffyactive.
You can reelyActive's open source efforts directly by contributing code & docs, collectively by sharing across your network, and commercially through our packages.Continue exploring our open architecture and all its applications.