What configuration is needed on Aruba Controller to monitor BLE beacons using Meridian cloud?
Meridian solution from Aruba, make use of beacons for location and push notifications. The major administrative challenge with this solution is manage and monitor these beacons which are usually in 10's and 100's, depending on the kind of deployment. Aruba wireless backbone can turn this overhead into ease and help monitoring them with very minimal configuration.
Not every Aruba AP is designed or programmed to support this functionality. AP-225/224 or AP-215/214 come up with USB port, which enables them with this capability, when USB beacon is plugged in. Adding to that, AP-325/324 come with built-in hardware from factory that helps them to listen to beacons.
Access Points listen to deployed beacons and the controller can then relay the data about the beacons to beacon management console sitting in the meridian cloud. For this communication to go through, a basic configuration need to be enabled on Mobility Controller.
Beacons Management Prerequisites:
Below parameters needed to be configured in the ap system profile on mobility controller:
- BLE Endpoint URL
- BLE Auth Token
- BLE Operation Mode
BLE Endpoint URL: This URL points out controller to meridian cloud and helps to resolve the endpoint to form a secure tunnel. This URL is as would be :
BLE Auth Token: This is unique identifier per meridian account and differentiates between customers. This token can be obtained from beacon settings page of meridian account as shown below:
BLE Operation Mode: This enables the Controller to report Beacons status to the Meridian Editor. This is set to "Disabled" by default. Set to "Beaconing".
Below image shows the configuration on aruba mobility controller: