Home/ Products/ OcNOS
SP · DC · AI Fabric · OEM

OcNOS: the brain inside the box.

OcNOS is the carrier-grade software that turns open merchant-silicon hardware into a production router or switch. It comes in two families, OcNOS-SP and OcNOS-DC, each sold in editions, with a shared CLI, plus OcNOS for OEMs. In production with 900+ operators across 60+ countries.

What is a network operating system?

In production with
NTT eww ITandTEL DIGI Communications Lintasarta Scott Data Uniti
Open hardware choice 40+ qualified Edgecore, UfiSpace and Celestica platforms
Carrier Ethernet E-Line, E-LAN, E-Tree on open hardware
One OcNOS family, one CLI SP · DC · AI Fabric · OEM: editions by role
One vendor with OcNOS Systems Software · hardware · RMA: one support contract
What a NOS does

Open hardware becomes a router or switch only when a NOS runs on it.

A network operating system forwards every packet, runs BGP with the rest of the internet, programs the merchant-silicon ASIC, exposes APIs for automation, and keeps the network up around the clock.

Open hardware, before a NOS.

An open switch from Edgecore or UfiSpace ships as merchant-silicon hardware with no networking software on it: no BGP, no EVPN, no CLI, no telemetry, and no way to push config or fail over a link until a NOS is installed.

[ no os installed ]

The same box becomes a carrier-grade router or switch.

Boot OcNOS and the same box becomes carrier-grade infrastructure. BGP holds the full internet table, SR-MPLS computes Flex-Algo paths, EVPN-VXLAN builds the leaf-spine fabric, and RoCEv2 keeps the AI cluster lossless. It runs an industry-standard CLI and the APIs orchestrators already speak, and as an OcNOS System it puts hardware, software and RMA on one support contract.

ocnos@core-01 # show bgp summary
Inside the box

The OcNOS stack, layer by layer.

Open hardware at the bottom, ZebOS routing daemons in the middle, and NETCONF and gNMI on top. Six layers; select any one to see what it does.

Layer 06: Orchestration

IP Maestro automates an OcNOS fleet from Day 0 to Day 2.

Day-0 zero-touch provisioning, Day-1 golden-config templates, Day-2 drift detection, gNMI telemetry to your dashboards. It is optional, and it sits alongside the official Ansible collection.

ZTPGolden config Drift detectTelemetry Ansible
Layer 05: Northbound

Open APIs and standard models.

An industry-standard CLI for engineers, and NETCONF/YANG, gNMI and OpenConfig for automation. BGP-LS for controllers. Streaming telemetry, dial-in and dial-out telemetry to your existing collector.

CLINETCONF/YANG gNMIOpenConfig sFlow SNMPv3BGP-LS
Layer 04: Control plane

The ZebOS stack: routing in production since 1999.

Multi-protocol routing daemons: BGP, OSPF, IS-IS, PIM, BFD, LDP, RSVP-TE, SR-MPLS with Flex-Algo and TI-LFA, EVPN-VXLAN, the DCB stack for lossless RoCEv2, IEEE 1588v2 timing, Carrier Ethernet, and ZR and OpenZR+ coherent optics. One control plane under every OcNOS-SP and OcNOS-DC edition.

BGP · OSPF · IS-ISSR-MPLS · Flex-Algo EVPN-VXLANPFC · ECN · DLB Carrier Ethernet · Y.17311588v2 · SyncE 400G ZR · OpenZR+
Layer 03: HAL

One control plane across the qualified Broadcom silicon.

The Hardware Abstraction Layer translates control-plane intent into ASIC programming on Tomahawk, Trident, Qumran and Jericho 2C+. The CLI and the automation stay the same whichever silicon is in the box.

Tomahawk 5Tomahawk 4 Trident 4Qumran2 Jericho 2C+
Layer 02: Boot & OS base

ONIE installs OcNOS on a Linux base.

The Open Network Install Environment loads OcNOS the way open network software is installed: load the image from the ONIE prompt and reboot. Upgrades run from the OcNOS shell, and engineers keep the Linux tools they already know.

