UDP 4791 · PFC + ECN · DCQCN

RoCEv2: Lossless Ethernet for AI Fabrics

RoCEv2 is how RDMA runs on standard Ethernet: it encapsulates RDMA in UDP/IP and uses UDP destination port 4791, so GPU collective traffic is routable across a normal leaf-spine fabric. It needs a lossless fabric built from PFC and ECN, with DCQCN as the congestion-control loop, and OcNOS delivers that full toolkit today on supported 400G and 800G open hardware.

UDP 4791RoCEv2 destination port
up to 800Gopen RoCEv2 platforms
1 NOSOcNOS-DC on open hardware
256 to 4,096GPU reference designs
The lossless fabric

The same GPUs on a lossless leaf-spine fabric

A compact rail slice: two spines and two leaves carrying RoCEv2 between four GPUs. PFC pause frames travel hop by hop on congestion, while ECN marks elephant flows for DCQCN reaction at the source. RDMA is encapsulated in UDP/IP on destination port 4791, so the same traffic is routable across a standard Ethernet fabric.

RoCEv2 AI fabric topology: two spines, two leaves, and four GPUs, with PFC pause arrows on lossless RoCEv2 traffic
RoCEv2: two-spine, two-leaf AI fabric carrying lossless GPU traffic with PFC pause flow.
Why RoCEv2 matters for AI fabrics

Near-zero loss keeps GPU collectives efficient

GPU collectives (all-reduce, all-gather, all-to-all) generate elephant flows that saturate single fabric paths and demand near-zero loss to keep training jobs efficient. Drop a single packet on a 400G RoCEv2 link and the affected NIC re-transmits the entire RDMA send window, measurable as seconds of GPU idle time. RoCEv2 turns a leaf-spine fabric into a lossless transport for these workloads by encapsulating RDMA in UDP/IP on destination port 4791, so the same traffic is routable across Layer 3.

Parameter RoCEv1Layer 2 RoCEv2UDP/IP, routable
EncapsulationRDMA carried directly over Ethernet (dedicated EtherType).RDMA encapsulated in UDP/IP, using UDP destination port 4791.
Network layerLayer 2 only; confined to a single broadcast domain.Layer 3 routable across a standard leaf-spine fabric.
ECMP entropyNo IP or UDP header to hash; limited path spreading.UDP source port varied as a flow identifier to spread traffic across ECMP paths.
Lossless requirementNeeds a lossless fabric built from PFC and ECN.Needs a lossless fabric built from PFC and ECN, with DCQCN as the congestion-control loop.
Reach and scaleWithin a rack or single subnet.Routed data center fabrics; reference designs for 256 to 4,096 GPU clusters.
Lossless by design

The controls that keep the fabric lossless

A RoCEv2 fabric stays lossless through three cooperating mechanisms: priority flow control pauses the right traffic class, ECN and DCQCN hold throughput without loss, and adaptive routing keeps the few large flows off congested uplinks.

Priority Flow Control

Per-priority pause

802.1Qbb PFC pauses a single traffic class hop by hop so the queues carrying RDMA never drop. OcNOS pairs it with a PFC deadlock watchdog that detects a stalled priority and auto-recovers before it propagates.

Congestion control

ECN marking and the DCQCN loop

WRED-based ECN marks packets as queues build, and DCQCN is the congestion-control loop that reacts at the source to hold throughput without loss. Tuned defaults for xCCL collectives, with parametric override for custom RDMA stacks.

Load balancing

Adaptive flowlet routing

Static ECMP hashing collides on the few large elephant flows AI collectives produce. DLB re-bins flowlets on local link saturation in sub-millisecond windows, removing the static hashing collisions that hurt symmetric topologies.

The OcNOS implementation

RoCEv2 as OcNOS delivers it

Beyond the lossless controls, OcNOS ships the telemetry, reference designs, and a clean upgrade path that turn a lossless config into an operable fabric.

Telemetry

Per-priority queue stats

