Network integration
Aruba Central (HPE)
Read-onlyHPE Aruba Networking Central sites and devices on every customer's account hub. OAuth with auto-refresh keeps the connection alive without operator babysitting.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives. Every row below is a method this connector exposes today.
| Capability | Synced |
|---|---|
| Sites discovered from the regional API Gateway | |
| Devices per site — gateways, switches, access points — with model, serial, status, and firmware | |
| Site-to-customer mappings drive everything that reaches the customer hub or portal |
Read-only today
This adapter pulls data into Vectis but doesn't write back into Aruba Central (HPE). Rules can still react to the synced data — for example, a Pax8 subscription change can open a ConnectWise ticket. The write-back lands in the PSA, not in Aruba Central (HPE).
Aruba Central (HPE) is one of the read-only systems Vectis correlates against — synced data lands on the customer hub, drives rules, and shows up on the timeline; the vendor’s lifecycle stays inside its own console.
How it correlates
One customer, every tool.
Vectis is about Aruba Central (HPE) joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
Network device drift next to the PSA ticket history
An Aruba site that suddenly reports stale device check-ins lands in the same timeline as the customer's ticket activity, so the operator sees the network event and the user-reported impact in one place.
Vendor-agnostic network rules
Aruba devices land in the same network_devices table as UniFi and Meraki, source-tagged by vendor. A rule that fires on "any access point offline > 30 minutes" works across every Network adapter without per-vendor branching.
Setup snapshot
What connecting looks like.
Mint an OAuth app in Aruba Central → API Gateway → System Apps & Tokens; capture the client id, client secret, current access token, and refresh token. Paste the four values plus your regional gateway URL into Vectis admin → Integrations → Aruba Central. The first sync auto-discovers every site the OAuth app can see; map each site to a Vectis customer in the admin screen. Only mapped sites surface to customer pages. Vectis refreshes the 2-hour access token automatically via the refresh token — no operator action needed unless the OAuth app itself is rotated. The API surface is read-only here.
Full setup guideavailable after signup
Try Vectis with Aruba Central (HPE).
14-day free trial. Connect Aruba Central (HPE) at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.