Welcome to the ARUBA configuration guide. Within this guide, we aim to provide you with useful information and guidance to make the connection to Blyott using ARUBA AP devices. Before we show you how to configure the Bloytt part, ARUBA has technical documentation for configuring IoT. Please see this link which can already give you some insight on the setup of the network. For generic purpose you can always point to this link for additional information on Aruba. This guide can be downloaded as a PDF on this LINK.
Additionally, you can find the official Aruba configuration manual on this LINK, for more information.
- Connect to the Mobility Master.
- Select the hierarchy level where you want to setup Blyott integration.
- In the “Configuration” section, select “IoT”.
- From the “Transport streams” add a new profile “BlyottDemo” by clicking on “+”.
- “State” needs to be “Enabled.”
- “Server type” needs to be “Telemetry-Https”.
- Fill the “Server URL”, with the following: http://proxylocator.blyott.com/webhook/aruba
- “Device classes” needs to be selected “all”.
- “Reporting interval” needs to be “60” seconds.
- “RSSI reporting format” needs to be “average”.
- “Environment type” is up to your preferences.
Configure the profile as shown in the following snapshot.
In future release we should be able to filter based on device class “blyott” but as for now we have to send all devices data.
- In “Authentication” section, as is it mandatory, select “Use Token”.
- Fill “BlyoTT:2200!” in the “Access Token” field.
NOTE: Do not forget to select the AP group where to deploy the Transport Profile.
Now let us be sure that the embedded BLE in the APs are well configured to scan for BLE tags.
- Select “IoT radio profiles” tab.
- Click on “+” to add a new profile or edit a profile if you already use one.
- Check that “BLE” is selected in the “Radio mode”.
- Check that “Both” is selected in the “BLE operational mode”.
- For Tx Power, in this test setup we use -12dBM but this value can be adjusted depending on your setup / coverage and needs.
IMPORTANT NOTE: The Radio Profile must be selected in the “AP group configuration”.
- Select the “AP group” where you want to use the Radio Profile, then select the “IoT” tab and in the “IoT internal Radio Profile", be sure that the profile you just created / modified is selected.
From AOS 8.8, there is now an “IoT” dashboard in the Web UI.
There you can see the IoT devices seen by the APs, and that messages are sent through your Transport Profile (you must be on top of the hierarchy of Managed Network).
In previous releases, you can use the CLI to verify the APs see the tags.
- Connect to the Mobility Master.
- Go to the controller which managed the AP which should see the tags:
- Connect to the controller:
- Enter the following command:
show ap debug ble-table ap-name 50816 all
You should see an output as in the following snapshot (search for the Bluetooth Mac Address of your tags). In pre AOS 8.8 release you should not see “Blyott” in the device class column.
Before we start, I would recommend seeing our Onboarding Handbook for more details on Blyott Portal. We have also created a support portal containing information about the Blyott platform which you can access here. The support portal contains a knowledge base where you can find all relevant information about the platform including Blyott latest API documentation.
Clicking on “Locators” tab on the “List Views” panel, depending on your “Access Level”, you can see locators list with information like Locator Name, Location, Location Code, MAC, Type, Last Seen, Serial Number, IMSI, IMEI.
To add Locators, click on “+” (Add locator) button and fill the following data:
Enter desired locator name.
Enter “Ethernet” (not BLE) MAC address of the AP.
If “Type” is selected “WIFI”, you will need to create fixed locations in the “Location” tab before you can select the location. If you already have Locations, just select desired Location.
Select “Aruba | BLE-enabled”.
- Serial Number
Enter serial number of the device.
Enter IMEI number of the device.
*Make sure to enter the correct MAC ID. This can be confirmed locally with your IT team and/or occasionally marked on the device. Enter the MAC address in capital letters and without the semicolons (:).
When working with ARUBA, the client should add per Wi-Fi AP the Ethernet MAC address (not the Bluetooth MAC address). It is the Ethernet MAC address of each AP that the Aruba WLAN controller sends to the Blyott cloud platform.
Update your Aruba firmware to the latest version
We highly recommend updating it to the latest firmware. It should be upgraded to a minimum of v8.7 to be working properly with Blyott implementation.
- Offical User Guide on ArubaOS can be found in this PDF file.
- Official Getting Started Guide on ArubaOS can be found in this PDF file.
- Official AP Software Quick Start Guide can be found in this PDF file.
- The full official API documentation can be found in this PDF file.
- Official FAQ documentation can be found in here.
Within this Help Center we aim to provide you with useful information, documentation and guidance that will enable you to make the most out of your access to the Blyott Platform. In the Knowledgebase section you can find video walkthrough guide for support page, Release Notes, Documentation, Manuals and “How to” guides. Keep up to date with the information & articles you are interested in, by selecting the 'Subscribe' option and you will receive email updates every time we add new information.
For everything else do not hesitate to contact us on email@example.com.
Thank you for attention.
The Blyott Support Team