ONIELinux base Standard tooling
Layer 01: Open hardware

40+ qualified platforms. Buy the box that fits the build.

Compact cell-site routers through 14.4 Tbps SP core routers and 51.2 Tbps 800G AI-fabric spines, from Edgecore, UfiSpace and Celestica, all on Broadcom merchant silicon: 26 qualified for OcNOS-SP and 18 for OcNOS-DC.

EdgecoreUfiSpace Celestica40+ platforms
Where OcNOS runs

One OcNOS family, from carrier core to embedded OEM.

Service-provider routing, data-center fabric, and AI fabric, each with a full feature set. Plus OEM, where the same routing stack ships embedded inside vendor products.

See where OcNOS runs across the network

OcNOS-SP · Service Provider

Carrier-grade SR-MPLS, IPoDWDM, and 5G backhaul timing on open hardware.

OcNOS-SP routers at every tier, from the cell site to the IP core, each running the edition its role needs: IPBASE, MPLS, CSR or PLUS. In production with 900+ operators across 60+ countries, including NTT, DIGI and Uniti.

  • SR-MPLS, Flex-Algo, TI-LFA fast reroute, BGP-LU
  • Carrier Ethernet E-Line, E-LAN, E-Tree, Y.1731 OAM
  • 400G ZR and OpenZR+ IPoDWDM on 7 qualified routers
  • IEEE 1588v2 G.8275.1/.2 and SyncE for 5G backhaul
Explore OcNOS-SP
PEERS full table Internet Edge BGP · RPKI SR-MPLS OcNOS-SP CORE P · SR Flex-Algo · TI-LFA PE / AGG EVPN · E-LAN 5G CSR PTP · SyncE backhaul IPoDWDM 400G ZR/ZR+
OcNOS-DC · Data Center

EVPN-VXLAN leaf-spine on Broadcom Tomahawk and Trident.

Every switch runs OcNOS-DC, in the edition that fits its role: IPBASE, PLUS or DC-MGMT. eBGP unnumbered underlay, EVPN overlays, ZTP rack onboarding, gNMI streaming telemetry. OcNOS-DC shares one CLI and one automation model with OcNOS-SP, so one team runs both.

  • EVPN-VXLAN overlays with multi-homing & ARP/ND flood control
  • ZTP zero-touch provisioning over IPv4 & IPv6
  • gNMI streaming telemetry, dial-in and dial-out
  • DCI: 400G ZR and OpenZR+ on selected switches
Explore OcNOS-DC
SPINE PLUS SPINE PLUS LEAF A LEAF B LEAF C LEAF D DCI RACK storage RACK CPU · K8s RACK edge RACK mgmt REMOTE
OcNOS AI Fabric · Lossless RoCEv2

Lossless 800G networking for GPU clusters.

OcNOS-DC brings the DCB stack for RoCEv2 RDMA, PFC over L3, ECN, ETS, DCBX and Dynamic Load Balancing, to Broadcom Tomahawk 5 800G spines (Edgecore AIS800-64D, UfiSpace S9321-64E) with Tomahawk 4 400G leaves. As an OcNOS System, the fabric comes with one support contract for software, hardware and RMA.

  • PFC over L3, ECN and ETS for lossless RDMA queues
  • Dynamic Load Balancing moves flows off congested links
  • eBGP unnumbered underlay, ZTP, DCBX automation
  • PFC deadlock detection and recovery
Explore AI Fabric
SPINE 800G Tomahawk 5 · 51.2T SPINE 800G Tomahawk 5 · 51.2T LEAF 400G LEAF 400G LEAF 400G LEAF 400G GPU RACK RoCEv2 RDMA GPU RACK PFC · ECN DLB GPU RACK AllReduce AllGather STORAGE NVMe-oF
OcNOS for OEMs · Embedded

Building hardware? Use a routing stack first shipped in 1999.

