Skip to content

EVPN

EVPN (Ethernet VPN) provides a control-plane solution for VXLAN overlay networks on NX-OS, enabling scalable Layer 2 and Layer 3 connectivity across data center fabrics through BGP-based MAC and IP route advertisement. It manages per-VNI configuration including route distinguisher assignment, route target import/export policies for both auto-derived and explicitly defined targets, and table map filtering for route policy control. EVPN also supports multisite border gateway configuration for interconnecting multiple VXLAN EVPN fabrics, including site ID assignment, PIP advertisement, delay-restore timers, DF election timers, and per-site split-horizon control. EVPN is essential for modern VXLAN fabric deployments, enabling distributed anycast gateway, ARP suppression, and seamless workload mobility across leaf switches.

Diagram
NameTypeConstraintMandatoryDefault Value
evpnClass[evpn]No

NameTypeConstraintMandatoryDefault Value
multisite_border_gatewayClass[multisite_border_gateway]No
vnisList[vnis]No

multisite_border_gateway (nxos.devices.configuration.evpn)

Section titled “multisite_border_gateway (nxos.devices.configuration.evpn)”
NameTypeConstraintMandatoryDefault Value
site_idIntegermin: 1, max: 281474976710655Yes
dci_advertise_pipBooleantrue, falseNo
delay_restore_timeIntegermin: 30, max: 1000No
df_election_timeNumbermin: 1, max: 1000No
fabric_advertise_pipBooleantrue, falseNo
split_horizon_per_siteBooleantrue, falseNo

NameTypeConstraintMandatoryDefault Value
vniIntegermin: 1, max: 16777215Yes
rdStringNo
route_target_both_autoBooleantrue, falseNo
route_target_importsListStringNo
route_target_exportsListStringNo
table_mapStringNo
table_map_filterBooleantrue, falseNo

Example 1: L2 VNI with auto route targets for VXLAN bridging

nxos:
devices:
- name: LEAF1
configuration:
evpn:
vnis:
- vni: 10101
rd: 10.1.100.3:10101
route_target_both_auto: true
- vni: 10102
rd: 10.1.100.3:10102
route_target_both_auto: true

Example 2: L2 and L3 VNIs with explicit route targets for multi-tenant fabric

nxos:
devices:
- name: LEAF1
configuration:
evpn:
vnis:
# L2 VNIs for bridged traffic
- vni: 10101
rd: 10.1.100.3:10101
route_target_imports:
- "65000:10101"
route_target_exports:
- "65000:10101"
- vni: 10102
rd: 10.1.100.3:10102
route_target_imports:
- "65000:10102"
route_target_exports:
- "65000:10102"
# L3 VNIs for routed traffic per VRF
- vni: 11010
rd: 10.1.100.3:11010
route_target_imports:
- "65000:11010"
route_target_exports:
- "65000:11010"
- vni: 11020
rd: 10.1.100.3:11020
route_target_imports:
- "65000:11020"
route_target_exports:
- "65000:11020"

Example 3: EVPN VNIs with shared route targets for cross-leaf L2 stretching and table map filtering

nxos:
devices:
- name: LEAF2
configuration:
evpn:
vnis:
- vni: 10101
rd: 10.1.100.4:10101
route_target_both_auto: true
table_map: EVPN-TABLE-MAP
table_map_filter: true
- vni: 10102
rd: 10.1.100.4:10102
route_target_both_auto: true
- vni: 11010
rd: 10.1.100.4:11010
route_target_both_auto: true
- vni: 11020
rd: 10.1.100.4:11020
route_target_both_auto: true

Example 4: EVPN multisite border gateway for DCI with PIP advertisement and split-horizon

nxos:
devices:
- name: BORDER-GW1
configuration:
evpn:
multisite_border_gateway:
site_id: 1
dci_advertise_pip: true
delay_restore_time: 300
df_election_time: "2.0"
fabric_advertise_pip: true
split_horizon_per_site: true
vnis:
- vni: 10101
rd: 10.1.100.5:10101
route_target_both_auto: true
- vni: 11010
rd: 10.1.100.5:11010
route_target_both_auto: true

EVPN (Ethernet VPN) provides a control-plane solution for VXLAN overlay networks on NX-OS, enabling scalable Layer 2 and Layer 3 connectivity across data center fabrics through BGP-based MAC and IP route advertisement. It manages per-VNI configuration including route distinguisher assignment, route target import/export policies for both auto-derived and explicitly defined targets, and table map filtering for route policy control. EVPN is essential for modern VXLAN fabric deployments, enabling distributed anycast gateway, ARP suppression, and seamless workload mobility across leaf switches.

Diagram
NameTypeConstraintMandatoryDefault Value
evpnClass[evpn]No

NameTypeConstraintMandatoryDefault Value
vnisList[vnis]No

NameTypeConstraintMandatoryDefault Value
vniIntegerYes
rdStringNo
route_target_both_autoBooleantrue, falseNo
route_target_importsListStringNo
route_target_exportsListStringNo
table_mapStringNo
table_map_filterBooleantrue, falseNo

Example 1: L2 VNI with auto route targets for VXLAN bridging

nxos:
devices:
- name: LEAF1
configuration:
evpn:
vnis:
- vni: 10101
rd: 10.1.100.3:10101
route_target_both_auto: true
- vni: 10102
rd: 10.1.100.3:10102
route_target_both_auto: true

Example 2: L2 and L3 VNIs with explicit route targets for multi-tenant fabric

nxos:
devices:
- name: LEAF1
configuration:
evpn:
vnis:
# L2 VNIs for bridged traffic
- vni: 10101
rd: 10.1.100.3:10101
route_target_imports:
- "65000:10101"
route_target_exports:
- "65000:10101"
- vni: 10102
rd: 10.1.100.3:10102
route_target_imports:
- "65000:10102"
route_target_exports:
- "65000:10102"
# L3 VNIs for routed traffic per VRF
- vni: 11010
rd: 10.1.100.3:11010
route_target_imports:
- "65000:11010"
route_target_exports:
- "65000:11010"
- vni: 11020
rd: 10.1.100.3:11020
route_target_imports:
- "65000:11020"
route_target_exports:
- "65000:11020"

Example 3: EVPN VNIs with shared route targets for cross-leaf L2 stretching and table map filtering

nxos:
devices:
- name: LEAF2
configuration:
evpn:
vnis:
- vni: 10101
rd: 10.1.100.4:10101
route_target_both_auto: true
table_map: EVPN-TABLE-MAP
table_map_filter: true
- vni: 10102
rd: 10.1.100.4:10102
route_target_both_auto: true
- vni: 11010
rd: 10.1.100.4:11010
route_target_both_auto: true
- vni: 11020
rd: 10.1.100.4:11020
route_target_both_auto: true