The document describes how to configure a VXLAN network using Cumulus switches. Key steps include: 1. Configuring OSPF routing between the Cumulus switches to provide L3 connectivity. 2. Creating bridges on each Cumulus switch and connecting them to virtual VTEP interfaces to encapsulate L2 traffic in VXLAN tunnels between the switches. 3. Configuring IP addresses on router interfaces and ARP entries to allow L2 communication between routers connected to each switch via the VXLAN.

1. 1
Configuring a VXLAN with Cumulus
This is the physical topology created on GNS3 to realize a VXLAN TUNNEL
SWITCH 1/2 are Cumulus Vx version 2.5.3 running in virtual Box each with 5 interfaces Intel PRO/1000 MT
R1/2/3 are router Cisco version c7200 working as workstation each of them has been configured with IP

2. Configuring a VXLAN with Cumulus
2
The image below is the logical topology resulting from physical

3. Configuring a VXLAN with Cumulus
3
Main components of logical topology are:
• A layer 3 connection between SWITCH1 and SWITCH2 realized with OSPF protocol working on
Cumulus
• two bridge BR created on SWITCH1 and SWITCH2 connected to R1 R2 and R3 by swp2 swp3
• tunnel VXLAN create between the two bridge BR using VTEP( VXLAN Tunnel Endpoint) interface
for frame encapsulation
Let's see how work it out step by step
STEP1 - Creating layer 3 infrastructure
On SWITCH1 we're going to create a loopback interface and assign an IP address and assign an IP address
to interface swp1
auto lo
iface lo inet loopback
address 172.10.1.1
netmask 255.255.255.255

4. Configuring a VXLAN with Cumulus
4
auto swp1
iface swp1 inet static
address 192.168.168.1
netmask 255.255.255.0
After that we need to enable ospf protocol setting zebra = yes and ospf = yes in file /etc/quagga/daemons
cumulus@SWITCH1$ cat /etc/quagga/daemons
zebra=yes
bgpd=no
ospfd=yes
ospf6d=no
ripd=no
ripngd=no
isisd=no
babeld=no
configuring loopback interface in area 1 and swp1 in area 0 backbone
router ospf
network 172.10.1.0/24 area 0.0.0.1
network 192.168.168.0/24 area 0.0.0.0
on SWITCH2
auto lo
iface lo inet loopback
address 172.20.1.1
netmask 255.255.255.255
auto swp1
iface swp1 inet static
address 192.168.168.2
netmask 255.255.255.0
configuring loopback interface in area 2 and swp1 in area 0 backbone
router ospf
network 172.20.1.0/24 area 0.0.0.2
network 192.168.168.0/24 area 0.0.0.0
In SWITCH1 there will be a rote to 172.20.1.1
cumulus@SWITCH1$ sudo vtysh
sudo: unable to resolve host SWITCH1
[sudo] password for cumulus:

5. Configuring a VXLAN with Cumulus
5
Hello, this is Quagga (version 0.99.23.1).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
SWITCH1# sh ip ro
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, A - Babel, T - Table,
> - selected route, * - FIB route
K>* 0.0.0.0/0 via 10.0.2.2, eth0
C>* 10.0.2.0/24 is directly connected, eth0
O 172.10.1.1/32 [110/10] is directly connected, lo, 04:26:32
C>* 172.10.1.1/32 is directly connected, lo
O>* 172.20.1.1/32 [110/20] via 192.168.168.2, swp1, 04:26:18
O 192.168.168.0/24 [110/10] is directly connected, swp1, 04:26:32
C>* 192.168.168.0/24 is directly connected, swp1
In SWITCH2 there will be a rote to 172.10.1.1
cumulus@SWITCH2$ sudo vtysh
sudo: unable to resolve host SWITCH2
[sudo] password for cumulus:
Hello, this is Quagga (version 0.99.23.1).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
SWITCH2# sh ip ro
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, A - Babel, T - Table,
> - selected route, * - FIB route
K>* 0.0.0.0/0 via 10.0.2.2, eth0
C>* 10.0.2.0/24 is directly connected, eth0
O>* 172.10.1.1/32 [110/20] via 192.168.168.1, swp1, 04:24:45
O 172.20.1.1/32 [110/10] is directly connected, lo, 04:51:40
C>* 172.20.1.1/32 is directly connected, lo
O 192.168.168.0/24 [110/10] is directly connected, swp1, 04:51:40
C>* 192.168.168.0/24 is directly connected, swp1

6. Configuring a VXLAN with Cumulus
6
SWITCH1# ping 172.20.1.1
PING 172.20.1.1 (172.20.1.1) 56(84) bytes of data.
64 bytes from 172.20.1.1: icmp_req=1 ttl=64 time=0.571 ms
64 bytes from 172.20.1.1: icmp_req=2 ttl=64 time=0.465 ms
^C
When a layer3 infrastructure is ready we can configure Cumulus Switch
On SWITCH1 we're going to create a bridge br with swp2 and swp3 and vetp1000
Vtep1000 is an interface which permits to reach IP 10.1.1.3 configured on fa 0/0 on R3 ( mac address
ca:03:5d:5c:00:00 )
Layer 2 Traffic to R3 is incapsuled in layer3 packet with source IP 172.10.1.1 dest IP 172.20.1.1 and VXLAN
network indentifier 1000
auto vtep1000
iface vtep1000 inet static
vxlan-id 1000
vxlan-local-tunnelip 172.10.1.1
auto br
iface br
bridge-ports swp2 swp3 vtep1000
post-up bridge fdb add ca:03:5d:5c:00:00 dev vtep1000 dst 172.20.1.1 vni 1000
On SWITCH2 we're going to create a bridge br with swp2 and swp3 and vetp1000
Vtep1000 is an interface which permits to reach IP 10.1.1.1 and 10.1.1.2 configured on fa 0/0 of R1 and R2
( respectively mac address ca:01:45:0c:00:00 and ca:01:4f:0c:00:00 )
Layer 2 Traffic to R1 and R2 is incapsuled in layer3 packet with source IP 172.20.1.1 dest IP 172.10.1.1 and
VXLAN network indentifier 1000
auto vtep1000
iface vtep1000 inet static
vxlan-id 1000
vxlan-local-tunnelip 172.20.1.1
auto br
iface br

7. Configuring a VXLAN with Cumulus
7
bridge-ports swp2 swp3 vtep1000
post-up bridge fdb add ca:01:45:0c:00:00 dev vtep1000 dst 172.10.1.1 vni 1000
post-up bridge fdb add ca:02:4f:08:00:00 dev vtep1000 dst 172.10.1.1 vni 1000
On R1,R2 and R3 we need to configure IP
! on R1
interface FastEthernet0/0
ip address 10.1.1.1 255.255.255.0
! onR2
interface FastEthernet0/0
ip address 10.1.1.2 255.255.255.0
!R3
interface FastEthernet0/0
ip address 10.1.1.3 255.255.255.0
and arp resolution
!R1 and R2
arp 10.1.1.3 ca03.5d5c.0000 ARPA
!R3
arp 10.1.1.1 ca01.450c.0000 ARPA
arp 10.1.1.2 ca02.4f08.0000 ARPA
In the end we can test our infrastructure with ping from R2 to R3
As we can see l2 frame source mac ca02.4f08.0000 dest mac ca03.5d5c.0000 is encapsulate in l3 packet
source IP 172.10.1.1 dest IP 172.20.1.1

8. Configuring a VXLAN with Cumulus
8