Meridian Deployment Prerequisites Follow

There are many different ways to configure an HPE Aruba network for use with Meridian. Use this document to identify your HPE Aruba network configuration’s prerequisites and follow the links to more detailed configuration steps.

This article presumes that you are using HPE Aruba BLE Beacons hardware in your deployment.

Prerequisites for All Configurations

The following are the prerequisites for a Meridian Beacon deployment.

• A Meridian Editor account.
• HPE Aruba Beacons (Battery, USB, or Access Point Beacons).
• Meridian Manager app.

Network Ports

While uncommon, if your network restricts outbound traffic, the following network ports must be allowed to enable connections to the Meridian services:

• 80/TCP (HTTP).  This port is used for internet traffic.
• 443/TCP (HTTPS).  This port is used for encrypted internet traffic.
• 50051/TCP (gRPC).  This port is used for Meridian streaming API traffic and also for visualizing tag location on Meridian map for Meridian Manager app

Remote Beacons Management Prerequisites

The following are the prerequisites for enabling the Meridian Editor’s Remote Beacons Management feature. Versions represent minimum needed.

Go here for information on how to enable Beacons Management in the Meridian Editor.

Asset Tracking Prerequisites

The following are the prerequisites for using BLE Tags for asset tracking.

• BLE Tags.
• Meridian Manager app.
• HPE Aruba NetworkingAccess Points (APs).
• HPE Aruba Networking controller / Any HPE Aruba Networking AP Management platform.

Go here for information on how to deploy BLE Tags with the Meridian Manager app.

Go here for information on how to configure a HPE Aruba Network for asset tracking.

Go here for information on how to manage BLE Tags in the Meridian Editor.

Detailed Prerequisite Information

These versions are derived from Aruba's End of Life dates