NETCONF, YANG & Zero-Touch Provisioning

OcNOS gives you a model-driven config surface: NETCONF over SSH/TLS, OpenConfig and native YANG, candidate datastore with commit/rollback, and Zero-Touch Provisioning that brings a new router to operational state with a DHCP lease.

Day-0 Zero-Touch Provisioning Flow

A factory-fresh OcNOS router boots, requests a DHCP lease, fetches its image and then its configuration, and reaches operational state. No operator on-site.

NETCONF and ZTP provisioning flow: OcNOS boot to DHCP to image server to config server to operational state
NETCONF and ZTP: Day-0 provisioning flow from boot through image and config servers to operational state.

Why model-driven config matters

CLI scripts don't compose, don't roll back, and don't validate inputs against a schema. NETCONF + YANG gives you a typed, transactional config surface: push a candidate, validate, commit, or discard the changes if any leaf is rejected. OcNOS exposes OpenConfig models and IP Infusion native models for OcNOS-specific knobs. Combined with Zero-Touch Provisioning, a new router reaches operational state with no operator on-site.

The OcNOS NETCONF, YANG & ZTP implementation

SSH + TLS transport

RFC 6241 NETCONF protocol, over SSH (RFC 6242) and TLS (RFC 7589), with full Get / Get-Config / Edit-Config / Commit / Validate / Lock / Discard-Changes RPC support.

Candidate + commit / rollback

Candidate datastore over NETCONF; in the CLI, commit confirmed and commit-rollback to an earlier commit from the commit history.

Day-0 provisioning

DHCP-driven boot over IPv4 or IPv6: fetch the image, install, reboot, then fetch the configuration.

What you get with OcNOS automation

  • Operational rollback. With commit history enabled, the CLI commit-rollback command returns to an earlier commit if a change goes wrong.

Standing up a model-driven operations stack?

Request a Technical Demo →

Frequently asked questions

What YANG models does OcNOS support over NETCONF?
OcNOS exposes OpenConfig models and IP Infusion native models for OcNOS-specific features.
Does OcNOS support config rollback?
Yes. NETCONF edits go to the candidate datastore and apply on commit. In the CLI, commit-rollback returns to an earlier commit from the commit history, and commit confirmed reverts a change that is not confirmed in time.
How does Zero-Touch Provisioning work in OcNOS?
A factory-fresh router boots, requests a DHCP lease, fetches its image and its configuration over TFTP or HTTP, and reaches operational state with no operator on-site.