Configuring VXLAN EVPN Multihoming
The receipt of type-1 and type-2 routes with valid ESI and the path-list resolution are not tied to the evpn esi
multihoming command. If the switch receives MAC/MAC-IP routes with valid ESI and the command is not
enabled, the ES based path resolution logic still applies to these remote routes. This is required for
interoperability between the vPC enabled switches and the ESI enabled switches.
Complete the following steps to configure EVPN multihoming:
Before You Begin
VXLAN should be configured with BGP-EVPN before enabling EVPN ESI multihoming.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
VXLAN EVPN Multihoming Configuration Examples
See the sample VXLAN EVPN multihoming configuration on the switches:
Command or Action
evpn esi multihoming
address-family l2vpn evpn
maximum-paths <>maximum-paths
ibgp <>
Example:
address-family l2vpn evpn
maximum-paths 64
maximum-paths ibgp 64
evpn multihoming core-tracking
interface port-channel
Ethernet-segment <>System-mac <>
Example:
ethernet-segment 11
system-mac 0000.0000.0011
hardware access-list tcam region
vpc-convergence 256
Example:
hardware access-list tcam region
vpc-convergence 256
Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide, Release 7.x
VXLAN EVPN Multihoming Configuration Examples
Purpose
Enables EVPN multihoming globally.
Enables BGP maximum-path to enable ECMP for the MAC
routes. Otherwise, the MAC routes have only 1 VTEP as
the next-hop. This configuration is needed under BGP in
Global level.
Enables EVPN multihoming core-links. It tracks the uplink
interfaces towards the core. If all uplinks are down, the
local ES based the POs is shut down/suspended. This is
mainly used to avoid black-holing South-to-North traffic
when no uplinks are available.
Configures the local Ethernet Segment ID. The ES ID has
to match on VTEPs where the PO is multihomed. The
Ethernet Segment ID should be unique per PO.
Configures the local system-mac ID that has to match on
the VTEPs where the PO is multihomed. The system-mac
address can be shared across multiple POs.
Configures the TCAM. This command is used to configure
the split horizon ACLs in the hardware. This command
avoids BUM traffic duplication on the shared ES POs.
105