I have searched various tutorial on VXLAN but got confused along the way, until I landed on this one. Now I understand the concepts of VxLAN and how to use this protocol. Thanks Engineer BitsPlease, you're Awesome 👍
Thank you BitsPlease for the great lessons about VxLAN. Your teaching is amazing to precisely summarize the knowledge required for VxLAN implementation. You've save me from insanity when trying to learn VxLAN :)
amazingly detailed. one of the best videos on the subject ive seen. Goes through all the pieces in depth and very well explained. Thank you for creating this series.
A big thankyou for this , you have explained in such simple terms ...it is so difficult to understand from documents ...thaks a lot ..will look forward to other videos related to vxlan evpn.
as host sends the GARP Message, the local table of the Leaf-switch will learn the Mac-address of the host , but while sending the details to the Route-reflector(which is basically the Spines) ,it includes additionally the VTEP IP of the Leaf-switch where its connected.. Guys, agree with me ?
Great Video! very informative. though am still confused with the underlay and overlay concept, OSPF and multicast runs over underlay and VXLAN and BGP EVPN runs on overlay for control plane. does it mean data flows on overlay's data plane? if so what will happen if OSPF neighbourhood fails, data will still flow via Overlay via VXLAN and BGP EVPN????
if you are having GARP and supress ARP, then what is the need to configure multicast ? once the endhost do GARP leaf using the control plane should send the info to other leaf and using Supress ARP endhosts can populate their arp table ? do you think without multicast it can work ?
Hello Joel, That was a very Good explanation on vxlan. I would like to know your homelab specs for building this lab topologies. Could you recommend a server or pc that could handle these topologies?
thank you for you explanation and efforts. I fallow up all your instructions and I am trying to build my own lab. at the end I can ping the getaway from PCs but from PC1 I can`t ping PC3. and same with vlan20. I can ping there getaways but from one PC I can`t ping other PC. can you please help me troubleshot it? cheers
Like your video. But having one clarification. Why do you use Loopback IP address for the physical interface links between Leaf and Spine? I thought loopback ip addresses are only for the VTEP ip addresses. Can we have different ip addresses for physical links and different loopback address for VTEPs?
Thanks for the time spent making the video. It got a bit confusing toward the last part, at least for me. Specifically, I could not visually map what you explained about MAC-vrf and IP-vrf to the the configuration script.
Thanks Marco. Well in L2VNI you just have the MAC vrf in play. (IP vrf in the next video)And there isn't much to configure honestly with it as the l2vpn evpn address family config takes care of it. MAC Vrf is just a contruct to explain the fact that we are now exchanging MAC routes and inorder to distinguish all these MACs coming from different VLANs into the l2vpn evpn table, we need a RD just like the age old MP-BGP days. Hope that helps
Hi....thanks .... (1)vxlan tunnel created must go thru spine device or it will be between leaf-to-leaf? from IP perspective seem the the next hope is the spine. (2) Why we need mplsoudp in the overlay if vxlan is already leverage for overlay protocol...Thanks
1) Vxlan tunnel is created between leafs. But the underlay is via the spine since leafs are not directly connected to each other. 2) Can you re-phrase this one. I didn't get the question
@@BitsPlease (1) virtually the traffic traverse via tunnel is transparent to underlying physical topology right, meaning that more efficient and no hop.. can I conclude that? (2) If overlay network is already running with vxlan...why we need mplsoudp as I can understand from my readng some of the overlay network are using vxlan and mplsoudp as overlay transport.
I have completed your entire VXLAN series, you explain so nicely. I just have question which you miss here like if I need device level redundancy for a host like in VPC how I achieve it in VXLAN
The 2 switches involved in VPC will act as a single VTEP from data plane perspective. BGP peering has to be set up individually from both the switches towards the spine.
Can you please share the video where you discussed MP-BGP in detail. I checked your MPLS playlist but couldn't find in which vid you talked about MP-BGP
Hi, one of the advantages of using VXLAN is unlimited vni compared to traditional 1-4095 vlans. I'm struggling to understand how VXLAN helps with this, as you still have to map VNI to traditional VLANs; this some how means you can only have as much VNIs as you have traditional VLANs. Another question, in this scenario say on leaf NXOS3 you already had 4095 hosts and each of them on separate VLAN, when you want to add a new host on the same Leaf on its separate VLAN how would you do it?
Every VLAN on any Leaf is locally significant. Now imagine 4 Leafs Leaf-1 has vlans 1-4095 mapped to VNI 1- 4095 Leaf-2 has vlans 1-4095 mapped to VNI 4096- 8190 Leaf-3 has vlans 1-4095 mapped to VNI 1- 4095 Leaf-4 has vlans 1-4095 mapped to VNI 4096- 8190 Technically we have increased the broadcast domains from 4095 to 8190. Haven’t we? Ex: VLAN 1 on Leaf 2 can talk to VLAN 1 on Leaf 4 using VNI 4096. No imagine 4 more switches with VNI going from 8191 - 16380. Similarly VXLAN can scale to 16 million Though the above is just an example, no one uses 4095 VLANs on a switch due to resource limitation.
@@BitsPlease with the mapping you have used how will host in vlan 1 on leaf 1 mapped to vni 1 be able to communicate to host in vlan 1 on leaf 2 mapped to vni 4096, assuming vni uses the same number as vn-segment
@@BitsPlease I’m looking to understand how this can be useful in my environment, I have a phyical interface on a router that has exhausted 4094 subinterfaces mapped to vlans. My solution to this problem is using another physical interface on the router and connect to a different switch to serve the hosts. Can this technology help there?
Also back to your problem, (if i understood it right) you can't really use VXLAN to increase the VLANs beyond 4095 cause VXLAN doesn't bypass that local VLAN switch limit. All it does is in a cloud multi-tenant environment, it gives you more scalability to re-use the VLAN numbers across multiple customers by distinct VNIs
you have to explain little more to understand the technology for who doesn't have any basic. My suggestion is running more, "show commands" and explain in little deeper. I watch another video to understand what you are taking about. channel name is : "BridgeWhy" for your reference. Btw he is providing only paid video classes for complete course.
I have searched various tutorial on VXLAN but got confused along the way, until I landed on this one. Now I understand the concepts of VxLAN and how to use this protocol. Thanks Engineer BitsPlease, you're Awesome 👍
You explained VXLAN better than anyone ! thank you
Thank you BitsPlease for the great lessons about VxLAN. Your teaching is amazing to precisely summarize the knowledge required for VxLAN implementation. You've save me from insanity when trying to learn VxLAN :)
Thanks Dan !
This is a really good video on L2VNI not just that, you also touched upon the concepts around VXLAN which were well articulated.
amazingly detailed. one of the best videos on the subject ive seen. Goes through all the pieces in depth and very well explained. Thank you for creating this series.
Thanks Kevin !
This is very helpful and very well explained..
Thank you Sir for such rich contents ❤
One of the best video i came across for EVPN ! Thanks a lot for this.
A big thankyou for this , you have explained in such simple terms ...it is so difficult to understand from documents ...thaks a lot ..will look forward to other videos related to vxlan evpn.
Thanks Ayushi.
Excellent video..thank you so much for sharing wonderful information.
Thank you for this.
Appreciate this stuff. Hard to find so much of details that too in a proper sequence. 👍
Thanks man !
You told type 2 route holds MAC address + VTEP IP address, but during the route table explanation, it was MAC address + end host IP address
as host sends the GARP Message, the local table of the Leaf-switch will learn the Mac-address of the host , but while sending the details to the Route-reflector(which is basically the Spines) ,it includes additionally the VTEP IP of the Leaf-switch where its connected.. Guys, agree with me ?
what a great video and teacher. many thanks keep it up
Thank you !
Great Video! very informative. though am still confused with the underlay and overlay concept, OSPF and multicast runs over underlay and VXLAN and BGP EVPN runs on overlay for control plane. does it mean data flows on overlay's data plane? if so what will happen if OSPF neighbourhood fails, data will still flow via Overlay via VXLAN and BGP EVPN????
No.. friend.. overlay is interdependent on underlay.. if underlay links get failed.. overlay connection will be broken & lost
if you are having GARP and supress ARP, then what is the need to configure multicast ? once the endhost do GARP leaf using the control plane should send the info to other leaf and using Supress ARP endhosts can populate their arp table ? do you think without multicast it can work ?
Hello Joel,
That was a very Good explanation on vxlan. I would like to know your homelab specs for building this lab topologies. Could you recommend a server or pc that could handle these topologies?
thank you for you explanation and efforts. I fallow up all your instructions and I am trying to build my own lab. at the end I can ping the getaway from PCs but from PC1 I can`t ping PC3. and same with vlan20. I can ping there getaways but from one PC I can`t ping other PC. can you please help me troubleshot it?
cheers
Why remote mac learnt are tagged as static and locally learnt macs are dynamic? Shouldn't both of them should be dynamic?
What are you using to draw? I notice it’s macOS.
bro good work, what is minimum devices to achieve the same? like can we lab with 1 spine 2 leaf ?
Awesome video, thanks for sharing
very good explanation!
Can you share the config's for all spines and leaf's here ?
QQ- If switch receives ARP broadcast, it should be able to respond back with the answer, due to EVPN database, so no need to BUM ? right
Hello, Great video. I was wondering what do you use a pen for drawing in onenote on mac. Thanks
I use a wacom tablet.
@@BitsPlease thanks
Which Nexus Devices will you suggest as Nexus 9000 Series Switch taking all my RAM/CPU as well?
Hi @BitsPlease hope you can add multisite on this series. Thanks!
Excellent, but is it vxlan used in ACI.any scenario
Like your video. But having one clarification. Why do you use Loopback IP address for the physical interface links between Leaf and Spine? I thought loopback ip addresses are only for the VTEP ip addresses. Can we have different ip addresses for physical links and different loopback address for VTEPs?
hello, what server software images I need to use for bgp evpn solution ?
what server configuration i must buy
please help
Thanks for the time spent making the video. It got a bit confusing toward the last part, at least for me. Specifically, I could not visually map what you explained about MAC-vrf and IP-vrf to the the configuration script.
Thanks Marco. Well in L2VNI you just have the MAC vrf in play. (IP vrf in the next video)And there isn't much to configure honestly with it as the l2vpn evpn address family config takes care of it. MAC Vrf is just a contruct to explain the fact that we are now exchanging MAC routes and inorder to distinguish all these MACs coming from different VLANs into the l2vpn evpn table, we need a RD just like the age old MP-BGP days. Hope that helps
Hat off sir. Thank you.
i made the same config but bgp session is not stablished...i do not understand how is possible under this config bgp sesion could stablished...
Fantastic tutorial. Thank you very much.
Hi....thanks .... (1)vxlan tunnel created must go thru spine device or it will be between leaf-to-leaf? from IP perspective seem the the next hope is the spine. (2) Why we need mplsoudp in the overlay if vxlan is already leverage for overlay protocol...Thanks
1) Vxlan tunnel is created between leafs. But the underlay is via the spine since leafs are not directly connected to each other.
2) Can you re-phrase this one. I didn't get the question
@@BitsPlease (1) virtually the traffic traverse via tunnel is transparent to underlying physical topology right, meaning that more efficient and no hop.. can I conclude that? (2) If overlay network is already running with vxlan...why we need mplsoudp as I can understand from my readng some of the overlay network are using vxlan and mplsoudp as overlay transport.
Hi, which stylus are you using for your MacBook?
Do you have a plan to build multisite dc (DCI) using arista veos? Would like to watch it
Very good work. A small correction in Type 2 route if it contains the IP address along with mac this IP is not VTAPS IP but the host IP
Very well explained Sir :)
I have completed your entire VXLAN series, you explain so nicely. I just have question which you miss here like if I need device level redundancy for a host like in VPC how I achieve it in VXLAN
The 2 switches involved in VPC will act as a single VTEP from data plane perspective. BGP peering has to be set up individually from both the switches towards the spine.
Hi! Thanks for your videos! What NX-OS are u using?
It's been a while with this one but I think it was Nexus 9000v 7.0(3)I7(1).
Excellent video, thank you!
Best tutorial! Thanks a lot!
Can you please share the video where you discussed MP-BGP in detail. I checked your MPLS playlist but couldn't find in which vid you talked about MP-BGP
MP-BGP is used in MPLS L3 VPN, so this lecture of mine should help - ruclips.net/video/cqC3egLqJ8k/видео.html
What is the CPU and memory settings of your NXOS nodes in EVE? Or do you set it to default? You probably work on a server with very high RAM and CPU.
Yeah I use the default. The server has 24 cores and 128 g ram
Excellent Thank you for this topic
What images in Eve-NG are you running for your spines and leafs?
Nexus 9kv on 7.x release.
thank you so much , great explain
The best video for vxlan available on the internet.
Can you help with the stimulator u have used
I am using nexus titanium image in eve-ng but these commands are not available like "feature nv overlay"..
This lab uses Nexus 9kv 7.x images and not titanium
Can you share the configs if possible ?
Really nice explanation.
Hi, one of the advantages of using VXLAN is unlimited vni compared to traditional 1-4095 vlans. I'm struggling to understand how VXLAN helps with this, as you still have to map VNI to traditional VLANs; this some how means you can only have as much VNIs as you have traditional VLANs.
Another question, in this scenario say on leaf NXOS3 you already had 4095 hosts and each of them on separate VLAN, when you want to add a new host on the same Leaf on its separate VLAN how would you do it?
Every VLAN on any Leaf is locally significant.
Now imagine 4 Leafs
Leaf-1 has vlans 1-4095 mapped to VNI 1- 4095
Leaf-2 has vlans 1-4095 mapped to VNI 4096- 8190
Leaf-3 has vlans 1-4095 mapped to VNI 1- 4095
Leaf-4 has vlans 1-4095 mapped to VNI 4096- 8190
Technically we have increased the broadcast domains from 4095 to 8190. Haven’t we? Ex: VLAN 1 on Leaf 2 can talk to VLAN 1 on Leaf 4 using VNI 4096.
No imagine 4 more switches with VNI going from 8191 - 16380.
Similarly VXLAN can scale to 16 million
Though the above is just an example, no one uses 4095 VLANs on a switch due to resource limitation.
@@BitsPlease with the mapping you have used how will host in vlan 1 on leaf 1 mapped to vni 1 be able to communicate to host in vlan 1 on leaf 2 mapped to vni 4096, assuming vni uses the same number as vn-segment
@@BitsPlease I’m looking to understand how this can be useful in my environment, I have a phyical interface on a router that has exhausted 4094 subinterfaces mapped to vlans. My solution to this problem is using another physical interface on the router and connect to a different switch to serve the hosts. Can this technology help there?
@@johnmoff9324 I have edited the above reply to make it a little less confusing.
Also back to your problem, (if i understood it right) you can't really use VXLAN to increase the VLANs beyond 4095 cause VXLAN doesn't bypass that local VLAN switch limit. All it does is in a cloud multi-tenant environment, it gives you more scalability to re-use the VLAN numbers across multiple customers by distinct VNIs
Buen video saludosss de Perú
Videos are not loud enough. Maxed out the volume but still can just hear it.
Could you please upload this video in HD
It’s available in HD now. RUclips takes few hours to process it into HD : )
L2VNI like MAC VRF .this is the same like L2Vll services in the MPLS like we create xconnect an interface Valn.
Great one!
great video
Great Sir !!
Excellent
Good one , keep it up
you have to explain little more to understand the technology for who doesn't have any basic. My suggestion is running more, "show commands" and explain in little deeper. I watch another video to understand what you are taking about. channel name is : "BridgeWhy" for your reference. Btw he is providing only paid video classes for complete course.
Won't it be simpler to just name the spines Spine1-2 and Leafs Leaf1-4
can you please share the complete script for this
Yogesh Kotiyal Script ? You mean the configs ? It’s on my GitHub. The link to my github is on my channel banner
@@BitsPlease I am not able to find the configuration on GitHub website. Could you please share the path,where is it
@@superyogesh21 github.com/TheFly1ngDutch/bitsplease/tree/main/vxlan-palylist
You explained it better.
What is the rush, slow down buddy.
This is relatively new and complex tech. We all can't grasp and understand it at X100 speed.
Schaefer Forest
Dietrich Mountains
With all respect to this author, but this looks like a bad copy of Terri Winson's youtube tracks (same topic but a way better explanation).
Thanks for the feedback. I did go back to look up the author/videos you mentioned. This video was posted 5 months before them.