Frequently Asked Questions

OcNOS & open networking, answered.

Common questions about disaggregated networking, OcNOS, and how IP Infusion compares to traditional network vendors including Cisco, Juniper, and Nokia.

Quick links

Can't find your answer here? Talk to an engineer who has deployed OcNOS in production.

Book a Demo →
What is disaggregated networking and why does it matter?
Disaggregated networking decouples network software from proprietary hardware, allowing operators to run a carrier-grade NOS like OcNOS on validated open hardware from ODMs like Edgecore and UfiSpace. This gives service providers hardware choice, lower TCO, and faster innovation cycles compared to traditional integrated chassis from Cisco, Juniper, or Nokia.
How is IP Infusion different from other open networking NOS vendors?
Among open networking NOS vendors, IP Infusion is distinctive in offering first-line support for software, hardware, and RMA under a single unified SLA via our integrated PRO/FAST bundles and partner network. Most other open NOS options require operators to coordinate separate relationships between the NOS provider and the hardware ODM. IPI also has 26 years of carrier-grade networking experience and 600+ customers worldwide.
What use cases does OcNOS support?
OcNOS supports the full range of service provider and data center use cases: SR-MPLS core and aggregation, metro transport with 400G IPoDWDM and ZR+ coherent optics, broadband access (BEAD-ready), AI fabric with lossless RoCEv2 for GPU clusters, EVPN-VXLAN data center fabric, and data center interconnect (DCI).
Can OcNOS replace Cisco IOS-XR or Junos in a production network?
Yes. OcNOS is deployed in production at 600+ operators globally, including Tier 1 service providers. It delivers carrier-grade protocol support (IS-IS, BGP, SR-MPLS, MPLS-TP, EVPN-VXLAN), IEEE 1588v2 timing, and MEF 3.0 certification — the same requirements met by traditional proprietary NOS platforms.
What hardware platforms does OcNOS support?
OcNOS is validated on 50+ open hardware platforms from ODMs including Edgecore and UfiSpace. Platforms range from 1G access switches to 25.6 Tbps spine switches. The full Hardware Compatibility List (HCL) is available in the IP Infusion documentation portal.
How does IP Infusion support compare to buying whitebox hardware separately?
With most open networking approaches, operators must manage separate support contracts for NOS software and hardware — leading to finger-pointing between vendors during outages. IP Infusion provides a single SLA covering OcNOS software, validated hardware, and RMA logistics. One vendor owns the full stack.
What is OcNOS-SP vs OcNOS-DC?
OcNOS-SP is the service provider variant — built for access, aggregation, metro transport, and core networks with SR-MPLS, MPLS-TP, IPoDWDM, and BNG capabilities. OcNOS-DC is the data center variant — optimized for leaf-spine fabrics, EVPN-VXLAN, lossless RoCEv2 for AI workloads, and 400G/800G switching. Both run on open hardware and share the same automation interfaces.
Does OcNOS support network automation?
Yes. OcNOS provides NETCONF/YANG (OpenConfig and IPI models), gNMI streaming telemetry, a REST API, an Ansible collection (ipinfusion.ocnos), zero-touch provisioning (ZTP), and on-switch Docker containers. All standard automation tools work on day one with no screen-scraping required.
What is IP Maestro?
IP Maestro is IP Infusion's network management and orchestration platform. It provides multi-device lifecycle management, real-time telemetry dashboards, GUI-driven ZTP, configuration templates, and a REST API for managing OcNOS deployments at scale.

Still have questions?

Talk to an IP Infusion network architect. Every demo is led by someone who has deployed OcNOS in production.

Book a Technical Demo →