Hi Donald,
I have an L2 working fine right now between two neighbors.
As soon as I add a veth interface into the same bridge where the Vxlan interface is connected, that MAC address is advertised to the other neighbor without any problem.
Also I see the entry in "bridge fdb show" command to send the broadcasts to the other neighbor using its VTEP IP:
00:00:00:00:00:00 dev vxlan200 dst 198.18.0.12 self permanent
198.18.0.12 is the neighbor IP.
One router has 100.64.0.10 in the bridge and the neighbor has 100.64.0.11 in its bridge, they can communicate fine over VxLAN using the information provided by EVPN.
I am adding an static entry in the ARP table of 100.64.0.10 but this entry is not being propagated over EVPN
# arp -i br100 -s 100.64.0.2 62:e1:e3:18:24:f8 pub
The output in EVPN is not reflecting this new ARP entry:
# show evpn arp-cache vni 100
Number of ARPs (local and remote) known for this VNI: 3
IP Type MAC Remote VTEP
100.64.0.10 local 62:e1:e3:18:24:f8
fe80::60e1:e3ff:fe18:24f8 local 62:e1:e3:18:24:f8
100.64.0.11 local 22:b9:50:4c:b8:9c
And when I check the neighbor to see why it cannot ping this is showing up:
# arp -n
Address HWtype HWaddress Flags Mask Iface
100.64.0.2 (incomplete) br100
100.64.0.10 ether 62:e1:e3:18:24:f8 C br100
If I manually add ARP entry into the neighbor(100.64.0.11) table it works.
Not sure if this answer this question Donald, this is pretty much where I am right now.