Aruba Central Configuration Manual – ArubaOS 10.x

Introduction

This guide is specifically designed for the setup and configuration of Aruba Access Points (APs) managed in Aruba Central running ArubaOS 10.x or higher for integration with the Blyott platform.

Prerequisites

Before starting, make sure the following requirements are met:

• Aruba Central Access: Administrator role.

• ArubaOS Version Requirements:

  • External VM (Data Collectors): ArubaOS 10.4 or higher.

  • AP Connector (IoT Connector on APs): ArubaOS 10.5.latest or higher, supported on Aruba AP Series 500, 600, 700 and above.

• AP Groups: At least one existing AP Group in Aruba Central already running ArubaOS 10.x with APs assigned.

• Blyott Credentials: Tenant code and access token (request via helpdesk@blyott.com).

• Certificates: AWS Trusted Root CA certificate available for upload (Step 1).

• Firewall/Router Requirements:

  • TCP/UDP 123 → NTP server access (e.g. pool.ntp.org).

  • TCP 443 → HTTPS access to:

    • https://api.blyott.com

    • https://portal.blyott.com

    • https://firmware.blyott.com

    • or https://*.blyott.com

  • TCP 8883 → MQTT over TLS to:

    • tcp://aroncdz10y0su-ats.iot.eu-west-1.amazonaws.com:8883.

---

Step 1: Manage Certificates

Blyott connections require a trusted CA certificate from AWS. Without it, the AP will reject the secure connection.

Install AWS Root CA:

1. Download the AWS Root CA certificate in DER format from https://www.amazontrust.com/repository/

2. In Aruba Central, go to Organization → Certificates.

3. Click ➕ Add and fill in:

   • Name: Amazon Root CA 1

   • Type: CA Certificate

   • Format: DER

   • File: Select your downloaded certificate file.

4. Click Add to upload.

Assign the Certificate:

1. Go to Global → Network Structure → [Your Group] → Devices → Config → Security.
2. Under Certificate Usage, scroll to IoT CA.
3. Select the uploaded certificate.
4. Click Save Settings.

---

Step 2: Configure AP Connector (IoT Connector on AP)

The AP Connector runs the IoT Connector service directly on the AP. This is required for sending BLE advertisement data to the Blyott platform.

Minimum Requirements:

• ArubaOS 10.5.latest or higher.

• Supported hardware: Aruba AP Series 500, 600, 700 and above.

Steps:

1. In Applications → IoT Operations, click Add Connector.

2. Select Telemetry-WebSocket as the connection type.

3. Enter the Blyott connection details.

4. Save.

---

Step 3: Install the Blyott App

The Blyott application in Aruba Central allows APs to recognize and handle Blyott tag data.

1. In Aruba Central, navigate to the App Marketplace.

2. Find Blyott Devices.

3. Click Install.

---

Step 4: Configure Radio Profile (BLE Scan Mode)

The Aruba AP must have its internal BLE radio enabled to detect Blyott tags.

Steps:

1. In Devices → Config → IoT, go to the BLE Radio Profile settings.

2. Set Radio Mode = Internal, BLE.

3. Set BLE Operation Mode = Scanning.

4. Adjust Tx Power for site coverage.

5. Save.

---

Step 5: Create Transport Profile for Blyott

The Transport Profile links BLE scan data to the Blyott’s servers.

1. Navigate to: Applications → IoT Operations → Manage Transport Profiles → IoT Transport.

2. Click + Add Transport.

3. Fill in:

   • Name: Blyott

   • Stream Type: Data Frames

   • Subscription: Device Class = Blyott

   • Protocol: WSS

   • URL: wss://proxylocator.blyott.com/aruba10/{TENANTCODE}

   • Format: protobuf

   • Authentication: Token

   • Token: (Provided by Blyott)

4. Click Create and assign to your AP group.

Important: Replace {TENANTCODE} with your actual Blyott tenant code (case-sensitive).

---

Step 6: Add AP as Locator in Blyott Portal

You can also refer to our how to guide - How to add a locator

1. Log in to Blyott Portal.

2. Go to Locators → + New Locator.

3. Enter:

   • Locator Name

   • Hardware Model: Aruba | BLE-enabled

   • ID (MAC): Ethernet MAC (uppercase, no colons)

   • Fixed Location: Select predefined location

4. Save.

Note: Always use the Ethernet MAC, not the Bluetooth MAC.

---

Step 7: Post-Deployment Checks & Verification

After completing the configuration, perform the following checks to ensure your Aruba APs are correctly scanning BLE tags, classifying them as Blyott devices, and sending data to the Blyott cloud.

---

Quick Checklist

• BLE Scanning Enabled (AP Point of View): Confirm AP CLI shows tags with Company ID 09CD.

• IoT Device Table (Aruba Central GUI): Verify the Blyott app is running and tags are classified as “Blyott.”

• IoT Transport Connection: Confirm IoT profile state is Connection Established.

• Blyott Dashboard: Locators’ Last Seen ≤ 5 minutes.

• Certificates: AWS Root CA valid.

• After Firmware Updates: Reconfirm BLE scanning, IoT profiles, and filtering remain active.

Support Note: If any check fails, email helpdesk@blyott.com with CLI outputs and/or screenshots from the IoT Device Table for assistance.

---

Detailed Verification Steps

7.1. BLE Tag Detection (AP Point of View)

From the AP CLI, confirm BLE scanning is enabled and the AP is detecting tags:

• Verify tags are listed with Company ID 0x09CD.

• Confirm Last Update values are recent (a few seconds).

• If no tags appear:

  • Ensure BLE scanning is enabled (Step 4).

  • Confirm tags are powered on and in range.

  • Check Company ID filtering is applied correctly.

---

7.2. Verify IoT Device Table in Aruba Central GUI

Once you have confirmed BLE scanning at the AP level, the next step is to check that the Blyott application is running properly in Aruba Central:

1. Go to Applications → IoT Operations → Device Table.

2. Verify that entries appear for your tags.

3. Confirm they are properly classified as “Blyott.”

4. Multiple tags should be visible if several are in range.

---

7.3. Verify IoT Transport Connection

• Confirm Server Connection State: Connection Established.

• If not, run:

   

  show ap debug ble-relay ws-log <profile>


  and share results with Blyott support.

---

7.4. Verify Message Processing

• Incoming/Processed messages should increase steadily.

• Dropped messages should remain very low (<0.5%).

---

Common Errors

• Missing or incorrect CA certificate chain.

• Wrong token or authentication credentials.

• DNS resolution issues.

• Firewall blocking communication.

Note: In ArubaOS 10, IoT server connections are established even when no BLE devices are currently detected.

---

8. Additional Aruba Information

8.1 API Integration (AOS 10.x)

• Aruba provides a robust REST API for ArubaOS, supporting automation and third-party integrations.

  • ArubaOS 10.x API Developer Guide – available in the Aruba Developer Hub.

  • Aruba Developer Hub – https://developer.arubanetworks.com.

8.2 Aruba Support Portal

• Access the full range of user guides, firmware updates, technical articles, and support documentation via the Aruba Support Portal:

  • https://asp.arubanetworks.com

---

9. Blyott Support and Assistance