Hardware vendors do not have to write a routing stack from scratch. License OcNOS CP, the control-plane source code formerly known as ZebOS, to compile into your own OS or appliance, or OcNOS Flex, a complete binary NOS image that IP Infusion ports to your hardware. ZebOS and OcNOS CP have a lineage spanning 300+ OEMs.

  • Flex: complete binary NOS, ported by IP Infusion
  • CP: control-plane source code, compiled into your OS
  • ZebOS lineage: first shipped to OEMs in 1999
  • CP: license fee plus per-unit royalty; Flex: per-box license
Explore OEM Options
VENDOR PRODUCT (OEM) OcNOS Flex binary NOS image drop in · turnkey OcNOS CP source · control plane your data plane · deep ZebOS AND OcNOS CP LINEAGE · 300+ OEMs
The spec sheet

One OcNOS family, from the metro edge to the AI fabric.

The OcNOS family that runs carrier and transport networks in production also builds the AI Ethernet fabric. You do not trade carrier-grade routing to get a modern data-center fabric, and you do not run a data-center-only NOS that cannot carry your transport. OcNOS-SP and OcNOS-DC share the same industry-standard CLI and operational model, and pre-integrated OcNOS Systems add one support contract and one RMA path.

Capability What OcNOS delivers Qualified Broadcom silicon and platforms
Service provider, transport, and broadband
IP/MPLS core routing BGP, IS-IS, OSPF, LDP, RSVP-TE, and a 1/2/3 level queuing hierarchy. Jericho 2C+ (up to 14.4 Tbps), Qumran 2C
Segment routing SR-MPLS, Flex-Algo, TI-LFA fast reroute, BGP-LU. Initial SRv6 support on selected routers, with more in development. SR-MPLS on all 26 qualified OcNOS-SP routers (Qumran, Jericho 2C+)
Carrier Ethernet E-Line, E-LAN, E-Tree services, a 1/2/3 level queuing hierarchy, Y.1731 and CFM OAM. Qumran 2A, Qumran 2U, Qumran 2C
IP over DWDM (IPoDWDM) 400G ZR and OpenZR+ coherent pluggables driven from the routing CLI, with no separate transponder shelf. 7 OcNOS-SP routers (Jericho 2C+, Qumran 2C, Qumran 2A; 18 ZR+ capable ports on the S9610-36D), Trident 4 and Tomahawk 4 switches
Timing and sync for 5G backhaul IEEE 1588v2 PTP with the G.8275.1 and G.8275.2 telecom profiles, boundary and transparent clocks, SyncE. Qumran 2A, Qumran 2U cell site gateway
Broadband and subscriber edge Carrier-grade ISP aggregation and edge routing; vBNG supplied by an ecosystem partner. Qumran 2A, Qumran 2C
Data center and AI Ethernet fabric
Leaf-spine fabric EVPN-VXLAN overlays, EVPN multi-homing, ARP/ND flood control, eBGP unnumbered underlay, ZTP. Trident 3, Trident 4, Tomahawk 4
Lossless RoCEv2 for GPU and AI PFC over L3, ECN, ETS, DCBX, and PFC deadlock detection and recovery. Tomahawk 5 (51.2 Tbps, 64x800G), Tomahawk 4
Dynamic load balancing DLB moves flows off congested ECMP paths, with reactive path rebalance on selected platforms. Tomahawk 4 and Tomahawk 5
800G and 400G switching 64x800G OSFP spines with 400G leaves for GPU back-end fabrics. Edgecore AIS800-64D, AS9817-64D; UfiSpace S9321-64E, S9321-64EO
AI fabric scale Two tiers reach 4,096 GPUs at 800G per GPU on Tomahawk 5; three tiers reach 16,384. These are reference-design ceilings based on Clos radix calculations, not measured figures. Tomahawk 5 leaves and spines
Data center interconnect 400G ZR and OpenZR+ coherent optics to a remote data center, from the same switch. Trident 4, Tomahawk 4; 800G ZR on two Tomahawk 5 platforms
Shared across both families
Model-driven management OpenConfig and native YANG over NETCONF, gNMI streaming telemetry, plus SNMP for existing NOC tooling. All qualified platforms; gNMI per platform
Automation, Day 0 to Day 2 ZTP and the official Ansible collection (ipinfusion.ocnos). All qualified platforms
Support and delivery One industry-standard CLI across both families. OcNOS Systems add one purchase order, one 24/7 TAC SLA, and one RMA path across software and qualified hardware. 40+ qualified platforms

