Configure Beacon Management and Asset Tracking for AOS 8.3.x (Controller)
Use this guide to configure Aruba controllers with AOS 8.3.x for use with Meridian Beacon Management and Asset Tracking.
- 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
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 (available in Meridian Editor)|
BLE Operation Mode
Asset Tracking Ingestion URLs ---
Global Asset Tag Ingestion endpointURL
EU Asset Tag Ingestion endpointURL
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
You can find your Location ID by;
1. Navigating to your Meridian account (https://edit.meridianapps.com)
2. Select the appropriate Meridian location
3. Go to the Settingstab on the left-hand navigation pane
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.
- 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
- 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.
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 to Enable Access Point Beacons Using the Aruba Controller CLI
#configure terminal (config) #ap system-profile <profile-name> (AP system profile "System-Profile-Name") #ble-op-mode Beaconing (AP system profile "System-Profile-Name") #end #write memory
Configure Beacons Management and Asset Tracking IoT Transport Profiles in the Aruba Controller CLI
ArubaOS 8.3.x uses the ioT transportProfile methodology for configuration. Use the following commands;
Configuring Beacons Management
#configure terminal (config) #iot transportProfile <beacons management profile-name> (ioT Data Profile "profile-name) #endpointType Meridian-Beacon-Management (ioT Data Profile "profile-name) #endpointURL https://edit.meridianapps.com/api/beacons/manage (ioT Data Profile "profile-name) #endpointToken <meridian-token> (ioT Data Profile "profile-name) #payloadContent managed-beacons (ioT Data Profile "profile-name) #transportInterval 600 ! (config) #iot useTransportProfile <beacons-management-profile-name>
Configuring Asset Tracking
#configure terminal <br>(config) #iot transportProfile <asset-tracking-profile-name> <br>(ioT Data Profile "profile-name) #endpointType Meridian-Asset-Tracking <br>(ioT Data Profile "profile-name) #endpointURL <Select Global or EU endpointURL from above inventory> <br>(ioT Data Profile "profile-name) #endpointToken <meridian-token> <br>(ioT Data Profile "profile-name) #endpointID <locationID> <br>(ioT Data Profile "profile-name) #payloadContent managed-tags <br>(ioT Data Profile "profile-name) #transportInterval 5 <br>! <br>(config) #iot useTransportProfile <asset-tracking-profile-name>
locationID = Found in the Meridian Editor URL string or under the “Locations” tab in the Meridian Editor.
endpointToken = Found in the Meridian Editor Beacons Management Page
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.