Modern infrastructure rarely belongs to a single vendor or platform. Campus and branch networks may run on HPE Aruba Networking, the data-center core on other vendors, and application solutions maybe run in an hybrid enviromnet across cloud or hyperscalers like AWS or Microsoft Azure.
Each environment has its own control plane and data model. The challenge appears when architects, engineering teams, and technology leaders need a consistent view across those boundaries, the challenge isn’t a lack of data it’s that the architectural truth is trapped behind paginated APIs and vendor-specific silos.
Today, we’re releasing the v0.1.0 OSIRIS JSON Producer for HPE Aruba Networking Central which is aimed to solve exactly this problem.
The producer reads infrastructure data directly from Aruba Central and converts it into a portable, vendor-neutral OSIRIS JSON document. The result is a deterministic, point-in-time snapshot that can be stored locally, compared over time, integrated with other tools, and combined with snapshots generated by other OSIRIS JSON producers.
What the producer captures
The new OSIRIS JSON producer is a standalone, read-only Go binary designed to represent both the inventory and the relationships that give an Aruba environment its architectural context. It maps the proprietary Aruba data model into the OSIRIS JSON vendor-neutral Specification.
It currently extracts and standardizes:
- Infrastructure inventory: switches, access points, gateways, and wired and wireless clients.
- Logical organization: switch stacks, VSX peers, link aggregation groups, VLANs, and IAP mesh swarms.
- Device adjacencies: LLDP and CDP neighbor relationships between managed devices.
- External boundaries: unmanaged or third-party devices discovered at the edge of the Aruba environment are retained as stub resources instead of being discarded.
- Operational context: configuration-health compliance and site-health rollups that can support comparison and drift-oriented analysis comparing different OSIRIS JSON documents.
- Two output purposes:
documentationfor a concise architectural representation, andauditfor deeper properties.
Preserving unmanaged neighbors is especially important in multi-vendor environments. It allows an Aruba topology to describe where the managed domain ends and where another network, provider, or OSIRIS JSON producer may continue the visualization.
Private and controlled by design
The producer can run locally or inside a controlled CI/CD workflow. It connects directly to Aruba Central and writes the resulting OSIRIS JSON snapshot under your control.
It does not require:
- SaaS or consultancies: You don’t send any of your data to us.
- AI platforms or agents: Your infrastructure data is already into Aruba Central, you don’t need AI platforms or agents to extract it, viceversa OSIRIS provide deterministic, auditable output which you can use in your AI or MCP workflow.
- Intermediary third-party APIs: OSIRIS direct connect from your environment to Aruba Central.
Authentication is supported through standard OAuth 2.0 API Gateway credentials and HPE GreenLake Personal API clients.
This model gives infrastructure teams a governed separation between the live control plane and the tools that consume its data. Documentation systems, CMDB/IPAM/DCIM workflows, visualization tools, and internal AI platforms or MCP servers can work from an organized OSIRIS snapshot rather than requiring direct access to Aruba Central.
From an Aruba Central view to a wider infrastructure view
An OSIRIS JSON document is not tied to a proprietary dashboard or database. It can be retained as evidence, validated, versioned, compared with an earlier state, transformed into diagrams, or passed into downstream automation.
The OSIRIS JSON for Aruba Central snapshot can also be used alongside OSIRIS JSON outputs from AWS, Microsoft Azure, and Cisco producers. This creates a common baseline for building broader views of infrastructure that would otherwise remain separated by vendor-specific APIs and terminology.
Potential uses cases include:
- architecture and operations documentation;
- Draw.io topology generation;
- point-in-time comparison and drift analysis;
- audit and compliance evidence;
- CMDB, IPAM, and DCIM enrichment;
- integration and data-transformation workflows; and
- precise, governed context for internal AI, agent, and MCP-based solutions.
Get started
read the quick start guide to start bringing your edge infrastructure into focus.
Run it against your environment, inspect the generated snapshot, and share your feedback.