gNMI streaming sensors for queue depth, PFC pause counters, ECN-marked packets, and microburst detection, exported on a 10-second sample interval for fabric-wide observability.

Reference designs

Rail-optimized fabrics

Reference designs for rail-aligned and scheduled-fabric topologies, covering 256 to 4,096 GPU clusters on off-the-shelf 400G and 800G open switches. CLI diagnostics verify a known-good lossless config end to end.

Next-generation transport

A clean path to Ultra Ethernet

Build lossless RoCEv2 today and keep an open path to Ultra Ethernet, which adds packet spray and multi-path RDMA to standard Ethernet as UEC NICs ship. One NOS carries both.

Why OcNOS

One NOS image across open hardware

The RoCEv2 toolkit is part of the base OcNOS-DC license, not a set of paid add-ons, and it runs unchanged across a multi-vendor hardware choice.

  • Open hardware choice. Run RoCEv2 on UfiSpace, Edgecore, or Celestica platforms with the same NOS image, so the fabric layer carries no vendor lock-in.
  • Day-one feature parity. Adaptive load-balancing, DCQCN tuning, and ASIC-native telemetry are part of the base OcNOS-DC license, not paid add-ons.
  • Reference designs. Reference configs for popular AI fabric topologies, with the configs and the test results published.
  • Engineering access. The premium support tier includes direct dialog with the OcNOS RoCEv2 team during fabric bring-up.
The IP Infusion view

Standard Ethernet, RDMA performance, open hardware

RoCEv2 lets an AI fabric reuse the Ethernet operations and gear the rest of the data center already runs, and OcNOS is the enabler that makes it lossless on open switches.

Standard Ethernet, RDMA speed

RoCEv2 carries RDMA over routable UDP/IP, so GPU collectives get low-latency, low-CPU data movement without a separate purpose-built fabric.

Open hardware choice

The same lossless config runs across UfiSpace, Edgecore, and Celestica switches at 400G and 800G, keeping the fabric layer multi-vendor.

OcNOS is the enabler

PFC, ECN, DCQCN, DLB, and per-priority telemetry ship as one NOS on open switches, so the complete lossless fabric is a build, not an integration project.

FAQ

RoCEv2, answered

What is RoCEv2?
RoCEv2 (RDMA over Converged Ethernet version 2) carries RDMA traffic over routable UDP/IP networks, letting servers move data directly between memory with very low latency and low CPU overhead. It is widely used for AI clusters and high-speed storage on Ethernet fabrics.
What is the difference between RoCEv2 and RoCEv1?
RoCEv2 runs RDMA over UDP/IP, so it is routable across Layer 3 networks, while RoCEv1 runs directly over Ethernet (Layer 2) and stays within a single broadcast domain. RoCEv2 scales to larger, routed data center fabrics that RoCEv1 cannot reach.
Does RoCEv2 need a lossless network?
RoCEv2 needs a lossless or near-lossless fabric because RDMA performance drops sharply when packets are lost. Operators provide this with PFC for flow control and ECN with DCQCN for congestion control, keeping queues shallow so RDMA flows avoid drops and retransmits.
What UDP port does RoCEv2 use?
RoCEv2 uses destination UDP port 4791, the IANA-reserved port for RoCEv2 traffic. Because RDMA is encapsulated in UDP/IP, the packets are routable and the UDP source port can be varied as a flow identifier to spread traffic across ECMP paths.
How does RoCEv2 compare to InfiniBand?
RoCEv2 delivers RDMA over standard Ethernet and IP, while InfiniBand is a separate purpose-built fabric with its own switches and adapters. RoCEv2 reuses Ethernet operations and gear, which is why many AI and storage networks adopt it instead of a dedicated InfiniBand fabric.

Building or scaling an AI fabric? Get a workload-specific review

Tell us the GPU scale and the collective pattern, and an IP Infusion engineer will size the switch tiers and tune the lossless config with you, or start with a first-pass leaf-spine layout in the AI Fabric Design Suite.