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

Information Needed for Meridian Editor Aruba Network Configuration

Use this guide to configure Aruba controllers with AOS 6.5.2.x/6.5.3.x or 6.5.4.x for use with Meridian Beacon Management and Asset Tracking.


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

Complete These Steps

Complete these steps to enable the Meridian Asset Tracking solution.

  1. Turn on the embedded Bluetooth in your APs and configure your infrastructure for Beacons Management.
  2. Install the DigiCert root certificate on all local controllers.
  3. Configure the Web Secure Socket between your controller and the Meridian back-end servers. 
  4. Deploy your Aruba Access Points using the Beacons app.
  5. 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.

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
Location ID{Location ID}

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 URLs ---
BLE Asset Tag Ingestion Endpoint URL for **6.5.2.x/6.5.3.x** wss://
BLE Asset Tag Ingestion Endpoint URL for **6.5.4.x+**
EU Tag Ingestion URLs ---
EU BLE Asset Tag Ingestion Endpoint URL for **6.5.2.x/6.5.3.x** wss://
EU BLE Asset Tag Ingestion Endpoint URL for **6.5.4.x+**

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.

Find Your Location ID

If you need to find your Meridian Editor location ID, the following image shows where to find that.

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 *

Aruba Controller Configuration

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 AP Configuration.
  3. Expand the AP settings, and then click AP system. This opens the AP system profile pane.
  4. In the AP system profile pane, click the Advanced tab to input the BLE configuration information you got from the Meridian Editor.

  5. Set BLE Operational Mode to Beaconing.

Configuring for Asset Tracking

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 * 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 an AP System-Profile Using the Aruba Controller CLI

    #configure terminal
    (config) #ap system-profile <profile-name>
    (AP system profile "System-Profile-Name") #ble-url <ble-url>
    (AP system profile "System-Profile-Name") #ble-token <ble-token>
    (AP system profile "System-Profile-Name") #ble-op-mode Beaconing
    (AP system profile "System-Profile-Name") #end
    #write memory

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

for AOS 6.5.2.x and 6.5.3.x

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

or for EU-hosted instances

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

for AOS 6.5.4.x 

#configure terminal (config)
#ble_relay mgmt-server type https <ingestion URL> token <token ID> id <location ID>

Where: Ingestion URL = Global or EU Tag Ingestion Endpoint URL (shown above)

Token ID = The Meridian Editor Beacons Management token. 

Location ID = Found in the Meridian Editor URL string or under the “Locations” tab in the Meridian Editor. At this time, Configuration of WSS is not available through the Aruba Controller Web-UI.

In order for the WSS to open, as shown in the  Validate your BLE Infrastructure section below, you must successfully deploy an Aruba AP and configure an Asset Tag using the Tags app.

At least one deployed Asset Tag will need to be in range of a configured observer in order for the Asset Tag signal to trigger the establishment of a WebSocket connection.