Aruba

Integration guide

Configurations for Aruba Central and Aruba On-Prem

Foot Analytics
FIRST STEPS

Configuration with your Aruba platform

You can connect your Aruba network to iKnos (Foot Analytics platform) using Aruba’s cloud controller, or using up to three different on-prem options.

Central Aruba
Aruba ON-PREM

Aruba Central is Aruba’s cloud controller, from which all the parameters of the different buildings and associated APs can be configured. Currently, there are two licenses available to assign to APs. Specific details for each of them can be found on the official website.

The available integrations are:

Streaming API: available with the Advance License.

Localization Service: available with the Foundation License.

Support matrix

Support matrix. Here you will find the supported products and firmware versions:

Product/VersionCompatible
AOS 8.10 or higherYes
AOS 10.4 or higherYes
ALE 1.xYes
ALE 2.xYes
ALE 3.xYes

Streaming API Integration

It mainly consists of the connection through the WSS (Secure WebSocket) protocol from the Foot Analytics platform to the Aruba Central cloud.
We use a secret credential to connect to the URL indicated by Aruba Central to receive the data.
The customer must activate the API in their Aruba Central control panel by going to the following option:

Organization> Platform Integration > Streaming

Aruba platform integration

Once inside, the Presence event must be enabled, and the Endpoint and Streaming Key must be shared with Foot Analytics (when the button is clicked, it will be saved to the clipboard).

Aruba streaming

RTLS

In this case, Aruba Central allows us to configure the APs to send RTLS (Real Time Location Services) data to the location server of our choice.
Foot Analytics provides a compatible ALE instance. To apply the configuration, we need to access the device tab:

Devices (left menu, 1)> Select AP or Group(2)

Aruba RTLS

Then:

Devices (left menu, 1)> Select the AP or Group(2).

Aruba device

At this point, we can configure the connection for ALE:

Server: 54.76.148.47:8855

Report interval: 10s

Troubleshooting

There are three different methods for connecting Aruba data:

Foot Analytics IAP to ALE

Foot Analytics Client to ALE Controller

Customer ALE to Foot Analytics ALE

Support Matrix

Below you will find the supported products and firmware versions:

Product / VersionCompatible
AOS 8.10 or higherYes
AOS 10.4 or higherYes
ALE 1.xYes
ALE 2.xYes
ALE 3.xYes

IAP Integration

IAPs (Instant Access Points) can connect directly to our ALE in two ways: using the CLI or the Instant UI (recommended).

Connection data required for the customer:

Server: ale.foot.bi

Port: 8855

The user interface / form could look like the following:

Aruba ON-PREM

Controller Integration

The IAPs send the data to the client controller, which forwards it to the Foot Analytics ALE.

Connection data required for the customer:

User: To be defined with the customer

Password: To be defined with the customer

Server: ale.foot.bi

Port: 8855

Connection data required for Foot Analytics:

IP address of the Client Controller

The user interface / form could look like the following:

Aruba IAP

ALE Integration

A WebSocket tunnel is established between two ALEs. The client ALE acts as a WebSocket client, and the Foot Analytics ALE acts as a WebSocket server receiving data from the client. The client must configure its ALE server by applying the following configuration:

ALE > Options > Websocket Tunnel

The user interface / form will be similar to the following:

Aruba-ALE

Then, the following configuration must be added:

Add a local endpoint with the following parameters:

Host: localhost

Port: 7778

Add a remote endpoint with the following parameters:

Server: ale.foot.bi

Port: 443

Troubleshooting