Home / Products / Automation & Programmability
OcNOS 7.0 · Ansible · NETCONF/YANG · gNMI · ZTP · Docker

Automation &
Programmability

Your existing NetDevOps tools work on day one. OcNOS exposes every configuration and operational state through standard, open interfaces, with no screen-scraping and no proprietary orchestrators.

Network teams are shifting from CLI-first operations to programmable, API-driven automation. OcNOS is built for this transition. Every protocol state, configuration element, and operational metric is accessible through Ansible, NETCONF/YANG, gNMI, REST, and Docker: the same standard interfaces Cisco IOS-XR and Juniper Junos expose. The difference is the platform: open hardware, open software, and a fraction of the cost.
Application Note

The playbooks engineers use.

A field-proven walkthrough of integrating Ansible with OcNOS: modules, inventory patterns, and the Day-0/1/2 playbook structure.

The problem OcNOS automation solves
Before

Manual CLI operations

Config pushed device-by-device over SSH. SNMP polling with 5-minute intervals. Engineers on-site to rack and cable new hardware. No structured state, no rollback.

→
After OcNOS

Fully programmable, Day 0 to Day N

Ansible deploys BGP and EVPN-VXLAN across 100 switches in minutes. gNMI streams telemetry with sub-second updates. ZTP boots new hardware with zero human touch. Rollback in seconds.

Programmable Interfaces

Six ways to automate OcNOS

Pick one or use all six together. OcNOS doesn't force a proprietary orchestrator. It works with the tools your team already uses.

Ansible Collection

ansible-galaxy collection install ipinfusion.ocnos

Official IP Infusion collection on Ansible Galaxy. Modules include ocnos_facts, ocnos_config, ocnos_command, ocnos_bgp_facts, and ocnos_isis_facts. Jinja2 templating for dynamic, fleet-wide provisioning. Use the same Ansible playbooks you already write. OcNOS speaks the same language as Arista, Juniper, and Cisco.

ansible-playbook deploy-sr-mpls.yml
$ansible-playbook -i inventory deploy-sr-mpls.yml
ok: [spine-01] – IS-IS + SR-MPLS configured
ok: [leaf-01..04] – BGP-LU overlay up
ok: [all] – config backup saved
PLAY RECAP · 5 switches · 0 failures · 0:42 elapsed
Ansible Guide in OcNOS Docs

NETCONF / YANG 1.1

IPI-native + OpenConfig models · RFC 6241

Full NETCONF 1.1 with both IPI-native and OpenConfig YANG data models. Structured config and operational state retrieval: get, edit-config, commit, rollback, and candidate datastore. Works with Python's ncclient library, Ansible's netconf_config module, or any NETCONF client.

netconf – edit-config + commit
<edit-config>
<target><candidate/></target>
<config>...YANG payload...</config>
</edit-config>
<ok/> ← candidate locked
<commit/> ← applied atomically

gNMI Streaming Telemetry

OcNOS 7.0 · On-Change + Periodic · 100+ sensor paths

Real-time, push-based telemetry via gNMI over gRPC. Replaces SNMP polling with structured, sub-second updates across interfaces, BGP session state, MPLS forwarding, QoS queues, PFC/ECN counters, and system health. Connect to Telegraf, Prometheus, or any gRPC collector, then visualise in Grafana.

gnmic subscribe – interfaces
$gnmic subscribe --path /interfaces/interface[name=et-0/0/1]/
in-octets: 4,218,753,012
out-octets:3,874,112,440
mode: ON_CHANGE · encoding: PROTO

Zero Touch Provisioning

DHCP + TFTP/HTTP · Day 0 automation

Rack it. Cable it. Power it on. ZTP handles everything else. DHCP assigns an address and points to a provisioning server. The switch downloads its OS image and startup config over TFTP or HTTP, applies it, and joins the network, with no console cable and no engineer on-site. Combine ZTP with Ansible for a complete Day 0-to-Day 2 pipeline.

Real-world use case: A 48-node AI GPU cluster spine-leaf fabric provisioned over a weekend with zero on-site engineers. ZTP boots each switch, Ansible deploys BGP + PFC configuration, gNMI confirms lossless fabric.

IP Maestro GUI Orchestration

Web UI · REST API · Single-pane OcNOS management

For teams that want visual control alongside API automation. IP Maestro provides an interactive topology map of your entire OcNOS estate, GUI-driven ZTP dashboards, software lifecycle management (upgrade, schedule, rollback), streaming telemetry visualization, and configuration templates. Also exposes a REST API for integration with OSS/BSS and CI/CD pipelines.

Explore IP Maestro

Docker & On-Switch Containers

OcNOS 7.0 · Docker · Kubernetes

OcNOS 7.0 natively hosts Docker containers directly on the switch. Run Telegraf agents, Zabbix proxies, custom Python monitoring scripts, or security tools alongside the NOS, without external compute hardware. Kubernetes (K8s) is also supported for container lifecycle orchestration across a fleet.

Also: OcNOS exposes standard SNMP MIBs, so it can be monitored with Zabbix's generic SNMP templates, keeping legacy SNMP-based NOC tooling working alongside gNMI.

100+ gNMI Sensor Paths
6 Automation Interfaces
0 Proprietary Orchestrators Needed
600+ Production Networks
Day 0 First Automated Push
Full Lifecycle Coverage

Day 0 → Day 1 → Day 2