Feature support is per platform and per OcNOS edition. The Feature Matrix and Hardware Compatibility List below are the authoritative, per-platform source of truth. AI-fabric GPU counts are reference-design ceilings, not measured figures.

Proof

In production from Tier-1 carriers to regional broadband.

In production with 900+ operators across 60+ countries: Tier-1 IOWN transport, sovereign MPLS, regional broadband and open fiber transport, each on the OcNOS edition its role needs.

How OcNOS compares

Why pick OcNOS over a proprietary chassis?

OcNOS brings carrier-grade routing to qualified open hardware, and as an OcNOS System it comes with one accountable vendor for software, hardware, and RMA.

✕ Proprietary chassis
Software tied to one vendor's own chassis
Hardware choice limited to that vendor's catalogue
Refresh cycles set by the vendor's roadmap
Often separate operating systems for SP, DC, and AI fabric
✓ OcNOS on qualified open hardware
Broadcom merchant silicon on 40+ qualified Edgecore, UfiSpace and Celestica platforms
Licensed by edition and platform capacity
With OcNOS Systems, one support contract covers software, hardware, and RMA
One OcNOS family and one CLI across SP, DC, and AI fabric: one ops team

Also an alternative to a self-integrated open-source NOS. IP Infusion qualifies each platform per model and ASIC stepping and supports OcNOS with 24/7 TAC, on a routing stack first shipped in 1999. Read a detailed comparison with a proprietary router NOS.

FAQ

Frequently asked questions

