Home/Products/IP Maestro
IP Maestro 3.1  ·  GA  ·  EMS for OcNOS

Run your whole OcNOS network
from one screen

IP Maestro is a GUI-based Element Management System (EMS) for OcNOS. See the state of each managed device, work alarms from one list, and push configuration or software to many devices at once, without per-device CLI sessions.

Try the Demo VM Request a Demo
250 devices per instance Single server or VM OcNOS 6.3.4+
IP Maestro › Network 250 devices
250 devices 98% links up 3 alarms
Spine-01 OcNOSUp · CPU 22%
Spine-02 OcNOSUp · CPU 31%
Leaf-01 OcNOSUp
Leaf-02 OcNOSUp
Leaf-03 OcNOSLink down · 1 alarm
Leaf-04 OcNOSUp

Illustrative interface

From the command line to one console

Managing OcNOS device by device means a mix of SSH sessions, SNMP tools, and scripts you maintain yourself. IP Maestro replaces that with one GUI built for OcNOS.

The challenge
With IP Maestro

Faults found too late

Without a live view, an alarm on one device often surfaces only when a customer notices. Finding it means SSH and guesswork.

See faults as devices report them

Alarms appear on the topology map and in one alarm list, so the NOC can act without logging in to each device.

Changes, one box at a time

Rolling the same config or a new image across a fleet means repeating per-device CLI steps, in a maintenance window, by hand.

Change the whole fleet in one move

Push configuration or a software image to one device or many from one screen, and schedule configuration pushes for a maintenance window.

No single source of truth

Topology, inventory, alarms, and logs live in different terminals and spreadsheets, so nobody has the whole picture in one place.

One source of truth

Topology, inventory, faults, and logs in a single console, with no per-device CLI.

Day-to-day OcNOS operations, from one screen

IP Maestro › Dashboard
IP Maestro dashboard: device summary, CPU, memory, and interface traffic
01 See

See your whole network at a glance

Open IP Maestro and the state of every OcNOS device is in front of you. No hunting across terminals, no stale spreadsheet.

  • Live topology map with link health by color and alarms shown on the map.
  • Inventory and device details with CPU, memory, transceivers, and administrative status.
  • Dashboards and streaming telemetry with customizable metrics and graphs. Streaming telemetry needs OcNOS 6.6.0 or later.
  • Third-party devices on the map linked to your OcNOS devices, so the topology shows the physical network.New in 3.1
IP Maestro › Alarms
IP Maestro fault management: active alarms with severity and acknowledgement
02 Detect

Know when something breaks

Alarms come to you as devices report them, so the NOC works from one alarm list instead of searching device by device.

  • Fault management from NETCONF notifications, with severity cues and alarm acknowledgement.
  • Email notifications on alarm, with the triggering severity configurable per user.
  • Searchable log repository consolidated across every managed device.
  • Performance monitoring with per-device counters and trend graphs.
IP Maestro › Config diff
IP Maestro configuration compare: a side-by-side config diff
03 Change

Change hundreds of devices in one move

Make a change once and roll it to one device or the whole fleet, on your schedule, with a diff to prove what changed.

  • Text config push to OcNOS in CLI or JSON, based on NETCONF data models.
  • Scheduled and mass provisioning for maintenance windows.New in 3.1
  • Backup and config diff with scheduled periodic backups.
  • Software image updates pushed to one device or many from the GUI.
IP Maestro › Device terminal
IP Maestro device terminal: an SSH session to an OcNOS device
04 Integrate

Secure it, and fit it into your stack

Built to fit how you already operate: your authentication, your tooling, and your language.

  • Role-based access (RBAC) with LDAP admin, operator, and user profiles, with audit logs.
  • Northbound REST API so an NMS or OSS can drive OcNOS through IP Maestro.
  • Device terminal access with SSH to OcNOS straight from the UI.
  • Internationalized UI including Japanese, plus remote system backup.
See the full feature list in the documentation →

One management node, your whole OcNOS fleet

A single IP Maestro instance manages and monitors many OcNOS devices over NETCONF. The devices can be laid out in any topology, including a leaf/spine (Clos) fabric. IP Maestro itself runs on one server or VM, not a cluster.

IP Maestro EMS architecture: an optional northbound NMS or OSS connects over REST to a single IP Maestro instance, which manages OcNOS spine and leaf devices over NETCONF.
A single IP Maestro EMS instance manages OcNOS spine and leaf devices over NETCONF, with an optional northbound NMS or OSS over REST.

Southbound: NETCONF

IP Maestro talks to OcNOS devices over NETCONF, carrying configuration and the fault notifications that drive alarms.

Northbound: REST API

A REST API lets a higher-level controller or OSS integrate with IP Maestro, including config push through to the devices.

One instance, one host

Runs as Docker Compose micro-services on a single Ubuntu server or KVM VM. No cluster required.

EMS, not NMS. IP Maestro manages network elements directly. When you already run an NMS or OSS, it sits beneath them through the northbound REST API.

Gallatin Wireless Internet, operating as Celerity Internet and Wispwest, adopted OcNOS and IP Maestro to monitor and manage their network across South Dakota, Wyoming, and Montana. IP Maestro is built by IP Infusion, the team behind OcNOS.