OcNOS covers the complete operational lifecycle with open, standard tooling. No proprietary orchestrators, no CLI scripting, no SNMP polling.

Day 0: Provision

Hardware joins the network itself

Switch powers on. DHCP assigns an IP. ZTP downloads the OcNOS image and base config over TFTP/HTTP. Device registers in IP Maestro. No console cable. No engineer on-site. Entire rack provisioned while your team sleeps.

ZTP DHCP IP Maestro
Day 1: Configure

Services deployed in minutes, not days

Ansible playbooks push BGP, MPLS, EVPN-VXLAN, QoS, ACLs, and timing config across the fleet. NETCONF/YANG ensures structured, validated pushes with rollback on failure. IP Maestro templates for intent-based deployment.

Ansible NETCONF/YANG OpenConfig IP Maestro
Day 2: Operate

Real-time visibility, automated remediation

gNMI streams sub-second telemetry to Telegraf → Prometheus → Grafana. Ansible handles config drift detection, scheduled backups, and software upgrades. Docker runs custom tools on-switch. IP Maestro provides topology alerts and lifecycle scheduling.

gNMI Telegraf Grafana Docker Zabbix
Ecosystem

Works with your existing stack

OcNOS speaks standard protocols. No forklift of your toolchain. The tools your team already knows work on day one.

Config Management

Ansible

Official Galaxy collection: ipinfusion.ocnos

Telemetry Collector

Telegraf

gNMI input plugin, direct subscription

Metrics Store

Prometheus

gNMI exporter, time-series metrics

Visualisation

Grafana

Pre-built dashboards for OcNOS telemetry

SNMP Monitoring

Zabbix

Standard SNMP MIBs, works with Zabbix SNMP templates

Python NETCONF

ncclient

Standard Python library, full NETCONF 1.1

gNMI CLI Client

gnmic

Subscribe, get, set: command-line testing

On-Switch Compute

Docker / K8s

Native container runtime in OcNOS 7.0

Common Questions

OcNOS automation, answered

Questions network engineers actually ask before deploying.

Does OcNOS support Ansible?
Yes. IP Infusion publishes an official Ansible Collection on Ansible Galaxy (ipinfusion.ocnos). It includes modules for facts gathering, command execution, configuration management, and protocol-specific operations including ocnos_facts, ocnos_config, ocnos_command, ocnos_ping, ocnos_bgp_facts, and ocnos_isis_facts. Playbooks use Jinja2 templating for fleet-wide, dynamic provisioning across hundreds of OcNOS devices.
What YANG models does OcNOS support?
OcNOS supports both IPI-native YANG models and OpenConfig models over NETCONF 1.1. This allows structured configuration and operational state retrieval: get, edit-config, commit, rollback, and candidate datastore operations. The same model-driven approach used by Cisco IOS-XR and Juniper Junos. Python's ncclient library works directly with OcNOS NETCONF.
Can I stream OcNOS telemetry to Grafana or Prometheus?
Yes. OcNOS 7.0 supports gNMI streaming telemetry with both on-change and periodic subscription modes. Connect directly to Telegraf (gNMI input plugin), Prometheus (gNMI exporter), or any gRPC-compatible collector and visualise in Grafana. Over 100 sensor paths are available covering interfaces, BGP state, MPLS labels, QoS queues, PFC counters, and system health, replacing SNMP polling with push-based, structured data.
What is Zero Touch Provisioning (ZTP) in OcNOS?
ZTP automates Day 0 device setup entirely. When a new switch powers on, it uses DHCP to locate a provisioning server, then downloads the correct OcNOS image and startup configuration via TFTP or HTTP, with no console cable and no engineer on-site. Combined with Ansible, ZTP covers the full Day 0-to-Day 2 lifecycle: ZTP handles initial boot and image delivery, Ansible handles ongoing config management, and gNMI handles operational monitoring.
Can I run Docker containers directly on OcNOS?
OcNOS 7.0 natively supports Docker containers on-switch. This lets operators run third-party monitoring agents (Telegraf, Zabbix), security tools, or custom Python/Go scripts directly alongside the NOS, without external compute. Kubernetes (K8s) is also supported for container lifecycle management across a fleet of OcNOS switches.
Does OcNOS work with Zabbix for SNMP monitoring?
Yes. OcNOS exposes standard SNMP MIBs, so it can be monitored with Zabbix using Zabbix's generic SNMP device templates. For teams still using SNMP-based NOC tooling, OcNOS runs SNMP alongside gNMI. You can operate both in parallel during a migration to streaming telemetry.
How does OcNOS automation compare to Arista EOS or Cisco NX-OS?
OcNOS exposes the same standard interfaces, NETCONF/YANG, gNMI, OpenConfig, and Ansible, that Arista EOS and Cisco NX-OS do. The difference is platform: OcNOS runs on validated open hardware from Edgecore, UfiSpace, and other whitebox vendors, at significantly lower total cost. Your existing Ansible playbooks and Grafana dashboards can migrate to OcNOS with minimal changes.
Automate These Products

One toolchain for your entire open network

Every automation interface on this page works with OcNOS-SP, OcNOS-DC, and IP Maestro: one consistent pipeline across your estate.

Get Started Today

See OcNOS automation in action

Book a live demo with our engineering team. Bring your automation requirements, and we'll show you exactly how OcNOS integrates with your pipeline.