OcNOS is IP Infusion's commercial network operating system: the software that turns an open switch from a box of silicon into a production router. It is in production with 900+ operators across 60+ countries on 40+ qualified open hardware platforms. One OcNOS family with one CLI covers service-provider routing (SR-MPLS, IPoDWDM, 5G backhaul timing) as OcNOS-SP, data-center and AI fabric (EVPN-VXLAN leaf-spine, lossless RoCEv2 on Broadcom Tomahawk 5) as OcNOS-DC, each sold in editions, plus OcNOS for OEMs (OcNOS CP source licensing and OcNOS Flex). Its routing stack, ZebOS, has shipped in carrier and OEM products continuously since 1999.
OcNOS-SP is the service-provider family, sold in IPBASE, MPLS, CSR and PLUS editions: SR-MPLS, BGP, EVPN, Carrier Ethernet, IEEE 1588v2 PTP and SyncE timing for 5G backhaul, and 400G IPoDWDM with ZR and OpenZR+ coherent optics on selected routers. PLUS also adds initial SRv6 support on selected routers, with more in development. OcNOS-DC is the data-center family, sold in IPBASE, PLUS and DC-MGMT editions: EVPN-VXLAN leaf-spine overlays, lossless RoCEv2 with PFC and ECN for AI and GPU clusters, ZTP, and gNMI streaming telemetry on Broadcom Tomahawk and Trident silicon. Both families share one CLI and one automation model. OcNOS for OEMs comes in two licensing models: OcNOS CP, the control-plane source code formerly known as ZebOS, and OcNOS Flex, a complete binary NOS image that IP Infusion ports to the OEM hardware. ZebOS and OcNOS CP have a lineage spanning 300+ OEMs.
Yes. OcNOS-SP runs service-provider and transport networks (SR-MPLS, 400G ZR and OpenZR+ IPoDWDM, Carrier Ethernet, IEEE 1588v2 timing) and OcNOS-DC runs data-center and AI Ethernet fabric (EVPN-VXLAN, lossless RoCEv2 with PFC over L3, ECN and DLB on Broadcom Tomahawk 5). Each family is sold in editions by role, and both share one industry-standard CLI and one automation model, so a neocloud or operator running both an AI training or inference fabric and a carrier WAN uses one operations model and one team. OcNOS runs the carrier and transport side in production today across 900+ networks; the AI fabric is built on the same OcNOS family on open 800G hardware. See how a neocloud runs both on OcNOS.
Yes. OcNOS-DC ships a Data Center Bridging stack for RoCEv2 RDMA: PFC for lossless queues, ECN for early backpressure, ETS for class scheduling, DCBX, and DLB to move flows off congested ECMP paths. It is qualified on Broadcom Tomahawk 5 800G platforms (Edgecore AIS800-64D, UfiSpace S9321-64E) for spines and Tomahawk 4 400G platforms for leaves. AI fabrics deploy with an eBGP unnumbered underlay, ZTP and gNMI streaming telemetry. See the AI Fabric solution page.
OcNOS runs carrier-grade routing and data-center switching on qualified open hardware with Broadcom merchant silicon, so the software and the hardware can be sourced separately or bought together as an OcNOS System with one support contract. Compared with a proprietary NOS, the difference is hardware choice: OcNOS is licensed by edition and platform capacity on Edgecore, UfiSpace and Celestica platforms. Compared with a self-integrated open-source NOS, the difference is accountability: IP Infusion qualifies each platform per model and ASIC stepping, supports it with 24/7 TAC, and builds on a routing stack first shipped in 1999. Read a detailed comparison with a proprietary router NOS.
OcNOS runs on 40+ qualified open hardware platforms based on Broadcom merchant silicon (Qumran, Jericho 2C+, Trident, Tomahawk 4 and 5) from Edgecore, UfiSpace and Celestica: 26 for OcNOS-SP and 18 for OcNOS-DC. Form factors range from compact 5G cell-site gateways through 14.4 Tbps SP core routers to 51.2 Tbps 800G AI-fabric spines. The Hardware Compatibility List shows per-platform feature support.
Free OcNOS VM downloads: virtual machine images for EVE-NG, GNS3, VirtualBox, and KVM. For a pilot on qualified hardware, IP Infusion sales can ship OcNOS Systems (PRO on Edgecore or FAST on UfiSpace) preloaded with OcNOS. See OcNOS Systems.
Yes. OcNOS is in production with 900+ operators across 60+ countries, including the NTT 400G IOWN solution, DIGI for broadband aggregation, Uniti Fiber for open transport, and sovereign MPLS networks at eww ITandTEL in Austria and Exatel in Poland. OcNOS earned MEF 3.0 Carrier Ethernet certification (E-Line, E-LAN, E-Tree) on the UfiSpace S9510-28DC, and the TIP Validated Solution Gold Badge from the Telecom Infra Project. Each hardware platform is qualified per model and ASIC stepping, and OcNOS-SP supports IEEE 1588v2 PTP with the G.8275.1 and G.8275.2 telecom profiles on qualified routers.
ZebOS is IP Infusion's multi-protocol routing stack, first shipped to telecom OEMs in 1999 and embedded in products from 300+ vendors since. It implements BGP, OSPF, IS-IS, MPLS, segment routing, BFD, PIM: the full carrier-grade routing protocol set. OcNOS is the productized NOS that wraps ZebOS: the same control-plane code that OEM equipment has carried since 1999, packaged with the hardware abstraction layer, northbound APIs (NETCONF/gNMI/OpenConfig), and IP Maestro orchestration. OEMs license that control plane as source code under its current name, OcNOS CP. See OcNOS for OEMs.
An open network operating system (open NOS) is router and switch software that is decoupled from the hardware, so the NOS and the underlying switch can be sourced separately instead of bought as one fixed appliance. This gives operators hardware choice, multi-vendor sourcing, and open economics while keeping standard routing, EVPN, and automation. OcNOS is a production open NOS, delivered by IP Infusion as complete routers and switches.
OcNOS is a commercial open NOS, not open-source software. Open here means open hardware and open standards: OcNOS runs on standard merchant-silicon switches rather than locked appliances. Unlike community open-source projects, it ships as a supported product with 24/7 TAC, and IP Infusion delivers it as complete routers and switches: an OcNOS System puts software, hardware and RMA on one support contract.

Ready to see OcNOS in action?

Book a technical demo, or get a free VM running on your laptop in minutes.