Home/Products/OcNOS-DC
DC · AI Fabric · EVPN-VXLAN

OcNOS-DC: the data center NOS.

Open network OS for leaf-spine data center fabric. EVPN-VXLAN overlays, lossless RoCEv2 for AI GPU clusters, ZTP automation, and streaming telemetry on qualified Broadcom open hardware.

dc-spine01 · OcNOS-DC
$show bgp l2vpn evpn summary
BGP router identifier 10.0.0.1, local AS number 65001
Neighbor V AS Up/Down State/PfxRcd
10.0.0.11 4 65001 6d09h07m 342
10.0.0.12 4 65001 6d09h07m 342
$show priority-flow-control statistics all
interface pri pause sent pause received
xe1 3 0 0
$show ztp status
ZTP Version 2
ZTP Config Auto ZTP Enabled
$

Scale up, out, and across.

OcNOS-DC grows a fabric in three directions: up within a pod, out to a wider Clos fabric, and across data centers, with BGP and EVPN as the control plane.

Scale the pod up

Raise the fabric's per-switch bandwidth and port density, moving from a 100G fabric to 400G and 800G, so the same leaf-spine-super-spine pod feeds larger, higher-bandwidth compute nodes without adding more pods.

OcNOS-DC · 100G to 800G

Scale the fabric out

Add more of the same building blocks, more spine and super-spine switches and leaf pairs, to widen the Clos topology horizontally. More racks and leaves connect while every endpoint keeps any-to-any reachability, all as one EVPN and BGP fabric.

OcNOS-DC · wider Clos, any-to-any

Scale across sites

Extend beyond a single data center. A coherent interconnect links independent pods at different sites, with BGP and EVPN carrying routes between them. OcNOS-DC at every site.

OcNOS-DC · multi-site DCI

OcNOS-DC on every tier, at every site.

OcNOS-DC runs every fabric in the data center: the AI back-end, storage, frontend, and out-of-band management, all on open Broadcom hardware. Each switch runs the OcNOS-DC edition that fits its role, with one CLI and one automation toolchain across every tier and every site.

OcNOS-DC across the AI, storage, and management fabrics A reference OcNOS-DC data center. A 1:1 non-blocking AI back-end fabric and a 1:3 storage fabric both connect to the GPU servers, every switch runs OcNOS. An out-of-band management fabric on OcNOS reaches every tier: the AI fabric, the storage fabric, the frontend fabric, and the servers. RoCEv2, ECN and PFC, and DLB run across the back-end. 800G LEAF-SPINE · LOSSLESS RoCEv2 · DLB AI FABRICback-end (TH4, TH5)OcNOSSpine 1OcNOSSpine 2OcNOSSpine 3OcNOSSpine NOcNOSLeaf 1OcNOSLeaf 2OcNOSLeaf 3OcNOSLeaf N1:1800G STORAGE FABRICNVMe-oF / NFSOcNOSSpine 1OcNOSSpine 2OcNOSSpine 3OcNOSSpine NOcNOSLeaf 1OcNOSLeaf 2OcNOSLeaf 3OcNOSLeaf N1:3100G GPU SERVERS · POD 1 8 NIC per server · one per rail Server 1 GPU compute Server 2 GPU compute Server N GPU compute OOB MANAGEMENT CLOS / MLAG · reaches every tier OcNOSOOB 1 OcNOSOOB 2 FRONTEND FABRIC 3:1 · user-facing edge · separate plane OcNOS-DC · 25G / 50G / 100G 400G 100G 1G 1G 1G OOB · 1G RoCEv2 ECN / PFC DLB 400 / 800G Scale-Out

OcNOS-DC runs the AI back-end, storage, frontend, and management fabrics. Explore the AI Fabric

What the fabric actually runs.

The mechanics that make an AI data center fabric work, built on open standards rather than a proprietary black box.

Lossless RoCEv2 for RDMA

Priority Flow Control pauses only the RoCEv2 traffic class, and ECN with WRED marks packets before a queue fills, so DCQCN on the NIC slows the sender at the source. PFC deadlock detection and recovery (DC-PLUS) clears a pause deadlock. The result is a lossless RDMA fabric for xCCL collectives.

PFC 802.1QbbECN / WREDDCBXPFC deadlock recovery

EVPN-VXLAN on open standards

MP-BGP EVPN carries Type-2 MAC/IP routes over a VXLAN data plane on the Trident 3 and Trident 4 switches, and EVPN multihoming gives dual-homed servers and storage a standards-based alternative to MLAG. Routed tenant features (IRB, the anycast gateway and Type-5 routes) vary by switch model. The control plane follows RFC 7432 and RFC 8365 for interoperability.

MP-BGP EVPNType-2 MAC/IPBGP unnumberedESI multihoming

Zero-touch onboarding for a new rack

Zero Touch Provisioning brings a new leaf or spine into the fabric with its OcNOS software and a day-0 config, without a console session. Model-driven interfaces fit existing Ansible or in-house controller pipelines.

ZTP IPv4 / IPv6AnsibleNETCONF/YANGNETCONF call home

Streaming telemetry over gNMI and gRPC

In the DC-PLUS edition, OcNOS-DC streams operational state over gNMI, dial-in or dial-out, with OpenConfig data models and on-change subscriptions. That feeds closed-loop assurance and congestion dashboards without polling the CLI.

gNMI / gRPCOpenConfigOn-changeDial-in / dial-out

The economics of open networking.

Same silicon as the incumbents, bought on open terms. The commercial case for OcNOS-DC, separate from the technology.

The same Broadcom silicon, without the proprietary tax

OcNOS-DC runs on open Edgecore, UfiSpace and Celestica switches built on Broadcom Tomahawk and Trident merchant silicon, at a lower cost per port. Hardware and software are bought and refreshed on separate cycles, not bundled to a chassis lifecycle.

Open ODM hardware Lower cost per port Separate refresh cycles
How to buy

Multi-vendor hardware, no single-source lock-in

Eighteen qualified platforms from Edgecore, UfiSpace and Celestica, from 1G management switches and 25G leaves to 800G spines. Source the hardware from more than one supplier, instead of buying the switch and the software from one vendor.

Leaf, spine, and border on OcNOS-DC

Every role runs OcNOS-DC in the edition that fits it, with the same OcNOS CLI and automation used on OcNOS-SP routers. One toolchain for the whole network, not a different operating system per box.

One contract per OcNOS System

Buy the switch as an OcNOS System and one contract covers OcNOS-DC, the qualified Edgecore or UfiSpace platform, and RMA coordination. For hardware you buy yourself, IP Infusion supports the software and the hardware manufacturer supports the hardware.

A supported commercial NOS with 24/7 TAC and a roadmap

OcNOS-DC ships as a commercial product with 24/7 TAC and a roadmap. A self-built open source NOS leaves integration, hardware qualification, and support with your team. IP Infusion takes on that engineering work.

SKU & platform comparison

OcNOS-DC ships in three editions. Every edition includes IP Infusion software support. An OcNOS System also includes hardware support and RMA.

OcNOS-DC: Data Center Switches DC-MGMT DC-IPBASE DC-PLUS
Layer 2 / Layer 3•••
EVPN-VXLAN••
Ethernet for AI (RoCEv2 / PFC / ECN)••
Streaming Telemetry (gNMI/gRPC)•
Dynamic Load Balancing (DLB)•
Qualified Platforms
ASICCapacityPort Speed DC-MGMT DC-IPBASE DC-PLUS
TD3-X2120G1/10G••
TD3-X41,080G10/100G••
TD3-X52,000G25/100G••
TD3-X72,000 to 3,200G25/100G••
TH26,400G100G••
TH312,800G400G••
TD412,800G400G••
TH425,600G400G••
TH551,200G800G••

*Feature support is platform-dependent. Refer to the Feature Matrix for details. 18 qualified DC platforms available.

Across the OcNOS-DC editions
EVPN-VXLANEVPN multihomingBGP ECMP RoCEv2PFCECN WRED RDMAZTPgNMI/gRPC OpenConfigNETCONF/YANGAnsible 400G ZR+DLBsFlow
Test Drive Free Qualified Platforms Interactive Feature Matrix

OcNOS-DC vs. proprietary data center switching

OcNOS-DC runs on Broadcom silicon in open hardware, with no proprietary tax on AI networking.

✕  Proprietary DC switching
Proprietary NOS on proprietary hardware: vendor lock-in at every refresh
AI fabric features tied to the vendor's own switch hardware
AI fabric designs that couple switches, NICs, and GPUs to one supplier
Vendor-specific automation: limited portability across platforms and generations
Hardware premium over equivalent Broadcom silicon on open ODM platforms
License renewals and refresh cycles tied to the vendor hardware cadence
✓  OcNOS-DC on open Broadcom hardware
Open NOS on Edgecore and UfiSpace open hardware: multi-vendor hardware choice
RoCEv2 on OcNOS-DC: PFC and ECN from DC-IPBASE, DLB and PFC deadlock detection and recovery in DC-PLUS
Runs the AI fabric on open Broadcom switches with any GPU and NIC vendor: no single-supplier AI stack
Linux-based open APIs: Ansible, NETCONF/YANG, OpenConfig, gNMI
Broadcom silicon up to Tomahawk 5, with software and hardware on separate refresh cycles
One IP Infusion support contract covers OcNOS-DC software and hardware bought as an OcNOS System

