Scenario: configure VxLAN both Flood
& Learn and EVPN mode.
You have 1 Spines and 3 Leafs. Leaf-2 and
Leaf-3 are setup as vPC pairs.
Goal: The Goal of the lab is to configure
VXLAN overlay to provide reachability between SW1,SW2 and SW3 using VXLAN
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.
Note: Flood and Learn (F&L)
As the name suggests, F&L used exactly flooding and
learning procedure to learn the end hosts. F&L works in data plane.
“feature nv overlay” and “feature vn-segment-vlan-based” on all Leaf switches
Configure Vlan and associate unique vn-segment
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.
F&L, there is no configuration needed on Spine.
nve interface is configured on all the leafs, you are ready to test the
Verification: you will see (*,G) and (S,G)
entry in mroute table.
Step1: Configure “nv overlay evpn”
on all switches.
Step2: For control plane, configure BGP from
Leaf to Spine with address family l2vpn evpn.
Step3: configure bgp in line with the interface
to use bgp as a protocol for host reachability.
Map the vni to evpn and configure RD/RT. Here we have
an option configure device to automatically generated RD/RT value.
Step5: Configure the spines as
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.