# Show HN: Portable Aruba Central JSON snapshot using a vendor-neutral OSIRIS JSON

> Source: <https://docs.osirisjson.org/osiris-producers/network/hpe-aruba-networking-central/>
> Published: 2026-07-29 14:03:49+00:00

Aruba Networking Central

available cloud-native, AI-powered network management platform that unifies Wi-Fi, switching, and SD-WAN operations

Transport: REST API

The OSIRIS JSON HPE producer connects to HPE infrastructure platforms (in its first 0.1.0 release, Aruba Central is supported and others will come later) and generates OSIRIS JSON snapshots of your network topology, devices, interfaces, and connections.

Aruba Networking Central

available cloud-native, AI-powered network management platform that unifies Wi-Fi, switching, and SD-WAN operations

Transport: REST API

The Aruba Central producer supports two credential types:

`client_id`

and `client_secret`

plus an OAuth2 token pair (`access_token`

and `refresh_token`

), created via the Central UI or OAuth2 flow.`client_id`

and `client_secret`

pair (generated at `common.cloud.hpe.com/manage-account/api`

). No access/refresh token pair is needed upfront; the producer mints tokens automatically against the GreenLake SSO endpoint.By default, the producer runs interactively. It will auto-detect your cluster and list the sites available in your account, prompting you to select one or more. Each selected site generates its own separate OSIRIS JSON document.

The producer is designed to run without interactive login if needed.

This examples works as a perfect use-case for unattended execution (e.g., in a cron job or pipeline), you can specify one or multiple site or use the `--all`

flag, this discovers and exports every accessible site non-interactively. Each site’s resources is written to a dedicated OSIRIS JSON document in the output directory.

| Flag | Short | Description |
|---|---|---|
`--token-file` |
JSON file with `{client_id, client_secret}` . Mandatory for non-interactive auth. |
|
`--cluster` |
Cluster short code (e.g. `eucentral3` ). Auto-detects if omitted. |
|
`--base-url` |
Override the API Gateway base URL (takes precedence over `--cluster` ). |
|
`--site` |
Comma-separated site name(s) to collect (bypasses interactive site picker). | |
`--all` |
Auto-discover and export every accessible site, skipping prompts. | |
`--output` |
`-o` |
Output directory for files. Default is `osirisjson-hpe-arubacentral` in current dir. |
`--purpose` |
`documentation` (default) or `audit` (adds client fingerprints/health deep-dives). |
|
`--include-raw-body` |
Attaches full API responses to resources. Requires `--purpose audit` . |
|
`--safe-failure-mode` |
Secret handling: `fail-closed` (default), `log-and-redact` , `off` . |

The OSIRIS JSON producer for Aruba Networking Central extracts the following inventory and topology:

**Run in documentation mode (Default)**

| Resource / Element | Description |
|---|---|
`network.switch` |
Switches (includes stacking logic, hardware sensors, and VSX peerings) |
`network.gateway` |
Gateways (includes uplinks, ports, and VLANs) |
`network.interface` |
Interfaces and ports for the devices |
`network.vlan` |
VLANs spanning devices |
| APs & Radios | `osiris.hpe.arubacentral.accesspoint` , `.radio` , `.wlan` , `.bssid` and `.swarm` (mesh swarms) |
| Clients | `osiris.hpe.arubacentral.client` (unified wired/wireless clients) |
| Neighbors (Topology) | LLDP/CDP adjacencies mapping device-to-device connections (`network` connections) |
| Unmanaged devices | `osiris.hpe.arubacentral.device` (Stubs out 3rd-party edge devices found via CDP/LLDP) |
| Config Health & Sites | Maps Aruba’s config-health compliance and site-health to OSIRIS `status` fields |

**Run in audit mode adds**

| Element | Description |
|---|---|
| Client Fingerprints | Exact device host name, user name, OS, manufacturer, and authentication/security type |
| Deep Health telemetry | Breakdowns of AP/switch/gateway health and unmanaged-device MAC lookup resolution |
| Raw Payloads | (With `--include-raw-body` ) the true, unmodified API response under `extensions` |

By default, documents are saved in an `osirisjson-hpe-arubacentral`

folder, structured by site. Each additional snapshot will be saved into the same site folder.

Re-running the command adds new timestamped files alongside prior ones, creating a clean historical record for drift detection.

The Aruba Central producer emits the standard OSIRIS JSON envelope:

In this example we run a single site collection.

The following example have been intentionally trimmed replacing real values with documentation examples reserved by established IETF standards: