Users Guide

Table Of Contents
*>r Route distinguisher: 3.3.3.3:65002 VNI:65002
[5]:[0]:[24]:[12.12.12.0]:[0.0.0.0]/224 3.3.3.3 0 100 0 100 101 ?
*>r Route distinguisher: 4.4.4.4:101 VNI:101
[2]:[0]:[48]:[14:18:77:25:6f:4d]:[32]:[11.11.11.2]/224
4.4.4.4 0 100 32768 ?
*>r Route distinguisher: 3.3.3.3:102 VNI:102
[2]:[0]:[48]:[14:18:77:25:8f:6d]:[32]:[12.12.12.1]/224
3.3.3.3 0 100 0 100 101 ?
*> Route distinguisher: 3.3.3.3:101
[3]:[0]:[32]:[3.3.3.3]/152 3.3.3.3 0 100 0 100 101 ?
*>r Route distinguisher: 4.4.4.4:101
[3]:[0]:[32]:[4.4.4.4]/152 4.4.4.4 0 100 32768 ?
*>r Route distinguisher: 4.4.4.4:102
[3]:[0]:[32]:[4.4.4.4]/152 4.4.4.4 0 100 32768 ?
OS10# show ip route vrf blue
Codes: C - connected
S - static
B - BGP, IN - internal BGP, EX - external BGP, EV - EVPN BGP
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,
E2 - OSPF external type 2, * - candidate default,
+ - summary route, > - non-active route
Gateway of last resort is not set
Destination Gateway Dist/Metric Last Change
------------------------------------------------------------
C 11.11.11.0/24 via 11.11.11.1 0/0 1 day 02:54:39
virtual-network101
B EV 15.15.15.2/32 via 4.4.4.4 200/0 1 day 02:09:19
B EV 15.15.15.0/24 via 4.4.4.4 200/0 1 day 02:09:19
B EV 11.11.11.2/32 via 4.4.4.4 100/0 1 day 05:10:11
B EV 12.12.12.0/24 via 3.3.3.3 100/0 1 day 00:10:01
BGP EVPN with VLT
OS10 supports BGP EVPN operation between VLT peers that you configure as VTEPs. For more information about
configurations and best practices to set up VLT for VXLAN, see Configure VXLAN Configure VLT. This information also
applies to BGP EVPN for VXLAN.
Dell EMC recommends configuring iBGP peering for the IPv4 address family between the VTEPs in a VLT pair on a dedicated
L3 VLAN that is used when connectivity to the underlay L3 network is lost. It is NOT required to enable the EVPN address
family on the iBGP peering session between the VTEPs in a VLT pair because EVPN peering to the spine switch is performed on
Loopback interfaces.
Both VTEPs in a VLT pair advertise identical EVPN routes, which provides redundancy if one of the VTEP peers fails. To set up
redundant EVPN route advertisement, configure the same EVI, RD, and RT values for each VNI on both VTEPs in a VLT pair,
including:
In auto-EVI mode, this identical configuration is automatically ensured if the VNID-to-VNI association is the same on both
VTEP peers.
In manual EVI mode, you must configure the same EVI-to-VNID association on both VTEP peers.
In manual EVI mode, you must configure the same RD and RT values on both VTEP peers.
In an EVPN configuration, increase the VLT delay-restore timer to allow for BGP EVPN adjacency to establish and for the
remote MAC and neighbor entries to download by EVPN and install in the dataplane. The VLT delay-restore determines the
amount of time the VLT LAGs are kept operationally down at bootup to allow the dataplane to set up and forward traffic,
resulting in minimal traffic loss as the VLT peer node boots up and joins the VLT domain.
For a sample BGP EVPN VLT configuration, see Example: VXLAN with BGP EVPN.
1166
VXLAN