Network automation for OcNOS routers and switches

IP Infusion delivers OcNOS routers and switches that you provision with zero touch provisioning, configure over NETCONF and YANG or with the Ansible collection, and monitor with gNMI streaming telemetry. Use IP Maestro when you want a GUI.

Book a demo Get the Ansible app note
26OcNOS-SP routers
18OcNOS-DC switches
900+operators in 60+ countries

From first power-on to daily operations

An OcNOS router or switch comes up through zero touch provisioning, takes its configuration over NETCONF or from the Ansible collection, and streams its state over gNMI. Each stage uses standard protocols and data models.

Pick a stage

A ZTP server, Ansible or IP Maestro, and a telemetry collector connect over the management VRF to two OcNOS routers and two OcNOS switches. Day 0 provisions a new switch, Day 1 pushes configuration to every device, Day 2 streams telemetry from every device to the collector ZTP serverDHCP and ZTP Ansible or IP MaestroNETCONF Telemetry collectorgNMI Management VRF Day 0: the new switch gets its address, software and startup configuration Day 1: configuration goes to every router and switch over NETCONF Day 2: every router and switch streams its state over gNMI RouterOcNOS-SP RouterOcNOS-SP SwitchOcNOS-DC New switchOcNOS-DC

Day 0: provision

A new router or switch gets its address from DHCP, then uses zero touch provisioning to load its software and startup configuration.

  • ZTP over IPv4 (RFC 8572), on all 26 OcNOS-SP routers and all 18 OcNOS-DC switches
  • ZTP over IPv6, on 16 OcNOS-SP routers and 15 OcNOS-DC switches
  • Install from the ONIE prompt, or upgrade from the OcNOS shell with sys-update, on every router and switch

Read the OcNOS documentation.

Illustrative. Check each router and switch in the OcNOS Feature Matrix.

Operators running OcNOS with their own tools

“IP Infusion’s OcNOS software, paired with Edgecore hardware, is now part of our production environment supporting middle-mile and data center transport. In these targeted use cases, the platform’s flexibility, support for open standards, and cost structure align well with our goals to expand broadband access throughout the Heartland while maintaining operational agility and performance.”

Cameron Kilton, Chief Technology Officer, Nextlink Internet

Nextlink Internet

NETCONF/YANG integration ties OcNOS into Nextlink’s network automation tools.

Read the story →

Celerity Internet and Wispwest

IP Maestro provides an interface for network monitoring and configuration that simplifies day-to-day operations and improves visibility across the network.

Read the story →

IzarLink

A redundant 100G core serving 25G access, with EVPN-VXLAN, BGP, OSPF, multi-homing, and streaming telemetry.

Read the story →

Automation interfaces by product line

Most automation interfaces run on all OcNOS-SP routers and OcNOS-DC switches. The table shows where support differs by model.

InterfaceOcNOS-SP routersOcNOS-DC switches
Ansible collection26 of 2618 of 18
NETCONF over SSH and TLS26 of 2618 of 18
YANG 1.0 and YANG 1.126 of 2618 of 18
OpenConfig and NETCONF Call Home26 of 2618 of 18
gNMI Subscribe (dial-in) and Publish (dial-out)26 of 2615 of 18
gNMI on-change streaming, from OcNOS 7.026 of 2615 of 18
gNMI in-band, single or multi VRF24 of 2615 of 18
Zero touch provisioning over IPv426 of 2618 of 18
Zero touch provisioning over IPv616 of 2615 of 18
Transaction-based CLI with commit rollback26 of 2618 of 18
SNMP v1, v2 and v3, sFlow and syslog26 of 2618 of 18

Counts from the OcNOS Feature Matrix. Check each router and switch in the OcNOS Feature Matrix.

On OcNOS-DC, streaming telemetry is part of the PLUS edition. On OcNOS-SP, NETCONF is in the IPBASE, MPLS and PLUS editions, and OpenConfig in MPLS and PLUS.

NETCONF and telemetry on the management VRF

From the running configuration of a UfiSpace S9600-28DX router on OcNOS-SP 7.0.2 in our lab.

