Hi, i just found your channel! I finally get VxLAN! We are implementing this new technology in our company and I've never really grasped it... until now! I will let all my co-workers know about your channel.
The best explanation of VXLAN on the internet. Great animations. We need more videos like this for other topics in the TCP/IP stack which are difficult to understand.
Thanks Aaron, I tried to take a different approach, as when I learned VXLAN, I found most resources were overly complicated. I hope I've made it simple
Great simple to understand format no BS! Same issue with vxlan as with tunnel solutions with MTU and fragmentation. It is possible to reduce MTU on end station to eliminate net fragmentation, however its more difficult to manage.
Thanks for the excellent explanation. I have a couple of queries here: 02:43: With the help of dest VTEP IP address, the packet can reach the destination VTEP but how would it attach the same VLAN id which was stripped off during encapsulation? And, Since the Dest MAC address in inside the inner Data Frame, how would the packet reach the correct machine?
Nice video, just need to point out a small error. At 1:18, you show the vtep adding an IP header and then a UDP header, the order should be reversed, UDP first followed by IP. You have this correct later on, just thought I'd mention it. :-)
Thanks for your feedback! The remainaing parts are on the way, but they're just not all available yet. They're coming out each week. Next one is on the 15/16th of Feb. To see when they come out, the best option is to subscribe and click the notification button Or, you can look at the playlist below. They'll be added there when they're ready. th-cam.com/play/PLDQaRcbiSnqFe6pyaSy-Hwj8XRFPgZ5h8.html
I like the way this is explained, I just don't why I would need jumbo frames. I'd think (like with other overlay networks, GRE, IPsec, ...) it would be better to lower the mtu?
For more details, see: networkdirection.net/VxLAN+Frames The book (affiliate): click.linksynergy.com/link?id=RL4E*8CmbSY&offerid=145238.2463561&type=2&murl=http%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9781587144677
Say i have two datacenters with vxlan and my isp is providing dual homed l2 leased circuit for redundancy. Will vxlan know about the looped topology and still employ stp on interconnects with the isp?
Good question! VXLAN is just an overlay, so loop prevention is based on the underlay network you employ. Generally, you would use BGP with EVPN in the underlay (see how this is configured in part 6). In this case, loop prevention is based on BGP. I should mention though, that the original design of VXLAN was designed to be in a single site. There is now support for EVPN Multi-Site, which you should probably check out. Low latency and stability in you underlay (the provider circuits in this case) are key.
I haven't tried to get VXLAN to carry BPDU's, so I'm not certain, but as far as I know, VXLAN does not carry BPDU's. By employing layer-3 in the underlay, layer-2 loop prevention (that is, spanning tree) is not required
In this particular series, I used real hardware, but in many others I use CML Network diagrams are usually in Visio/Powerpoint, but in this one I think I used Fusion for 3d. It's been a while, so I don't remember exactly for this video
Regarding reserved bits in VxLAN header. Source: cumulusnetworks.com/lp/evpn-data-center-oreilly/ Book by Dinesh Dutt - who designed VxLAN primarily. "I already had over-the-top virtualization (OTV-a proprietary precursor to EVPN) and LISP protocols to support. I wanted VXLAN to look like OTV and for both to resemble LISP, given that LISP was already being discussed in the standards bodies. But there were already existing OTV and LISP deployments, so whatever header I constructed had to be backward-compatible. Thus I made the VNI 24 bits because many L2 virtual networks already supported 24-bit VNIs, and I didn’t want to build stateful gateways just to keep VNI mappings between different tunneling protocols. The reserved bits and the always 1 bit are there because those bits mean something else in the case of LISP and OTV. In other words, the rest of the header format is a consequence of trying to preserve back‐ ward compatibility. The result is the VXLAN header you see."
Is enabling jumbo frame on every device's interface a pain? I'm guessing not so much with automation these days, but some companies have not moved that way yet.
Good question. You wouldn't use the internet as an underlay. VxLAN was primarily meant to be within a single site. There are other technologies that it can integrate with if you want to use it across sites, such as OTV and the newer EVPN Multi-Site. Having said that, I've seen it running across DCI links without these technologies and it's fine. I definitely wouldn't run it over the internet though. If you want an overlay over the internet, perhaps DMVPN with MPLS would be a better option.
I need to know that what is the use of VNI ( even if they are in millions ) as ultimately we are mapping 1 VNI to 1 VLAN , so indirectly we cannot map more than 4096 VNI. So how we can use other VNI on one site ? as we cannot use more than 4096 VNI. Please explain.
Leaf1 4094 vlans are mapped to vni 1-4094, next leaf will have vlan 1-4094 mapped to some other vni ( say 4097- 8000). The point is VLAN has local significance ( limited to that swicth) while VNI has global significance ( across the fabric). Hope it helped!
@@bestsaurabh But what we would achieve from this as same site this much number of VLANS are not required ? Even on next leaf, you can map the same as VLANS with VNI's as well for any communication. I do not see the real use case of this one.
![[LIVE] : ONE ลุมพินี 85 | คู่เอก "ยอดเหล็กเพชร vs ผึ้งหลวง"](http://i.ytimg.com/vi/Qq_19bnnxEo/mqdefault.jpg)
PERFECT , NEVER SEEN ANYONE DESCRIBED VXLAN BETTER THAN IN THIS SERIES A+++
Thanks again!
Welcome to part 2! I hope you enjoy it.
I've moved up the schedule, so a new episode of VxLAN every week.
Next week, the spine/leaf topology
Good presenter, good video. Thank you.
Thank you Nabil, I appreciate that
Hi, i just found your channel! I finally get VxLAN! We are implementing this new technology in our company and I've never really grasped it... until now! I will let all my co-workers know about your channel.
Thanks! Glad you like it!
Cisco ACI brought me here...Excellent explanation
Hope it helped!
Incredibly professional and concise. Definitely, the best network channel I've ever seen!
The best explanation of VXLAN on the internet. Great animations. We need more videos like this for other topics in the TCP/IP stack which are difficult to understand.
Awesome video , very descriptive and easy to understand
Glad you think so!
Fresh approach and straight to the point, Excellent work.
Thanks Aaron, I tried to take a different approach, as when I learned VXLAN, I found most resources were overly complicated. I hope I've made it simple
Great simple to understand format no BS! Same issue with vxlan as with tunnel solutions with MTU and fragmentation. It is possible to reduce MTU on end station to eliminate net fragmentation, however its more difficult to manage.
You are really awesome! You visualize everything so perfectly which makes us understand so easily.
Thanks!
I spent hours reading Cisco doc when I put this together on some Nexus 9ks. Wish this was out then!! Thanks!
I know your pain!
I also spent hours reading the docs and watching the Cisco Live videos... Worth it in the end though.
Nice work editing the video. nice animation and nice explanation. Way to go Network Direction.
Thanks. Took a lot of editing, that's for sure!
Excellent, thank you for this information 🤩
My pleasure 😊
About to do a presentation on VxLAN EVPN Multisite and this was an amazing overview. Thanks for doing these!
You're welcome, glad to be of assistance
Very nice tutorial, looking forward the next episodes.
Good news Atanas, part 3 is now available
th-cam.com/video/x1F-RCW9fqo/w-d-xo.html
One of the best videos on VXLAN! Wow!
Thanks Samantha!
Good Series...I like it. Thanks Network Direction.
You're very welcome!
great video!
Thank you!
Great content!
Thanks Moy!
Sir, thank you, very helpful explanation.
Thank you for explaining! Awesome Videos.
You’re welcome. I hope it made sense
Fantastic Videos. Great job and many thanks.
Glad you like it, thanks for the feedback!
excellent video...conducive voice for learning
Thank you!
Thank you for those good explanations
Hands down, it's awesome!
Thanks!
perfect video about vxlan!
Best way to explain I found, very helpful
Great video series, thank you very much, for your hard work 🙂
Amazing work and animation. Keep 'me coming!!
PERFECT EXPLANATION!!!!!!!!!!! THX
Glad you liked it! Thanks for watching!
Amazing Work . . . Hats off to Network direction (L)
Thanks!
perfect explanation
Thank you!
Thanks for the excellent explanation. I have a couple of queries here: 02:43: With the help of dest VTEP IP address, the packet can reach the destination VTEP but how would it attach the same VLAN id which was stripped off during encapsulation? And, Since the Dest MAC address in inside the inner Data Frame, how would the packet reach the correct machine?
Thanks a lot for Such Nice Explaination.
glad to help
Excellent 👌👌👌👌 thanks
You're welcome
Awesome series so far !!
Nice video, just need to point out a small error. At 1:18, you show the vtep adding an IP header and then a UDP header, the order should be reversed, UDP first followed by IP. You have this correct later on, just thought I'd mention it. :-)
i dont subscribe easily but i love your channel...
I'll take that as a huge compliment!
It was very well explained.
Thankyou for the feedback Owais
I liked the presentation please, we need the following parts if it is possible, tnkhs
Thanks for your feedback! The remainaing parts are on the way, but they're just not all available yet.
They're coming out each week. Next one is on the 15/16th of Feb.
To see when they come out, the best option is to subscribe and click the notification button
Or, you can look at the playlist below. They'll be added there when they're ready.
th-cam.com/play/PLDQaRcbiSnqFe6pyaSy-Hwj8XRFPgZ5h8.html
What an amazing video, loved it!
have to say very good explanation .
Thanks!
Excelent Series.
Cool Videos about this topic
I like the way this is explained, I just don't why I would need jumbo frames. I'd think (like with other overlay networks, GRE, IPsec, ...) it would be better to lower the mtu?
Very nice done.
Thanks!
Great video
Thanks!
Perfect sir
Thank you
For more details, see: networkdirection.net/VxLAN+Frames
The book (affiliate): click.linksynergy.com/link?id=RL4E*8CmbSY&offerid=145238.2463561&type=2&murl=http%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9781587144677
I have recently learned that some of those reserved bits are used for Cisco ACI. I guess other vendors do something similar
Say i have two datacenters with vxlan and my isp is providing dual homed l2 leased circuit for redundancy. Will vxlan know about the looped topology and still employ stp on interconnects with the isp?
Good question! VXLAN is just an overlay, so loop prevention is based on the underlay network you employ.
Generally, you would use BGP with EVPN in the underlay (see how this is configured in part 6). In this case, loop prevention is based on BGP.
I should mention though, that the original design of VXLAN was designed to be in a single site. There is now support for EVPN Multi-Site, which you should probably check out. Low latency and stability in you underlay (the provider circuits in this case) are key.
______ ()____________
| |
| |
| X (STP Block?) | forward
| |
DC#1--------VXLAN on OSPF with dedicated fiber ------ DC#2
does that mean VXLAN dont carry the BPDUs?
I haven't tried to get VXLAN to carry BPDU's, so I'm not certain, but as far as I know, VXLAN does not carry BPDU's.
By employing layer-3 in the underlay, layer-2 loop prevention (that is, spanning tree) is not required
Hi I was wondering what lab environment you use for these videos as well as drawing the network diagrams.. Thanks.
In this particular series, I used real hardware, but in many others I use CML
Network diagrams are usually in Visio/Powerpoint, but in this one I think I used Fusion for 3d. It's been a while, so I don't remember exactly for this video
Good work done Sir
Thank you!
Awesome! thanks.
thanks for sharing
You are very welcome! I'm glad you like the channel
I agree, great video and presenter.
Thanks Van, I appreciate it
Regarding reserved bits in VxLAN header.
Source: cumulusnetworks.com/lp/evpn-data-center-oreilly/
Book by Dinesh Dutt - who designed VxLAN primarily.
"I already had over-the-top virtualization (OTV-a proprietary precursor to EVPN) and LISP protocols to support. I wanted VXLAN to look like OTV and for both to resemble LISP, given that LISP was already being discussed in the standards bodies. But there were already existing OTV and LISP deployments, so whatever header I constructed had to be backward-compatible. Thus I made the VNI 24 bits because many L2 virtual networks already supported 24-bit VNIs, and I didn’t want to build stateful gateways just to keep VNI mappings between different tunneling protocols. The reserved bits and the always 1 bit are there because those bits mean something else in the case of LISP and OTV. In other words, the rest of the header format is a consequence of trying to preserve back‐ ward compatibility. The result is the VXLAN header you see."
The reserved bits can be used for QoS to prioritise one VNI prior to another?It makes sense ?
I've been trying to find some information on this, but I haven't been able to yet 🙁
Thank you so much
Nice
Thanks
Thanks!
Is enabling jumbo frame on every device's interface a pain? I'm guessing not so much with automation these days, but some companies have not moved that way yet.
thanks for video
You're welcome!
very niiiice
Thanks!
Jumbo frames? What if the XVLAN goes over the Internet as the underlay network? I think limiting the MTU would be required.
Good question.
You wouldn't use the internet as an underlay. VxLAN was primarily meant to be within a single site. There are other technologies that it can integrate with if you want to use it across sites, such as OTV and the newer EVPN Multi-Site. Having said that, I've seen it running across DCI links without these technologies and it's fine.
I definitely wouldn't run it over the internet though. If you want an overlay over the internet, perhaps DMVPN with MPLS would be a better option.
Please create more video and share with us.
4:31 what if i don't have admin access to the underlay network? (for example, the internet)
The underlay is created by you and is private. It's a collection of your switches connected together, it's not over the internet
Cisco's iVXLAN uses some of the reserved bits I believe.
Arrested Development! Hahaa! Amazing. Also very informative, thanks!
I wonder how many people know that's arrested development!
Why source and destination IP is different at source and destination VTEP ??
I need to know that what is the use of VNI ( even if they are in millions ) as ultimately we are mapping 1 VNI to 1 VLAN , so indirectly we cannot map more than 4096 VNI.
So how we can use other VNI on one site ? as we cannot use more than 4096 VNI. Please explain.
Leaf1 4094 vlans are mapped to vni 1-4094, next leaf will have vlan 1-4094 mapped to some other vni ( say 4097- 8000). The point is VLAN has local significance ( limited to that swicth) while VNI has global significance ( across the fabric). Hope it helped!
@@bestsaurabh But what we would achieve from this as same site this much number of VLANS are not required ? Even on next leaf, you can map the same as VLANS with VNI's as well for any communication. I do not see the real use case of this one.
So where are you actually from?
Hi Kaushik, thanks for visiting our channel! We live just outside of Sydney, Australia 😀
Thank you very much.
You're very welcome!