Skip to content

doc: Add L3 Multi-Homing with Backup Path HLD for IP Data Centers#2332

Open
pbrisset wants to merge 1 commit into
sonic-net:masterfrom
pbrisset:sonic-l3mh-hld-ipdc
Open

doc: Add L3 Multi-Homing with Backup Path HLD for IP Data Centers#2332
pbrisset wants to merge 1 commit into
sonic-net:masterfrom
pbrisset:sonic-l3mh-hld-ipdc

Conversation

@pbrisset
Copy link
Copy Markdown
Contributor

Summary

This HLD introduces Layer 3 Multi-Homing (L3MH) support with automatic backup path failover for IP-only data center deployments in SONiC. This feature enables EVPN-VXLAN multi-homing without requiring Layer 2 VNI (L2VNI) dependency, making it ideal for modern spine-leaf IP fabrics.

Key Features

  • Global L3VNI in Default VRF: Supports VRF-less deployments with a global L3VNI for VXLAN encapsulation
  • RT-2 Neighbor Synchronization: Synchronizes remote neighbors via EVPN Route Type 2 with Label-1=0 (L3-only mode)
  • Backup Nexthop Groups: Automatic failover using SAI backup nexthop groups with sub-second convergence
  • All-Active Multi-Homing: All VTEPs in an Ethernet Segment forward traffic simultaneously
  • Three-Path Architecture: Separates kernel neighbor, FPM route, and ASIC port state for robust failure detection
  • NO_HOST_ROUTE Flag: Prevents duplicate /32 route creation while maintaining neighbor entries

Architecture Highlights

  1. New Components:

    • vxlanmgr: Global L3VNI configuration manager
    • fpmsyncd_nhg: Backup nexthop group manager
    • neighsyncd_rt2: EVPN RT-2 remote neighbor synchronization
  2. Database Schema:

    • New VXLAN_GLOBAL table in CONFIG_DB
    • New BACKUP_NEXTHOP_GROUP_TABLE in APPL_DB
    • Enhanced NEIGH_TABLE with rt2_type metadata
  3. Dummy VLAN/SVI: Uses a reserved VLAN (e.g., Vlan4094) as the decapsulation context for the global L3VNI

Use Case

Ideal for IP-only data centers where:

  • Hosts are dual-homed to multiple ToRs for redundancy
  • Layer 2 bridging is not required (pure L3 design)
  • Sub-second convergence is critical for application availability
  • Simplified operations without VRF overhead

Compatibility

  • Backward compatible: Does not affect existing L2VNI-based EVPN or VRF-based L3VNI deployments
  • FRR changes: Requires corresponding FRR HLD (documented separately)

References

  • Related work: EVPN-VXLAN Multi-Homing HLD
  • RFC 7432: BGP MPLS-Based Ethernet VPN
  • RFC 8365: EVPN Overlay for VXLAN

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@pbrisset pbrisset force-pushed the sonic-l3mh-hld-ipdc branch from 1af656c to 1273e06 Compare May 13, 2026 20:06
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@pbrisset pbrisset force-pushed the sonic-l3mh-hld-ipdc branch from 1273e06 to bab9bac Compare May 13, 2026 20:08
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

This adds a High-Level Design document for EVPN L3 Multihoming backup
tunnel support using IP Directed Control (IPDC) approach in SONiC.

Signed-off-by: pbrisset <pbrisset@users.noreply.github.com>
@pbrisset pbrisset force-pushed the sonic-l3mh-hld-ipdc branch from bab9bac to bcb0552 Compare May 13, 2026 20:10
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants