Parent folderOpen Confluence

RWS Architecture article

Cisco NX-OS EVPN ESI multi-homing (Summary)

Summary of Cisco NX-OS EVPN Ethernet Segment Identifier (ESI) multi-homing behavior used to define production baseline controls for multi-homed tenant attachment in EVPN/VXLAN fabr

  1. Typesource
  2. Statusactive
  3. Domainnetwork
On this page
  1. Source - Cisco NX-OS EVPN ESI multi-homing
  2. Overview
  3. Context
  4. Decisions
  5. Current State
  6. References
  7. Future Work
  8. Related

Source - Cisco NX-OS EVPN ESI multi-homing

Overview

Summary of Cisco NX-OS EVPN Ethernet Segment Identifier (ESI) multi-homing behavior used to define production baseline controls for multi-homed tenant attachment in EVPN/VXLAN fabrics.

Context

This source is used for target-lane failover, convergence, and fault-tolerance behavior where EVPN ESI multi-homing is selected as baseline instead of vPC-first attachment patterns.

Decisions

Current State

  • ESI multi-homing controls include RT1 signaling, Type-2 re-origination, DF election, and delay-restore timers.
  • Next-hop behavior follows active-peer count: VIP with two or more active ESI peers, PIP when one peer remains.
  • L2FRR protects traffic during convergence; in PIP mode, FRR anycast source IP is mandatory, shared within the ESI cluster where required, and unique across the fabric.
  • Core-link tracking is required so ES state tracks upstream availability.
  • EAD-EVI is disabled by default in NX-OS implementations where Type-2 re-origination already provides path visibility.
  • Platform and release limits must be enforced in profile policy; for validated NX-OS 10.6(x) profiles this includes up to 4-way ESI and documented topology/mode constraints.
  • vPC and ESI coexistence is constrained at node role level; a VTEP operates in either vPC-VTEP or ESI-VTEP mode for the scoped design.

References

Future Work

  • Pin ESI behavior and limits to the exact NX-OS train used in production evidence bundles.
  • Add explicit failover test cases for PIP to VIP and VIP to PIP transitions in standard validation gates.

Related