Skip to content
nodeza.learn

Segment Routing over IPv6

SRv6 from RFC 8402/8754/8986 up through RFC 9800 compression, built and broken in containerlab with Linux seg6local and FRR, then mapped onto what really ships: Cumulus Linux 5.14+ uN/uA on Spectrum-4, DOCA Flow SRH push on BlueField-3/ConnectX, community SONiC HLDs, and a Dell Enterprise SONiC / OS10 feature matrix that publishes no SRv6 at all. Twelve lessons, three modules, every lab in a no-hardware (containerlab / NVIDIA Air) and a Dell-lab BlueField-3 variant, ending in the FAE conversation a Dell OEM account will actually have.

3 modules. Dots: grey not started, blue in progress, green complete with quiz ≥ 80%, amber complete but below 80%. Each module ends in a checkpoint that unlocks the next.

Segment Routing over IPv6

0%

0 of 12 cases closed

Foundations

Implementations

FAE scenarios

Foundations: how SRv6 encodes a path

Read an SRv6 packet off the wire byte by byte, explain a SID as LOC:FUNCT:ARG plus a behavior, and state exactly what became standard in 2024-2025 (RFC 9602, RFC 9800, RFC 9855) versus what is still vendor vocabulary.

  1. 1.1 Source routing, segments, and the two data planesThirty-one boxes, one budget line
  2. 1.2 The SRH on the wirePing is fine, the backups are not
  3. 1.3 SIDs as instructions: LOC:FUNCT:ARG and the behavior zooThe config that says the kernel is broken
  4. 1.4 Compression: RFC 9800, NEXT-C-SID, and what "uSID" really meansYour slide says 96 bytes and theirs says 40
  5. Checkpoint

Implementations: Linux, FRR, Spectrum-4, BlueField

Build a working SRv6 domain in containerlab with Linux seg6local and FRR, and state precisely which behaviors NVIDIA's switch and NIC products implement - and which they do not.

  1. 2.1 SRv6 in the Linux kernel: seg6 and seg6localThe route is there and nothing moves
  2. 2.2 FRR: locators, the SID Manager, IS-IS SRv6 and TI-LFAZero protected, and a draft that stopped being one
  3. 2.3 NVIDIA switching: uN and uA on Spectrum-4The slide that says SRv6 replaces our MPLS WAN
  4. 2.4 NVIDIA NIC and DPU: SRH push with DOCA FlowTwo cards, one binary
  5. Checkpoint

Services, operations, and the Dell OEM conversation

Deliver a defensible SRv6 answer to a Dell OEM customer: build BGP services over SRv6, diagnose a broken domain from first principles, and separate what is published from what is unverified before you say it out loud.

  1. 3.1 L3VPN and EVPN services over SRv6Every VPN prefix went invalid at 02:00
  2. 3.2 Ping the SID: OAM and the five failures that actually happenThe SID that answered with an error
  3. 3.3 Who actually ships SRv6: the Dell and NVIDIA support matrixDoes Dell do SRv6? One word, they said
  4. 3.4 Design and defend an SRv6 PoC for a Dell OEM accountTwo questions before anyone touches the whiteboard
  5. Checkpoint