Objectives
The simulator ticks each one as soon as the network meets it.
On L1 and L2, show nve peers and show bgp l2vpn evpn: the remote VTEP is missing.
On L2, send the route-targets: under neighbor 3.3.3.3, address-family l2vpn evpn, add send-community extended.
On L1, import the VNI’s own route-target: under evpn / vni 10010 l2 replace route-target import 65000:99 with route-target import auto.
Ping PC2 (192.168.10.20) from PC1.
Before you start
A BGP session that is Established is not enough: without send-community extended the route-targets are stripped and no VTEP imports the route; with the wrong import route-target the route is received but ignored. Route-target auto is ASN:VNI (65000:10010).
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.
