VxLAN Configuration || Vxlan flood & Learn || BGP EVPN on NX-OS

VxLAN Prerequisites:

Prerequisites are hardware/Software Specific:

For Nexus 5600 as hardware VTEP 

Set switching mode to store-and-forward

• h/w Ethernet store-and-forward-switching
• Requires a reboot

Establish IP unicast reachability between VTEPs

Establish PIM BIDIR reachability RPs for redundancy

Enable features:

1. feature vn-segment-vlan-based (VNI to VLAN mapping)
2. feature nv overlay (nve interface ) 

Bidirectional PIM is scaling technique of multicast control plan do not install (S,G) entry, only we have (*,G) & all traffic collected by RP, in BIDIR PIM RP is in data plan .

example: conf)# ip pim rp-address 1.1.1.72 group-list 224.0.0.0/4 bidir ; in all the devices

Note: Vxlan & Fabricpath are mutually exclusive , asic will not take both 

VxLAN Flood & Learn Config Steps 

1. Map vlan to Vxlan (vn-segment under vlan config more ; vlan 10 ; vn-segment 11111
2. Create Network Virtualization Edge (NVE) interface (interface nve0)
3. Specify VTEP Source ( source interface loopback 0)
4. Specify VNI membership ( member vni [vnid] ; member vni 11111
5. Specify multicast group for BUM replication ( mcast-group [group] ( 228.9.10.11 ) 

VxLAN Flood & Learn Verification 

• show interface nve id 
• show platform fwm info nve peer [all]
• show mac address-table
• show nve peer
• show nve vni
• show platform fwm info nve vni

Config Summary : 

feature nv overlay 

feature vn-segment-vlan-based

!

vlan 10

   vn-segment 11111

!

interface nve1 ; no shut ; source-interface loopback 0; member vni 11111; mcast-group 228.9.10.11

!

show ip route | in /32

Implementing VxLAN BGP EVPN on NX-OS

Note: We make sure unicast / multicast control plane is working otherwise arp will not work

Prerequisites anre hw/sw specific 

• For Nexus 5600 as h/w VTEP
• set switching mode to store-and-forward (hw ethernet store-and-forward)
• requires reboot
• Establish IP unicast reachability between VTEPs
• Establish PIM BIDIR reachability between VTEPs (Spines can be phantom RPs for redundancy)
• features to be enabled:  

                           install feature-set virtualization

                           install feature-set fabric

                           feature-set fabric

                           feature fabric forwarding

                           nv overlay evpn

                           feature nv overlay

                           feature vn-segment-vlan-based 

-----------  Config 

• Map vlan to vxlan (vn-segment under vlan config mode )
• Create n/w virtualization edge (NVE) (interface nve 0 )
• Specify VTEP source ( Source interface loopback 0 ) 
• Specify VNI Membership ( member vni [vnid] )
• Specify multicast group for BUM replication ( mcast-group [group] )
• Specify BGP as control plane protocol ( host-reachability protocol bgp )
• Establish BGP EVPN Peering ( address-family l2vpn evpn )
• extended community required 

SPINE SIDE CONFIGURATION : 

feature bgp ; router bgp 1 ; nei 1.1.1.71/32 ; remote-as 1 ; update-source lo0

address-family l2vpn evpn ; send-community extended ; route-reflector-client 

LEAF SIDE CONFIGURATION : 

feature bgp ; router bgp 1 ; nei 1.1.1.51/32 ; remot-as 1 ; update-source lo0

address-family l2vpn evpn ; send-community extended 

Verification : 

show interface nve id

show platform fwm info nve peer [all]

show mac address-table

show nve peer

show nve vni

show platform fwm info nve vni

show bgp l2vpn evpn summary 

show bgp l2vpn evpn

show bgp l2vpn evpn neighbor [neighbor] advertised-routes

!

evpn 

vni 11111  l2 

  rd auto

   route-target input auto

   route-target export auto