IP Maestro
ネットワーク オーケストレーション

IP Maestro is IP Infusion's GUI orchestration layer for fleets of OcNOS devices, giving operators a single pane for topology, configuration, telemetry, and software lifecycle without per-device CLI sessions. It manages both OcNOS-SP and OcNOS-DC variants from the same UI and complements rather than replaces existing automation such as Ansible, NETCONF/YANG, or gNMI. The platform is aimed at operators who want a visual, role-based front end on top of the disaggregated OcNOS stack.

IP Maestro builds an interactive network map that shows every managed OcNOS node, link, operational state, and active alert in one view. Operators can click into a node to drill down to interface statistics, BGP peer state, and the running configuration without opening an SSH session. Discovery relies on standard link-layer signalling and the device inventory IP Maestro maintains as new hardware is onboarded through ZTP.

When a new switch powers on, IP Maestro detects the device, matches it against an intent-based configuration template, and pushes both the OcNOS image and the desired config without manual SSH or CLI steps. Templates are version-controlled, so the same profile can be applied to a single lab box or a full leaf-spine pod. This is the same ZTP workflow used for fleet-wide rebuilds and refreshes, not just first-day provisioning.

Yes. IP Maestro ingests gNMI/gRPC streams from OcNOS devices using OpenConfig data models and renders sub-second dashboards for interface counters, BGP sessions, MPLS labels, and PFC counters. Threshold-based alerts can be routed to Slack, PagerDuty, or email with a full audit trail. Operators who already run Prometheus and Grafana can continue to consume the same telemetry stream alongside IP Maestro's built-in dashboards.

Configuration changes are stored as version-controlled, intent-based profiles, so an operator can roll a device or a group back to a known-good revision from the UI. For software, IP Maestro schedules fleet-wide OcNOS upgrades within defined maintenance windows and automatically rolls a node back if a post-upgrade health check fails. This avoids the per-device SSH choreography that fleet upgrades usually require.

IP Maestro is designed to sit in an automation pipeline rather than replace it. It speaks NETCONF (RFC 6241), RESTCONF, and gNMI to managed OcNOS devices and can be driven from existing toolchains such as Ansible or SaltStack through OpenConfig-modelled APIs. That lets teams keep their source-of-truth and CI/CD in place while using IP Maestro for visualisation, ZTP, and day-2 telemetry.

Yes. IP Infusion offers a downloadable IP Maestro demo VM and a live-demo booking option from the product page, so operators can evaluate the GUI against a lab OcNOS topology before any commercial discussion. The demo VM is intended for functional evaluation rather than production scale, giving teams a hands-on path to assess fit before procurement and sizing conversations.