VXLAN LAB on EVE-NG Platform

Scenario: configure VxLAN both Flood & Learn and EVPN mode.

Premise:

You have 1 Spines and 3 Leafs. Leaf-2 and Leaf-3 are setup as vPC pairs.

• The host port on Leaf-1 is in VLAN 10 and on Leaf-2 in VLAN 10 & 20
• vPC pair has a L2 switch connected to its member port and is passing all Vlans 10, 20 , 30.

Goal: The Goal of the lab is to configure VXLAN overlay to provide reachability between SW1,SW2 and SW3 using VXLAN

STEP1: Configure basic IP reachability between Leaf and Spine switches using OSPF routing protocol.

STEP2: Configure multicast between Leaf and Spine. Best practice is to use bidirectional mode. We can configure anycast or phantom RP for Spine redundancy. Make sure to allow the correct group address to be used for VxLAN.

As the name suggests, F&L used exactly flooding and learning procedure to learn the end hosts. F&L works in data plane.

Step3:  Configure “feature nv overlay” and “feature vn-segment-vlan-based” on all Leaf switches

Step4: Configure Vlan and associate unique vn-segment per vlan.

Step5: Configure “nve” interface with source interface of Loopback 0. Associate vni to nve interface and assign multicast group of which vni should be part of.

Step6: Configure a common secondary IP on loopback for vpc peers. The nve peering will be done with secondary IP only.

Step7: Configure VPC nve vlan on both vpc peers and SVI with ospf on it. Make sure to have increased cost on this link, so that it can’t be used as transit for all traffic.

Verification: Once nve interface is configured on all the leafs, you are ready to test the connectivity.

Verification: you will see (*,G) and (S,G) entry in mroute table.

BGP EVPN:

Step1: Configure “nv overlay evpn” on all switches.

Step2: For control plane, configure BGP from Leaf to Spine with address family l2vpn evpn.

Verification:

Step3: configure bgp in line with the interface to use bgp as a protocol for host reachability.

Step4:  Map the vni to evpn and configure RD/RT. Here we have an option configure device to automatically generated RD/RT value.

Verification:

Step5: Configure the spines as route-reflector Client

This is data driven protocol, which means you will see nve peer and mac address only when there is an active traffic.

Once the address is learned on leaf, BGP control plane will advertise the same to remote peers.