Configure Beacon Management and Asset Tracking for AOS 8.2.x (Controller)

Use this guide to configure Aruba controllers and Access Point Beacons (APBs) with AOS 8.2.x for use with Meridian Beacon Management and Asset Tracking.

When an Aruba Tag is heard by an access point (AP), the AP sends the Tag's RSSI value to the Meridian Editor. The Editor uses the highest weighted average RSSI value of the Aruba Tag heard by three APs to track its location on a map. Asset tracking is a continual process for all Aruba Tags being tracked for a location.


  1. Ensure correct Clock/NTP services
  2. Configure preferred DNS to reach *

Complete These Steps

Complete these steps to enable Meridian Asset Tracking.

  1. Turn on the embedded Bluetooth in your APs and configure your infrastructure for Beacons Management.
  2. Install the DigiCert root certificate on your Managed Devices (MDs) also known as your local controller(s)
  3. Configure the Web Secure Socket between your controller and the Meridian back-end servers. This should be done on your MDs/local controllers.
  4. Deploy your Aruba Access Point Beacons (APB) using the Beacons app.
  5. Configure and Deploy 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.

Aruba Tags app

Information Needed for Meridian Editor Aruba Network Configuration

Before you begin, you'll need to gather or set the following information in order to properly configure your controller for asset tracking.

Controller or IAP Value

Beacons Management URLs ---

Global Beacons Management URL
EU Beacons Management URL
Access Token Access Token (available in Meridian Editor)
BLE Operation Mode Beaconing
Global Tag Ingestion URL ---
BLE Asset Tag Ingestion endpointURL wss://
EU Tag Ingestion URL ---
EU BLE Asset Tag Ingestion Endpoint URL for **6.5.2.x/6.5.3.x**

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  *

Generate an Access Token for Communicating to the Meridian Server.

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

  1. 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.
  2. You'll need to copy your Access token and use in a later step to configure your infrastructure.

Configuring Beacons Management

  1. In the controller web UI, go to the Configuration tab.
  2. In the sidebar navigation menu, click System.
  3. In the top navigation menu, select Profiles.
  4. Under All Profiles, select AP.
  5. In the AP System pane, indicate the system profile used by your APs.
  6. Open the Advanced setting pane.
  7. In the BLE Endpoint URL field, enter:
  8. In the BLE Auth Token field, enter the Beacons Management auth token value.
  9. In the BLE operation mode field, enter beaconing.

Configuring for Asset Tracking

Adding DigiCert Root Certificate to the Aruba Controller 

The websocket endpoint uses the  wss (secure websockets) protocol and the server certificate is validated by the websocket library. When using a Meridian endpoint (with the * 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.

The root CA certificate for Meridian is available at:

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;

#show crypto-local pki TrustedCA (find the name of the GeoTrust Root Cert)  

#configure terminal 
#no crypto-local pki TrustedCA <GeoTrust cert name>

Configure the Web-Secure Socket (WSS) in the Aruba Controller CLI

At this time, Configuration of WSS is only available using the controller CLI.

This configuration should be done on the local controller

#configure terminal

(config) #ble_relay mgmt-server type ws wss://

or for EU-hosted instances

(config) #ble_relay mgmt-server type ws wss://