feature netconf-ssh vrf management
feature netconf-tls vrf management
feature streaming-telemetry vrf management
telemetry maximum-subscribe-paths 50
  1. NETCONF over SSH, on the management VRF.
  2. NETCONF over TLS, on the management VRF.
  3. gNMI streaming telemetry, on the management VRF.
  4. Sets the maximum number of telemetry subscribe paths to 50.

IP Maestro when you want a GUI

IP Maestro is the element management system for OcNOS. It manages OcNOS devices over NETCONF and offers a northbound REST API, so an NMS or OSS can drive OcNOS through IP Maestro while your operators use its GUI.

Monitor

Topology discovery and visualization, dashboards and metrics, performance monitoring and fault management from NETCONF notifications.

Configure

Configuration push in CLI or JSON, scheduled and mass provisioning, scheduled backup with config diff, and software image updates.

Scale

In IPMA 3.1, one instance is validated to manage 250 OcNOS devices on 8 vCPUs, 32 GB of memory and 1 TB of disk, with OcNOS 6.3.4 and later.

See IP Maestro, the element management system for OcNOS.

Questions about network automation on OcNOS.

Yes. IP Infusion publishes the ipinfusion.ocnos collection on Ansible Galaxy. Its modules gather facts, push configuration, run commands, ping, and read BGP and IS-IS state. Its actions back up and restore configuration, update software and validate the device. The Feature Matrix lists Ansible for all 26 OcNOS-SP routers and all 18 OcNOS-DC switches.
Yes. OcNOS runs NETCONF over SSH and over TLS with YANG 1.0 and YANG 1.1 models, OpenConfig support, event and base notifications, the NETCONF monitoring module and NETCONF Call Home, on all 26 OcNOS-SP routers and all 18 OcNOS-DC switches. On OcNOS-SP, NETCONF is in the IPBASE, MPLS and PLUS editions, and OpenConfig in MPLS and PLUS.
OcNOS streams telemetry over gNMI. A collector subscribes to the router (dial-in), or the router publishes to the collector over IPv4 through grpctunnel (dial-out). Subscriptions run in once, poll or stream mode over TLS with OpenConfig data models, and on-change streaming and user authentication arrive in OcNOS 7.0. gNMI runs on all 26 OcNOS-SP routers and 15 of 18 OcNOS-DC switches; on OcNOS-DC it is part of the PLUS edition.
Yes. SNMP v1, v2 and v3, sFlow and syslog run on all 26 OcNOS-SP routers and all 18 OcNOS-DC switches, so your SNMP monitoring keeps working while you add a gNMI collector.
A new router or switch gets its address from DHCP, then loads its software and startup configuration through zero touch provisioning (RFC 8572). ZTP over IPv4 runs on all 26 OcNOS-SP routers and all 18 OcNOS-DC switches, and ZTP over IPv6 on 16 OcNOS-SP routers and 15 OcNOS-DC switches. Software can also be installed from the ONIE prompt.
IP Maestro is the element management system for OcNOS. It manages OcNOS devices over NETCONF and offers a northbound REST API, with topology, fault and performance views, configuration push and software image updates. In IPMA 3.1 one instance is validated to manage 250 OcNOS devices, with OcNOS 6.3.4 and later.
Yes. The OcNOS CLI applies changes as transactions on commit, and CLI commit rollback returns the device to an earlier committed configuration. Both run on all 26 OcNOS-SP routers and all 18 OcNOS-DC switches.

App note and datasheet.

The Ansible app note and the IP Maestro datasheet to share with your team. Quick form, and the PDF opens immediately.

Automating Network Management: Integrating Ansible with OcNOS

How to run Ansible with OcNOS: inventory, variables, playbooks, conditionals, loops and Jinja2 templates, with a BGP deployment example.

Get the app note

IP Maestro 3.x Datasheet

IP Maestro in one PDF: assurance and telemetry, NETCONF southbound and REST northbound interfaces, deployment sizing and supported OcNOS releases.

Get the datasheet

Plan your network automation.

We map your provisioning, configuration and monitoring tools to OcNOS: ZTP for new routers and switches, NETCONF or Ansible for configuration, gNMI for telemetry and IP Maestro where a GUI fits.

Book a demo Try OcNOS free