! !-all the SPINE & LEAF adjust the loopback0 IP address for each swДЄt this stage вЂ“ OSPF adjacency should be formed between SPINE and LEAF and SPINE to SPINE switches. !-This is NOT required on a single-POD only solutionДescription вЂњconnected to SPINE switches вЂ“ back-to-back IP FabricвЂќ Ip ospf message-digest-key 0 md5 3 yourOSPFsecretДescription вЂњconnected to SPINE switches вЂ“ IP FabricвЂќ !-SPINE-01 and SPINE-02Дescription вЂњconnected to LEAF switches вЂ“ IP FabricвЂќ Interfaces E1/1 & E1/2 are connected to each other between SPINE and LEAF SPINE to SPINE connection using interfaces E1/10 & E1/11 on both the switches (as per the above network design diagram). I will be using the same вЂњloopback 0вЂќ IP address to all the interconnect interfaces between SPINE & LEAF switches with вЂњip unnumberedвЂќ feature. SPINE-LEAF VXLAN is a вЂњfull meshвЂќ network вЂ“ thus, it is hard to track interface IP addresses if they are configured individually with unique IP address it will be too many IPs and too many IP Subnets!! IP address вЂњunnumberedвЂќ is a nice way to avoid too many IPs and Subnets. Step 2: Setup OSPF routing and Ethernet interfaces IP address Ip router ospf VXLAN-UNDERLAY area 1.1.1.1 Ip router ospf VXLAN-UNDERLAY area 0.0.0.0 Note: you need to configure OSPF routing first.Дescription вЂњUnderlay вЂ“ Interfaces and Router IDвЂќ Also, we will be using this loopback IP address for SPINE-LEAF connections as вЂњip unnumberedвЂќ source IP address. We need вЂњloopback 0вЂќ IP address for router ID both for OSPF and BGP. Step 1: Setup Loopback IPs on all the SPINE and LEAF switches

вЂњroute-distinguisher (RD)вЂќ ID number for this POD-1 is 100 RD ID for POD-2 will be 200.Д«efore we move to the вЂњstep by stepвЂќ configuration вЂ“ enable the following features on the Cisco Nexus switches.ДЇeatures to be enabled on the SPINE switches вЂ“ ! nv overlay evpnДЇeatures to be enabled on the LEAF switches вЂ“ !.

Example вЂ“ VLAN ID 10 mapped to VNI 10010, VLAN ID 20 mapped to 10020.

VNI ID for this POD-1 is 1xxxx VNI ID for POD-2 will be 2xxxx.

However, вЂњSPINE to SPINEвЂќ are optional on a single-pod which can be leverage later on a multi-pod or multi-site EVPN design. NO вЂњLEAF to LEAFвЂќ or вЂњSPINE to SPINEвЂќ required.

Physical layer connectivity are вЂ“ вЂњSPINE to LEAFвЂќ only.

Both SPINE switches are вЂњroute reflectorвЂќ to the LEAF switches.

iBGP peering between вЂњSPINE to LEAFвЂќ вЂ“ mesh iBGP peering topology.

2 x VXLAN NVE VTEP interfaces on LEAF switches (source IP 172.16.0.5 and 172.16.0.6).IP address вЂњunnumberedвЂќ configured on the interfaces connected between SPINE and LEAF.е…ѓ VNI is Type-5 route within EVPN VXLAN вЂ“ which is вЂњIP prefix RouteвЂќ.ДЇollowing is the network topology design diagram I used here in this reference doco. L2 VNI is Type-2 route within EVPN VXLAN вЂ“ which is вЂњMAC with IP advertisement routeвЂќ. This doco describes L2 VNI only вЂ“ there will be another one doco covering е…ѓVNI. As I said earlier вЂ“ if you have ever configured MP-BGP address families, this will be super easy for you.

Example configuration in here are based on Cisco Nexus 9K.Д¬onfigurations are very straight forward and simple.

Mac install ucs platform emulator