Use this guide to configure Aruba controllers with AOS 8.3.x for use with Meridian Beacon Management and Asset Tracking.

Prerequisites

Configure Clock/NTP services

Configure preferred DNS to reach *.meridianapps.com

Complete These Steps

Complete these steps to enable the Meridian Asset Tracking solution.

Turn on the embedded Bluetooth in your APs and configure your infrastructure for Beacons Management.

Install the DigiCert root certificate on your Managed Devices (MDs) also known as your local controller(s)

Configure the Web Secure Socket between your controller and the Meridian back-end servers.

Deploy your Aruba Access Points using the Beacons app.

Configure your Aruba Asset Tags using the Tags app.

Notes on Web Secure Socket for Asset Tracking

In order for the Web Secure Socket to open between the Aruba Infrastructure and the Meridian Cloud, you must successfully deploy an Aruba AP using the Beacons app and configure an Asset Tag using the Aruba Tags app.

When an Aruba Tag is heard by an access point, the AP sends the RSSI value it's heard to the Meridian Editor using these configuration values. The Editor uses the highest weighted average RSSI value of the Aruba Tag heard by three of APs to track it on the map. This is a continual process for all Aruba Tags being tracked for a location.

Aruba Controller-based WLAN Configuration

The Aruba Wi-Fi network infrastructure is configured using an Aruba controller and APs. Configure a controller with Meridian configuration values and it will propagate that configuration to all connected APs.

The controller should have DNS configured and able to reach *.meridianapps.com.

Generate an Access Token for Communicating to the Meridian Server.

To get started, create your access token in the Meridian Editor.

In the sidebar menu click Beacons, then select, "Beacons Management" from the top navigation menu, and then click Generate a New Access Token to get started.

You'll need to copy your Access token and use in a later step to configure your infrastructure.

Turning on your AP Beacons

This can be done via CLI as well, which if preferred, is referenced below.

In the Controller's web UI, go to the Configuration tab.

In the sidebar navigation menu, click System.

In the top navigation menu, select Profiles.

Under All Profiles, select AP.

In the AP System pane, indicate the system profile used by your APs.

Open the Advanced setting pane.

In the BLE operation mode field, enter beaconing.

Configure Beacon Management IoT Transport Profile (Config below)

Adding DigiCert Root Certificate to the Aruba Controller

The websocket endpoint uses wss protocol (secure websockets) and the server certificate is validated by the websocket library. When using a Meridian endpoint (with the *.meridianapps.com domain), the server is signed by a DigiCert root certificate, that requires the user to add the root CA certificate to the controller.

Uploading the certificate to the controller can be done under the Configuration > Management > Certificates menu.

Select PEM as the certificate format and Trusted CA as the certificate type.

Meridian Asset Tracking was previously using a GeoTrust Root Certificate for SSL signing. If you had previously installed this cert, you can safely delete it from the WebGUI, or from CLI using the following statements;