Arista L3 Leaf/Spine Step by Step (2a) - Vxlan Bridging, configuration

Topology:

Configuration:


As long as you can reach the loopback 10 of each VTEPs, the Vxlan bridging configuration is quite straightforward:

wa465.vtep2#sh run int vxlan 1
interface Vxlan1
   vxlan source-interface Loopback10
   vxlan udp-port 4789
   vxlan vlan 2000 vni 2000
   vxlan flood vtep 200.255.200.7 200.255.200.8 200.255.200.9 200.255.200.12 200.255.200.34 200.255.200.56

Basically, you need to specify the following parameters:

• vxlan source interface. (loopback10 in this case)
• vxlan udp port (by default is 4789)
• vlan and vni mapping
• vxlan vtep flood list. 

Please note that you can include the local VTI in the flood list to keep vxlan interface configuration same across the whole domain. 

Ping tests

We can verify the setup by pinging the host address, and GW phy/virtual address. For example, from wa466.host2 (the host behind the bow-tie MLAG), 

ping 20.0.12.250
ping 20.0.12.251

ping 20.0.12.252

ping 20.0.12.253

!

ping 20.0.34.250

ping 20.0.34.251

ping 20.0.34.252

ping 20.0.34.253

!

ping 20.0.56.250

ping 20.0.56.251

ping 20.0.56.252

ping 20.0.56.253
!

ping 20.0.7.250

ping 20.0.7.253

!

ping 20.0.8.250

ping 20.0.8.253

!

ping 20.0.9.250

ping 20.0.9.253 <<<< failed

....

! all successful except 20.0.9.253

--- 20.0.9.250 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 12ms

rtt min/avg/max/mdev = 0.088/0.230/0.577/0.201 ms, ipg/ewma 3.049/0.424 ms

The ping to all host and GW are successful, except the one from wa466.host2 to Vtep3. But the ping from bn303.host3 to vtep3's SVI works. Why?

bn303.spine.host3(s1)(vrf:host3)#ping 20.0.9.253
PING 20.0.9.253 (20.0.9.253) 72(100) bytes of data.
80 bytes from 20.0.9.253: icmp_seq=1 ttl=64 time=0.214 ms
80 bytes from 20.0.9.253: icmp_seq=2 ttl=64 time=0.096 ms
80 bytes from 20.0.9.253: icmp_seq=3 ttl=64 time=0.100 ms
80 bytes from 20.0.9.253: icmp_seq=4 ttl=64 time=0.086 ms
80 bytes from 20.0.9.253: icmp_seq=5 ttl=64 time=0.087 ms

This is because recirculation, which is required for Vxlan routing on T2 platform. We will cover it in next blog. 

Configuration Files