Objectives
The simulator ticks each one as soon as the network meets it.
On the SONiC leaf L1: advertise-all-vni, and interface vxlan vtep1 with source-ip 10.10.10.1 and map vni 10010 vlan 10.
On the OS10 leaf L2: nve with source-interface loopback1, virtual-network 10 with vxlan-vni 10010, VLAN 10 bound to it, and evpn auto-evi.
L1 has a tunnel to 10.10.10.2, and L2 a tunnel to 10.10.10.1.
Ping PC2 (192.168.10.20) from PC1.
Before you start
Automatic route-targets contain the ASN, which differs between these leaves. This model matches them on the VNI, as Dell OSes can. Between other vendors, write the route-target out. Real interworking must be tested on your releases.
Concept
BGP EVPN: a control plane for VXLAN
BGP EVPN replaces flood-and-learn with BGP routes in the L2VPN EVPN address family. Each VTEP advertises an inclusive-multicast route (type 3) per VNI, so the others know to replicate to it, and a MAC route (type 2) per local host, so remote MACs are known before any traffic flows. A spine is usually the iBGP route reflector.
Concept
A leaf-spine fabric on Dell switches
Every leaf connects to every spine, and no leaf connects to another leaf, so any two leaves are two hops apart over several equal paths. eBGP routes between loopbacks form the underlay, usually with one ASN per leaf pair. EVPN then runs on the same BGP sessions: VTEPs announce their VNIs and hosts, and tunnels form from those routes. SONiC can peer without link addresses: ipv6 enable and neighbor interface are enough.