Also an alternative to a self-built open source NOS. OcNOS-DC is a commercial NOS with 24/7 TAC, a single-vendor SLA, and RMA logistics for OcNOS Systems. A self-built open source NOS leaves integration, hardware qualification, and third-party support with your team, the engineering work IP Infusion takes on. See how OcNOS compares with an open source NOS.

Ready to deploy OcNOS-DC?

Book a technical demo, or try it free in our cloud lab: no hardware required.

OcNOS-DC: frequently asked questions

What is OcNOS-DC and what is it used for?
OcNOS-DC is IP Infusion's data center variant of OcNOS, the network operating system in production with 600+ operators across 60+ countries. It is built for leaf-and-spine fabrics that carry EVPN-VXLAN overlays, lossless RoCEv2 traffic for AI and ML clusters, and 400G or 800G DCI links. It runs on qualified Broadcom-based open switches from Edgecore, UfiSpace and Celestica. IP Infusion supports the software, and the hardware too when you buy the switch as an OcNOS System.
Which EVPN-VXLAN features does OcNOS-DC support?
OcNOS-DC supports EVPN-VXLAN with Type-2 MAC/IP routes and ARP/ND learning to limit flooding in the overlay, and EVPN multihoming for dual-homed servers and storage. EVPN-VXLAN runs on the Trident 3 and Trident 4 switches. Routed tenant features (IRB, the anycast gateway and Type-5 IP-prefix routes) vary by switch model; the Feature Matrix lists each one. The control plane is MP-BGP EVPN per RFC 7432 and RFC 8365, so it interoperates with standards-based EVPN implementations.
How does OcNOS-DC build a lossless RoCEv2 fabric for AI workloads?
OcNOS-DC carries Priority Flow Control (PFC) with QoS over Layer 3 and Explicit Congestion Notification (ECN) for RoCEv2, so RDMA traffic classes can be paused on a per-priority basis to avoid GPU-to-GPU packet drops. The DC-PLUS edition adds Dynamic Load Balancing and PFC deadlock detection and recovery. The intent is a lossless fabric for xCCL collectives such as NCCL and RCCL. Real production deployments to date have run on the order of 20 to 200 GPUs, and the design scales further as engagements grow.
What are the OcNOS-DC license tiers?
OcNOS-DC is sold in three editions. DC-MGMT carries Layer 2 switching and Layer 3 routing (OSPF, IS-IS and BGP) for out-of-band management switches. DC-IPBASE adds EVPN-VXLAN, and DC-PLUS adds Dynamic Load Balancing and streaming telemetry. Features vary by switch model; the Feature Matrix lists each platform and edition.
Which switches and Broadcom silicon does OcNOS-DC run on?
OcNOS-DC supports 18 open hardware platforms from Edgecore, UfiSpace and Celestica, from 1G management switches and 48x25G ToR leaves up to 64x800G spines. Supported Broadcom silicon includes Tomahawk 5 (51.2T, 800G), Tomahawk 4 (25.6T, 400G), Tomahawk 3, Tomahawk 2, Trident 4, and Trident 3. Every switch runs OcNOS-DC in the edition that fits its role, so operators keep one CLI and one automation toolchain across leaf, spine, and border roles.
How does OcNOS-DC handle automation and zero-touch provisioning?
OcNOS-DC exposes NETCONF and gNMI northbound, with OpenConfig and YANG data models, so it fits existing Ansible or in-house controller pipelines. Zero Touch Provisioning brings a new leaf or spine into the fabric with its software and day-zero configuration, without console access. The DC-PLUS edition includes streaming telemetry over gNMI for closed-loop assurance.
What is scale-up vs scale-out vs scale-across for a data center fabric?
These are three ways OcNOS-DC scales the same fabric. Scale-up grows a single pod's capacity by raising per-switch bandwidth and port density, for example moving from a 100G fabric to 400G and 800G, so the same leaf-spine-super-spine topology feeds larger, higher-bandwidth compute nodes without adding more pods. Scale-out grows capacity by adding more of the same building blocks, more spine and super-spine switches and leaf pairs, widening the Clos topology horizontally so more racks and leaves connect while every endpoint keeps any-to-any reachability. Scale-across extends beyond a single data center: a coherent interconnect links independent pods at different sites, with BGP and EVPN carrying routes between them. OcNOS-DC covers all three, with the edition that fits each switch's role.