EVPN-VXLAN Config Build From Scratch 1

🏗 How to build an EVPN-VXLAN from scratch using Aruba AOS-CX devices.
🦴This is a near live presentation over two parts that takes a bare bones config and shows you the configuration of an EVPN-VXLAN network for inter-subnet traffic flows.
👉In Part 1 we cover the underlay config, and prove it with static VXLAN before configuring EVPN for L2VNI (intra-subnet)traffic.
🚀In Part 2 we will configure asymmetrical and symmetrical IRB for Layer 3 routing.
⏰Time stamps
00:00 Intro
01:04 Network design
03:55 Underlay configuration - VLANs, IP addressing, and OSPF
07:40 Static VXLAN - three VTEPs and two VNIs
12:30 Sending test traffic & viewing MAC tables
21:50 EVPN configuration for L2VNI - BGP peers and address-families
26:55 Viewing BGP EVPN sessions
28:00 EVPN specific config
31:00 The BGP EVPN tables - RT-3s
38:00 Generating RT-2s and viewing the EVPN tables
40:40 Viewing RT-2s in the BGP EVPN table
More info:
community.arubanetworks.com/discussion/evpn-vxlan-blog
🐦@joeneville_

[@patrickcasavant-cssmv]

Big thanks to you Joe! As always, verry well explained, you make it easy to understand! Love your Video's! 👍

[@null_zero]

Thanks Patrick 😊 More to come soon.

[@simonespinedi9586]

Without the labels of the interfaces in the draw it is complicated to understand to which trunk interfaces you allowed vlans 2010 and 2011 but mostly vlans 10,20... you applied for vlans only on 2 interfaces, 1/1/10 and 1/1/20... which of those are for the customer side? and which for the vteps? i'm getting lost...

[@null_zero]

1/1/10 is core, 1/1/20 is out to the customer. VLAN 2010 & 2011 are just the underlay VLANs, 10 & 20 are the ones from the customer that are bound to the VXLAN VNI.

[@baldeepsingh5516]

may have to go another route.

[@simonespinedi9586]

The interfaces where clients are attached are in access or in trunk?

[@null_zero]

Trunk. I was using linux servers with multiple VLAN interfaces to generate traffic in different VLANs from the same physical server. If the client is in the trunk or access doesn't really matter, the customer side VLAN is bound to a VNI in each case. Note also that the VLAN is not carried across the VXLAN network, even if it is a trunk port on the customer side.

[@simonespinedi9586]

I'm trying to replicate this lab, i struggling with the ospf adjacency... it forms neighborship correctly only between vtep 1 to vtep 3 on vlan 2011 and between vtep 2 to vtep 3 on vlan 2012, not between vtep1 and vtep 2 on vlan 2010... Configuration is the same as you did, don't know what to troubleshoot... Trunk on interfaces allow the vlan 2010, and with sh mac-address i can see the mac address of the vtep2 from vtep1, but i can't ping between 10.0.0.0 and 10.0.0.1 Could be a bug?

[@simonespinedi9586]

Obv the network type of ospf is point-to-point

[@null_zero]

Check the configs and ensure that you've used the correct subnet mask on each interface, and check the routing tables & arp tables on the VTEPs. The routing protocol isn't relevant if there's no connectivity across the underlay VLAN.

[@rasheednazar755]

Is your channel sponsored by Aruba to work with Aruba devices only. Anyways nice tuts. can get some idea though!

[@RishiRap]

Command line too small to see. Useless.