This article describes the setup and configurations required for supporting Meridian Beacons Management and Asset Tracking on the Aruba Controller using ArubaOS 8.6.0.x.
Table 1: Contact Support
|Airheads Social Forum and Knowledge Base||community.arubanetworks.com|
This article assumes that the user has access to an active Aruba Meridian Editor account and the required components are enabled for beacons management and/or asset tracking.
The following Meridian assets are required to complete the configurations necessary on the Aruba Controller for either Beacons Management or Asset Tracking.
The Location ID can be found in the Meridian Editor URL. The syntax for the Meridian Editor URL will look like this:
An alternate place where the Location ID can be found is in the Settings tab on the left-hand navigation pane.
The Access Token is used by the controller to securely communicate with Meridian Servers. Initially, the Access Token must be generated in the Beacon Management menu. After it has been generated, there is no need to regenerate a new access token unless that is absolutely necessary. The same Access Token can be used for both Beacons Management and Asset Tracking.
If the access token has not been generated, follow these steps to generate a new access token:
- In the sidebar menu click Beacons, then select Beacons Management from the top navigation menu
- Click Generate a New Access Token to get started.
The new Access Token will be displayed in the ACCESS TOKEN window. To the right of the window is a copy button that can be used to copy on to your clipboard.
Aruba Meridian has an EU Server for the European Union and Standard Server for the rest of the world. To find out which server your account is set up in, look at the webpage URL after you log in to your account.
Table 2. Meridian Servers
It is important that you know which instance of Meridian Server your Meridian Editor account is set up in so that you can pick the correct Meridian Server URL when configuring IoT transport profile.
Table 3. Beacons Management Server URL
Table 4. Asset Tracking Server URL
The Aruba Wi-Fi network infrastructure is configured using an Aruba controller and APs. When you configure a controller with Meridian configuration values and it will propagate that configuration to all connected APs.
To minimize problems, verify that all the nodes are synchronized with the same reference server and time.
For best performance, the controller should have DNS configured and be able to reach .meridianapps.com server.
The AP Beacons (APB) must be enabled so that it can be provisioned for use with Meridian. If the APB is not enabled, the APB will not be broadcasting the beacon ID, therefore Meridian tools will not be able to configure the beacon. Enabling the APB can be done using the Controller GUI or the CLI.
- In the Controller's web UI, navigate to the Configuration > System > Profiles.
- Under All Profiles, select AP.
- In the AP System pane, indicate the system profile used by your APs (i.e. AP > default)
- Open the Advanced setting pane.
- In the BLE Operation Mode field, select Beaconing from the list of options.
(config) #ap system-profile <ap system profile-name>
(config) #ble-op-mode Beaconing
Aruba Controller Configurations for Beacons Management
This section covers the additional controller configuration required for Meridian Beacons Management.
An IoT transport profile is a global profile that is used to transport BLE information to an endpoint server. The IoT transportProfile is the command that is used to create or modify an IoT transport profile for Beacons Management.
At this time, creating the IoT transportProfile for Beacons Management is not available through the Aruba Controller Web-UI. You will need to use a Command Line Interface (CLI) script to create the profiles.
Below is the CLI script for creating the IoT transportProfile for Beacons Management:
(config) #transportProfile <beacons-management-profile-name>
(config) #serverType Meridian-Beacon-Management
(config) #serverURL <Select Standard or EU URL from Table 3>
(config) #accessToken <Meridian Access Token>
(config) #reportingInterval 600
(config) #include-ap-group <select the Beacons Management AP group>
#iot useTransportProfile <beacons-management-profile-name>
Table 5. Parameters for Beacons Management
After you log into your Meridian Editor account, in the left-hand pane, click on Beacons, and then on the top menu pane, click on Beacons Management. In the first section directly below the menu pane, the status will indicate whether or not your network has reported Beacons information to Meridian server.
If Meridian Server has NOT received beacons information, the following message will be displayed:
If Meridian Server has received beacons information, the following message will be displayed:
This sections covers the additional controller configurations required for Meridian Asset Tracking.
The websocket endpoint uses a wss (secure websocket) 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.
The root CA certificate for Meridian is available at:
To import the Certificate to the controller,
- Navigate to Configuration > System > Certificates menu.
- Select PEM as the Certificate format
- Select TrustedCA as the Certificate type.
- Enter a Certificate name
- Browse for and select the appropriate .crt file.
Meridian Asset Tracking was previously using a GeoTrust Root Certificate for SSL signing. If you had previously installed this cert, you can safely remove it from the WebGUI, or from CLI using the following statements;
#show crypto-local pki TrustedCA (find the name of the GeoTrust Root Cert)
(config) #no crypto-local pki TrustedCA <GeoTrust cert name>
An IoT transport profile is a global profile that is used to transport BLE information to an endpoint server. The IoT transportProfile is the command that is used to create or modify an IoT transport profile for Asset Tracking.
At this time, creating the IoT transportProfile for Asset Tracking is not available through the Aruba Controller Web-UI. You will need to use a Command Line Interface (CLI) script to create the profiles.
Below is the CLI script for creating the IoT transportProfile for Asset Tracking:
(config) #iot transportProfile <asset-tracking-profile-name>
(config) #serverType Meridian-Asset-Tracking
(config) #serverURL < Select Standard or EU endpoint URL from Table 4.>
(config) #accessToken <Meridian Access Token>
(config) #clientId <Meridian Location ID>
(config) #reportingInterval 5
(config) #include-ap-group <select the AP groups you want to participate>
#iot useTransportProfile <asset-tracking-profile-name>
Table 6. Parameters for Asset Tracking
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 WebSocket connection.
To view the websocket connection status and the list of settings configured for the BLE tag reporting use the show ble_relay disp-attr all command:
Meridian Observers are APBs in the infrastructure that listens for and reports information about the battery-powered beacons or asset tags back to the respective Meridian servers. For an APB to operate as an observer, the:
- APB must be enabled
- APB must be configured as either a Location or Proximity beacon
- IoT transportProfiles are properly configured
- Battery powered beacons or asset tags are heard by at least one APB
For Beacons Management, when an observer hears an Aruba battery-powered beacon, it sends the AP sends the beacon ID, RSSI value and battery level to the Meridian Beacons server. This information is used to update Beacons Management in Meridian Editor.
For Asset Tracking, when an observer hears an Aruba Tag, it sends the tag id, RSSI value and other information to the Meridian Tags server. The Tags server uses the highest weighted average RSSI value of the Aruba Tag heard by up to three of observers to track the tag on the map.