Read the Celerity story →

One VM, up to 250 devices

IP Maestro runs as a set of Docker Compose micro-services on a single Ubuntu host or KVM virtual machine. No cluster required.

250
Managed OcNOS devices per instance, validated in IPMA 3.1
1
Server or VM, no cluster
6.3.4+
Supported OcNOS releases
Operating system
Ubuntu or Red Hat Enterprise Linux
Hypervisor (VM)
KVM virtual machine
Container runtime
Docker Compose
Server sizing (250 devices)
8 vCPU · 32 GB memory · 1 TB disk
Interfaces
NETCONF southbound · REST API northbound

Supported operating system and Docker versions are listed in the installation guide for each release.

Built for Service Providers Data Center Operators ISPs MSPs Enterprise

Take the full IP Maestro spec with you

The complete IP Maestro datasheet: capabilities, system recommendations, and server sizing. Opens as a PDF right after a short form.

Datasheet

IP Maestro 3.x Datasheet

Full specification for IP Maestro, the element management system for OcNOS: assurance and telemetry, NETCONF southbound / REST northbound interfaces, deployment sizing, and supported OcNOS releases.

Get the brief

See IP Maestro against your own lab

Download the free demo VM and evaluate IP Maestro on your own OcNOS topology. No commercial discussion required. Try the free IP Maestro demo VM.

1

Download the demo VM

Grab the free KVM image and quick-start guide.

2

Point it at your OcNOS lab

Bring up the demo topology and start managing devices.

3

Book a live walkthrough

Want a guided tour? Our team will walk you through it.

Try the Demo VM Request a Demo

An IP Maestro license sets how many devices each instance can manage. Contact us for licensing and sizing guidance.

IP Maestro: frequently asked questions

What is IP Maestro?
IP Maestro (IPMA) is IP Infusion's GUI-based Element Management System (EMS) for OcNOS. It manages and monitors your OcNOS devices from a single console: network topology, inventory, fault and performance monitoring, configuration, and software updates, without per-device CLI sessions. It is designed to simplify network management, improve visibility, strengthen security with role-based access, and integrate with other systems through an open API.
Is IP Maestro an EMS or an NMS?
IP Maestro is an Element Management System (EMS): it manages and monitors network elements (your OcNOS devices) directly. It is not a network management system (NMS) or orchestrator. IP Maestro can sit beneath an existing NMS or OSS through its northbound REST API, so a higher-level controller can drive OcNOS devices through IP Maestro while your operators use the IP Maestro GUI day to day.
Does IP Maestro run on a cluster or in the cloud?
No. A single IP Maestro instance runs as a set of Docker Compose micro-services on one Ubuntu server or KVM virtual machine, and from there it manages and monitors many OcNOS devices. The managed devices can be arranged in any topology, including a leaf/spine (Clos) fabric, but IP Maestro itself is a single management node, not a cluster or cloud service.
How does IP Maestro discover and visualize network topology?
IP Maestro discovers the network and renders a visual topology map showing each managed device and the physical connectivity between them. Link health is indicated with customizable colors, device alarms are surfaced directly on the map, and you can click any element to reach its details. Since IPMA 3.1, you can also add third-party, non-OcNOS devices to the map and link them to your OcNOS devices, so the topology reflects the physical network.
What protocols does IP Maestro use to talk to OcNOS?
Southbound, IP Maestro communicates with OcNOS devices over NETCONF, which carries configuration as well as the fault notifications that drive alarm handling. Northbound, IP Maestro exposes a REST API so a higher-level controller or OSS can integrate with it, including pushing configuration through IP Maestro to the managed devices.
How does IP Maestro handle configuration and software updates?
Configuration management is based on NETCONF data models. You can push text configuration in CLI or JSON form to one or many devices, schedule multi-device configuration pushes for maintenance windows, take scheduled configuration backups, and view a configuration diff to see what changed. For software, IP Maestro can download a new OcNOS image to one or more devices, so fleet-wide updates run from the GUI rather than per-device SSH.
How does IP Maestro handle faults, telemetry, and notifications?
IP Maestro performs fault management from the NETCONF notifications devices send: it captures alarms and traps, shows severity with visual cues, and lets operators acknowledge alarms. It also visualizes performance counters and, on devices running OcNOS 6.6.0 or later, streaming telemetry, maintains a consolidated, searchable log repository, and can send email notifications when alarms are detected, with the triggering severity configurable per user.
How is IP Maestro deployed, and how many devices does it support?
IP Maestro deploys on a Linux server (Ubuntu or Red Hat Enterprise Linux) or a KVM virtual machine, running as Docker Compose micro-services. The installation guide for each release lists the supported operating system and Docker versions. In IPMA 3.1, a single instance is validated to manage 250 OcNOS devices on a server sized at 8 vCPUs, 32 GB of memory, and 1 TB of disk. IP Maestro is supported with OcNOS 6.3.4 and beyond.
Is there a free IP Maestro demo VM?
Yes. IP Infusion offers a downloadable IP Maestro demo VM, plus a live-demo booking option, so you 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.