Controllers and Beacons Management

Beacons Management Prerequisites:

* 7xxx Aruba Controllers
* Aruba OS 6.4.3.3 or higher
* USB Beacons plugged into an AP 215/225 or AP 315/325
    * AP 215 requires AOS 6.4.4+ for USB Beacons Management.

    **or**

* Aruba Sensor

If you're using an Aruba Controller to manage your wireless network, you can configure it to report to the Meridian Editor. Configuring a controller will let you use the Editor's Remote Beacon Management feature to manage your Beacons.

Please note that if you're deploying Beacons hardware to your location, you'll need the Aruba Beacons app. This includes USB Beacons plugged into APs and Aruba Sensors.

Controller Login

To configure your Aruba Controller to work with the Meridian Editor and Aruba Beacons, you'll SSH into the Controller with a command line interface (CLI).

  1. Open a terminal.
  2. Type: ssh admin@[Controller IP]
  3. Enter your admin password. If you don't know what it is, contact your network administrator.
  4. Type: enable. This enables Privileged commands.

Configure a Controller for Beacons

  1. Type: configure terminal Enter configuration mode.
  2. Type: ap system-profile default Use the default AP system profile.
  3. Type: ble-token [Meridian Editor token] The Meridian Editor token authenticates the Controller.
  4. Type: ble-url https://edit.meridianapps.com/api/beacons/manage The URL for the Meridian Editor's Beacons management endpoint.
  5. Type: ble-op-mode Beaconing This enables the Controller to report Beacons status to the Meridian Editor. Set to Disabled by default.
  6. Type: write memory Save these configuration settings.

Your Meridian Editor token is located on the Beacons Management Settings page. To the left of the List and Map buttons, click the Settings gear button. If you see Enable Beacons Management, click it. Otherwise, you'll find the token under Controller Configuration, next to ACCESS TOKEN.

Controllers communicate with the Meridian Editor over HTTPS on port 443. If you're using a firewall, please make sure communication over this port is enabled.

You can also configure these settings in the Controller web interface.

Show BLE devices

Use the following commands to list all of the Access Points reporting to the Controller and list all of the Beacons reporting to a specific Access Point.

  1. show ap active This shows all of the Access Points reporting to the Controller.
  2. show ap debug ble-table ip-addr [IP address] This shows a table of all of the Beacons reporting to the Access Point at that IP address.

AP Beacon Table Breakdown

The table has the following columns:

  • MAC: The Beacon's MAC address.
  • HW_Type: The Beacon's hardware type.
    • LS-BT1: A battery-powered Beacon.
    • LS-BT1USB: A USB Beacon.
    • HAWTHORNE: An Aruba Sensor (AS-100)
    • UNKNOWN: The controller is unable to determine the Beacon's hardware.
  • FW_Ver: The Beacon's firmware version. A Beacon needs a minimum firmware version 1.1-25.
  • Flags: In most situations, you won't need to worry about the flag column.
  • Status: Status will show whether a Beacon is undergoing a firmware upgrade, among other things.
    • L: An AP's Beacon, such as a USB Beacon plugged into an AP or the Beacon in an Aruba Sensor.
    • I: A Beacon matching Apple's iBeacon specification. True for all Aruba Beacons.
    • A: An Aruba Beacon. True for all Aruba Beacons.
    • H: An Aruba HiPower Beacon. Periodically, Beacons send a high power signal to make sure they're heard. This status is added if the AP has heard this high powered signal from a Beacon.
  • Batt (%): For battery-powered Beacons, the Beacons remaining battery percentage.
  • RSSI: The Beacon's received signal strength in dBm.
  • Major#: The Beacon's major value. Assigned by the Editor. Not editable.
  • Minor#: The Beacon's minor value. Assigned by the Editor. Not editable.
  • UUID: The Beacon's unique identifier. Assigned by the Editor. Not editable.
  • Tx_Po: The Beacon's power level setting. Location Beacon's have a power level of 14. Proximity Beacon's have configured power levels from 0-15.
  • Last Update: The amount of time since the Access Point has heard from the Beacon.
  • Uptime: The amount of time the Beacon has been on.

Controller Web Interface

You can access your Controller through a web interface by entering your Controller's IP address into a web browser: https://[Controller IP]. If you don't know the Controller's IP, contact your network administrator.

Login with admin and your admin password. If you don't know the password, contact your network administrator.

Configure a Controller for Beacons using the Web Interface

In addition to configuring a Controller using SSH, you can also use the Controller's web interface to configure it for use with Beacons.

Once you're logged into the Controller's web interface, complete these steps to enable your Controller for Beacons Management.

  1. In the top navigation bar, click Configuration.
  2. In the sidebar under WIRELESS, click AP Configuration.
  3. In the AP Group tab, click the name of the AP group you'll be using to manage your Beacons.
  4. Under Profiles, click AP to expand it.
  5. Click AP System.
  6. Under AP system profile, click the Advanced tab.
  7. Scroll down to the bottom of the Advanced settings.
  8. In the BLE Endpoint URL field, enter https://edit.meridianapps.com/api/beacons/manage.
  9. In the BLE Auth Token field, enter your Meridian Editor token. This authenticates the Controller to communicate with the Editor.
  10. Click the BLE Operation Mode dropdown, and then click Beaconing.

Your Meridian Editor token is located on the Beacons Management Settings page. To the left of the List and Map buttons, click the Settings gear button. If you see Enable Beacons Management, click it. Otherwise, you'll find the token under Controller Configuration, next to ACCESS TOKEN.

IAP Web Interface

You can use Beacons Management with Instant Access Points.

You can access your IAPs through a web interface by entering your IAP's IP address into a web browser: https://[IAP IP]. If you don't know the IAP's IP, contact your network administrator.

Login with admin and your admin password. If you don't know the password, contact your network administrator.

Configure an IAP for Beacons using the Web Interface

Once you're logged into the IAP's web interface, complete these steps to enable your IAP for Beacons Management.

  1. Go to Services > RTLS.
  2. Check the box next to Manage BLE beacons.
  3. In the Authorization token field, enter your Meridian Editor token. This authenticates the IAP to communicate with the Editor.
  4. In the Endpoint URL field, enter this URL: https://edit.meridianapps.com/api/beacons/manage.
  5. For BLE Operation Mode, choose Beaconing.

Update Controller Firmware

Periodically, you'll need to update your Aruba Controller's firmware. Follow these steps to update your Aruba Controller.

Meridian

To get the latest firmware, go to ftp://whirlpool.arubanetworks.com and search for ArubaOS_72xx.

  1. To get the latest firmware, go to https://support.arubanetworks.com, login with your Aruba account, and then click the Download Software tab.
  2. In the Navigator column, click ArubaOS, and then download your chosen version.
  3. In a web browser, go to https://[Controller IP]. If you don't know your Controller's IP, contact your network administrator.
  4. Log in with admin and your admin password. If you don't know your password, contact your network administrator.
  5. In the top menu bar, click the Maintenance tab.
  6. In the left sidebar, click Image management.
  7. Under Master Configuration, choose the following settings:
    1. For Upgrade using, choose the local file option.
    2. For Partition to Upgrade, choose Partition 1.
    3. For Reboot Controller After Upgrade, choose Yes.
    4. For Save Current Configuration Before Reboot, choose Yes.
    5. Click Upgrade.
  8. The update process takes about 10-15 minutes. During the update process, the Controller will turn off, and the AP will blink its power light.