Thank you so much for taking the time to share this! Best explanation of VxLAN ever. Got your setup working in my GNS3 lab. Amazing. Also, the intro is simply brilliant.
This is a great nice video series. The content shared definitely helps a lot Understanding what really happens with VXLAN. Keep up the good job. This is by far one of those video series I would have paid for in platforms like Udemy or any other. :)
Great lesson as always - as expected from Network Direction - seriously :) If would be great to have an overview diagram of data center deployment with VxLAN Spine & Leaf configuration: VPC to the Hosts; Complete Path to show Hosts on VPC of one Leaf communicate with other Hosts in other Leaf; and how the outside world connect to the VxLAN domain. Thanks
Hi, could you make a series about SDN, Openflow and such technologies you're videos are really helpful understanding technologies and easy to follow, keep it up bro Thanks
at time 6:07. shouldn't the UDP header come first and then the IP header on top of it. Meaning the IP packet should have the UDP segment as payload ? Please correct me if I am wrong.
Holy shit lol Im only CCNA, but I work with virtual machines such as firewalls that all our traffic runs through, so it made some sense but Im not sure I get it fully. Professional levels already probably can tell Im misunderstanding it.
We are starting a project with MP-BGP EVPN and have 2 spines and 6 leafs. All the tutorials I have watched configure underlying network with OSFP and then BGP on top to create neighbor relationships with loopbacks. Is that the recommended apprach or is it to use BGP purely for underlay and forget about OSPF ? The plan is to run NSX-T on the network.
You don't have to use OSPF. Technically, you just need routing, so you could use static routes if you want to (although I wouldn't recommend it). OSPF or EIGRP are the simplest options. This keeps routing protocol separation between the underlay and overlay. You can use BGP in the underlay, but it is more complicated, and you need to make sure you're doing it right.
I have one question VXLAN increases scalability up to 16 million logical networks (with 24-bit VNID) VLAN to VNI mapping is one to one. That is, In the configuration, we can map one VLAN to one VNI. Then how it is scalable to 16 million?
I've had this question a few times, and it's one I asked myself initially On each switch, a VNI could map to any VLAN (remember that the switch is routed, so VLANs in the underlay are locally significant to the switch). So while the VNI is unique, VLANs can be reused. For example, VNI 90001 could map to VLAN 10 at site-A, while VNI 76543 could map to VLAN 10 at Site-B. The limit here would be that a single switch could only perform 4094 VLAN to VNI mappings
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.
There are some similarities to MPLS, especially L3VPN's. The difference is that this was designed to work in the data centre, while MPLS was designed for service providers. VXLAN was meant for well defined hierarchical structures like spine/leaf, while MPLS can handle more of a distributed approach. Also MPLS technically doesn't tunnel like VXLAN does. It adds tags to packets, but doesn't 'hide' the original packet.
I'm really having a hard time understanding what is an overlay network. Seems like both underlay and overlay networks are IP based, i don't see the added value an overlay provides...
In this case they are, but they don't have to be. Imagine that you have two sites, with routing in between. You want to stretch your server subnet across two sites. You can't stretch a VLAN across the link, as you have routes there, so how do you do it? Using an overlay, we can stretch the subnet over the routed link.
@@NetworkDirection Alright then i guess my question is, what is wrong with having a packet forged then encapsulated and sent across different IP networks? I'm not against the principle i'm trying to figure out what do we gain by strechting the subnet ? Why doing that?
Read the full story: networkdirection.net/VxLAN+Overview Download the video resources: www.patreon.com/posts/resources-vxlan-20793071 The book (affiliate): click.linksynergy.com/link?id=RL4E*8CmbSY&offerid=145238.2463561&type=2&murl=http%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9781587144677
This guy has a great approach to teaching I hope he continues to produce great content like this
what a nice example of an expert making high tech to the reach of newbies ! Congrats
Thanks!
PERFECT , NEVER SEEN ANYONE DESCRIBED VXLAN BETTER THAN IN THIS SERIES A+++
Thanks!
this how networking should be teached , very engaging
Thanks! I'm glad to hear you found our video engaging! Hope you have a great day.
Very Helpful and simple explanation to get closer.
Stumbled on your channel searching this topic. Only 6 minutes in and I'm already subscribed. Thanks for the great content
Thank you so much for taking the time to share this! Best explanation of VxLAN ever. Got your setup working in my GNS3 lab. Amazing. Also, the intro is simply brilliant.
Awesome visualization about overlay and underlay. Excellent!
Thank you
Very nice video, full of information taught in an easy manner.
Thanks!
A great video! The visualisations really helped explain the difference in functions between the underlay and overlay networks. Thank you!
I'm so happy that they were useful. It's a bit of an abstract concepts to get used to at first, so I'm glad it worked out.
Part 2 coming tomorrow!
This is really well made. I was trying to understand the concepts from INE but this explains even better than them
That's really good to hear, thank you!
Excellent explanation. The best by far on CZcams. Thanks
thanks for spending time for nice graphics and visualization, also for info without unnecessary crap.
You're welcome! I try to keep them as short and to the point as I can
This intro made my day lmao
Your intro made me laugh so much! I think it's incredible you put the effort into doing that for your viewer's enjoyment :)
Thank you so much! I enjoyed making it 😄
@@NetworkDirection Keep it up my friend!
Wow love the way you explain this topic
Thanks Jerry! I am really glad you found this helpful. Cheers
Passed 400 views so far, thanks everyone!
Part 2 coming on the 8th/9th of Feb (depending on timezone).
Hope you'll like it!
A bit more than that now :)
@@squelchedotter Hahaha, yeah. Up to 162,000 at the time of writing this
Thank you so much, great explanation of VxLan
thanks for watching!
I'm really enjoying your videos. Probably the best network training videos I've seen to date.
Thank you!
Hey your explanation method is too good . I have never seen such explanation before .
Very informative both the visualization and the script.
Thanks Reza
easy and simple. Thanks a lot!
Thanks for watching, glad you liked it
Thank you so much 🙏🙏...was eagerly waiting for the same
Awesome explanation and the animation makes it so much easier to understand . Thankyou for creating this great content.
Thank you, and you're welcome!
Falling In love with way of Traning
Thank you!
A great video indeed, very nice animations to help illustrating the concept. Thank you!
Thanks for watching 🙂
thank you very much for this man.... its helping me in my ccie dc review
This is so good to hear, thanks! Glad to help!
Detailed explanation with clear sub-topics. Great Work!
@Network Direction - Definitely am on your direction :P
Nice! Thanks!
Fantastic series.
Finally some great Vxlan explanation on internet.
I love that intro 😂
I had fun with that. Not the most productive use of my time, but totally worth it
well done guys... cant wait to see following parts
Thanks Sinan,
Two more days for part 3, hope you like it
Thanks for breaking down the VXLAN concepts. A course on Service instances, BDIs in EVCs would be really helpful!
Thanks for the suggestions 😎
Amazing video. Thank you so much.
Glad you liked it!
The only time that I hit Like and Subscribe just because the CZcamsr said so.
Such a neat explanation. Thanks dear. \m/
I know what you mean. It's such a common catchphrase now. I rarely say it any more.
But in any case, thankyou for subscribing!
Fantastic series, thanks for posting this!
You’re welcome 😊
Sir, thank you, very helpful explanation.
This is a fantastic tutorial set, thank you for putting this together!
You're welcome, glad you like it!
great video
Thanks!
Thank you for this series. Well done.
This video was useful to me and I am looking forward to watch the next video.
It was a fun series to make, so I'm glad you're looking forward to the next one
please make more videos on data center tech like ACI you got very good voice and knowledge
This is a great series. Would love to see all the parts!!
So glad that you're loving it!
I haven't finished creating all the series yet.
They're on a 2 week release schedule, next one coming on 8/9 or Feb
Thnaks to clear my vxlan concept.
You're welcome!
Vxlan rfc is actually informational
Thanks!
Awesome explanation!!
Thanks Avinash, a lot of time went into it, so it's good to hear that it's useful
better than the last two seasons of arrested development.
hahaha, yeah. I didn't even get through the last season
You made VXLAN so simple...Thanks :)
you're welcome
Excellent material!
Much appreciated!
Very well done. Thanks very much for sharing, Keep going !
Thanks, glad you liked it!
This is a great nice video series. The content shared definitely helps a lot Understanding what really happens with VXLAN. Keep up the good job. This is by far one of those video series I would have paid for in platforms like Udemy or any other. :)
Thanks Ricardo
Sounds like I should have been charging 😄
nice video.
Glad you liked it!
I love your intro 😂
Me too! It took a while to make...
Perfect explanation, Thank you!
Great lesson as always - as expected from Network Direction - seriously :) If would be great to have an overview diagram of data center deployment with VxLAN Spine & Leaf configuration: VPC to the Hosts; Complete Path to show Hosts on VPC of one Leaf communicate with other Hosts in other Leaf; and how the outside world connect to the VxLAN domain. Thanks
There are some great ideas here Dan. I might look at expanding the series.
Thanks for the suggestions!
Simple way very efficiently explained 👌👏 thank you any videos from you on Cisco ACI and SD Access
thank you!
I haven't used Cisco's ACI or SR Access yet, so I can't make any videos on them at this time, sorry
Very helpful explainations
Thanks Prashant!
My goal is to explain well, so your feedback is encouraging
One word perfect.
Thanks a lot for Such Nice Explaination.
no worries
Thank you for a good explanation !
subbed literally for the intro lol
Thanks
Thanks for watching!
Beautiful!
Awesome vídeo.
Thanks Diogo!
Hi,
could you make a series about SDN, Openflow and such technologies
you're videos are really helpful understanding technologies and easy to follow, keep it up bro
Thanks
This is great stuff!! thank you so much for your efforts!
Only took the intro to know I'd like this lol its an "Arrested Network Development"
Reminds me so much of EoIP.
Good boy
thanks for you ，
You're welcome
Currently studying CCNP Ent, this is a subject I've never even heard of haha
This one will come up in the data centre certifications, I think
@@NetworkDirection It's in the ENCOR exam to
Good video and didact!!!
Thanx!!
such a clear video. you made it like A-B-C ... that simple! thanks a ton, ofcourse you get a like and subscriber too.. ;)
Thanks, it's good to hear that it's clear!
at time 6:07. shouldn't the UDP header come first and then the IP header on top of it. Meaning the IP packet should have the UDP segment as payload ? Please correct me if I am wrong.
Holy shit lol Im only CCNA, but I work with virtual machines such as firewalls that all our traffic runs through, so it made some sense but Im not sure I get it fully. Professional levels already probably can tell Im misunderstanding it.
We are starting a project with MP-BGP EVPN and have 2 spines and 6 leafs.
All the tutorials I have watched configure underlying network with OSFP and then BGP on top to create neighbor relationships with loopbacks.
Is that the recommended apprach or is it to use BGP purely for underlay and forget about OSPF ?
The plan is to run NSX-T on the network.
You don't have to use OSPF. Technically, you just need routing, so you could use static routes if you want to (although I wouldn't recommend it).
OSPF or EIGRP are the simplest options. This keeps routing protocol separation between the underlay and overlay.
You can use BGP in the underlay, but it is more complicated, and you need to make sure you're doing it right.
From my understanding, NSX-T doesn't use VXLAN (although NSX-V does). Instead it uses Geneve
I have one question
VXLAN increases scalability up to 16 million logical networks (with 24-bit VNID)
VLAN to VNI mapping is one to one. That is, In the configuration, we can map one VLAN to one VNI. Then how it is scalable to 16 million?
I've had this question a few times, and it's one I asked myself initially
On each switch, a VNI could map to any VLAN (remember that the switch is routed, so VLANs in the underlay are locally significant to the switch).
So while the VNI is unique, VLANs can be reused. For example, VNI 90001 could map to VLAN 10 at site-A, while VNI 76543 could map to VLAN 10 at Site-B.
The limit here would be that a single switch could only perform 4094 VLAN to VNI mappings
How to configure 2 vlan for same customer but same vni?
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.
great video man! but I have a question, it looks a little bit like mpls, or is it just me? where is the difference? thx
There are some similarities to MPLS, especially L3VPN's.
The difference is that this was designed to work in the data centre, while MPLS was designed for service providers.
VXLAN was meant for well defined hierarchical structures like spine/leaf, while MPLS can handle more of a distributed approach.
Also MPLS technically doesn't tunnel like VXLAN does. It adds tags to packets, but doesn't 'hide' the original packet.
Network Direction thanks man!
You’re very welcome 😀
I want to install an SOHO network please I need guidelines on how to do it
You try to give the video more brightness it will be great if you do
Thanks for the feedback
Think it could be done across the WAN without SPINE involvement? Just two nexus switches using BGP-EVPN.
CAN YOU GIVE ME MORE INFORMATIONS ABOUT VLAN PLEASE
I'm really having a hard time understanding what is an overlay network. Seems like both underlay and overlay networks are IP based, i don't see the added value an overlay provides...
In this case they are, but they don't have to be.
Imagine that you have two sites, with routing in between. You want to stretch your server subnet across two sites. You can't stretch a VLAN across the link, as you have routes there, so how do you do it?
Using an overlay, we can stretch the subnet over the routed link.
@@NetworkDirection Alright then i guess my question is, what is wrong with having a packet forged then encapsulated and sent across different IP networks? I'm not against the principle i'm trying to figure out what do we gain by strechting the subnet ? Why doing that?
@@yumenokira7595 Some technologies require devices to be in the same subnet. Some examples are storage replication, and vMotion
@@NetworkDirection Got it. Thank you very much for taking the time to answer :)
Read the full story: networkdirection.net/VxLAN+Overview
Download the video resources: www.patreon.com/posts/resources-vxlan-20793071
The book (affiliate): click.linksynergy.com/link?id=RL4E*8CmbSY&offerid=145238.2463561&type=2&murl=http%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9781587144677
100
Gonzalez Anna Hall Kenneth Hall Ruth
Australian
yes
Arrested Development
Yes!
man this is like Chinese to me