You look like a person with a good sense of humor. That's why I chose your video for MP-BGP. It takes a lot of intelligence to get all the jokes. I made the right decision. In tech it's hard to find simple concise explanations. The way you've isolated the components makes it much easier to understand. I've passed the latest CCNP and have a virtual SDWAN network in Cisco Modeling Lab. Still didn't really understand some of the finer points of VXLAN. This playlist is very well stated. Seeing it yesterday I decided to go through the entire series. You are covering subjects that often come up in interviews. Thanks for the series.
Wow, thank you for the amazing feedback! I’m really glad you found the MP-BGP video and the playlist helpful! I try to make my presentation as fun as possible. Networking can get pretty technical and dry at times, so I try to make it more approachable and engaging. It’s awesome to know it resonated with you. 😊 Congrats on passing your CCNP and for running a virtual SD-WAN network in CML! That’s no small feat. VXLAN can definitely have its tricky parts, but once you get the concepts of overlay/underlay and MP-BGP EVPN, it starts to click. Stick with it, and feel free to drop a question anytime-I’d love to help. Best of luck on your networking journey, and I hope the rest of the series gives you even more value for those interview prep moments. You’ve got this! 🚀
Your comment put a smile on my face!! :D I will continue my videos on VXLAN and I'll think about putting together a troublshooting section... I'll do my best!
In addition to increasing the number of VLANs, can you touch on using VXLAN to extend a VLAN between multiple autonomous datacenters? This is the function I keep hearing VXLAN used for mostly in my day to day. Thanks for the great videos!!!
I appreciate how you explain things very simple starting from the basics and the reasons behind using newer or alternative technologies. I hope you'll consider posting some videos on firewalls in the future.
I'm so happy you find my style and approach informative! I will put firewalls and security in general on my to do list for the future... Thanks for the suggestion!
Hi, when i use vxlan to extend a vlan over a ipsec tunnel, it change the MTU of the interface on fortigate firewall, from 1500 to 1357, and in my test i have to change the MTU at the windows server for example. How can i do this without change this mtu, what you recommend?
A VXLAN encapulated packet will use UDP as the transport layer protocol, and will thus prepend a UDP header. This UDP datagram still goes through further encapsulation into an IP packet, and into an Ethernet Frame (or whatever other Layer 2 potocol is being used). All of this takes place on the Underlay network. Everything that is on the inside of the VXLAN header is part of the overlay network. Take a look at the next few videos which clarify this point even more.
Hellow Lazarus, wanted to clarify this point on vxlan...You can theoretically create as many as 16 million VXLANs in an administrative domain, compared to a maximum of 4094 traditional VLANs. I had a question on this. In a EVPN VXLAN network, we use VNI:s. Let say in a very big data center, we exceed 4096 VLANS. The good thing is we can use VNI and what I understand (correct me if Im wrong) of how EVPN VXLAN works is that you map a unique VNI to a VLAN, so for example VNI: 21500 to vlan 215. If we have used all vlans, so all 1-4096 VLANs, how can we then use VNIs? If we use all 4096 VLANs, how will we then use the VNI? How does it works if all 4096 VLANs are used and there are no more left?
This is an excellent question! In all of my examples, I keep a one to one relationship between the VNIs and the VLAN IDs. This is done to make it easier to keep track. And since our labs are always much smaller than 4K VLANs, we are able to achieve this. But what happens when you have, say 12000 VNIs in a VXLAN topology? How do you do VLAN to VNI mapping then? You will run out of VLANs! Well, the key is that in a VXLAN topology, the VLANs used at each switch only have local significance. What does this mean? Well, it means that within each switch, you can map your VNIs (which have global significance) to any local VLANs (local significance). Practically, this means that you can achieve the following mapping: - map VNIs 1000-1999 to VLANs 1 to 1000, on VTEP1 - map VNIs 2000-2999 to VLANs 1 to 1000 on VTEP2 - map VNIs 3000-3999 to VLANs 1 to 1000 on VTEP3 - map VNIs 4000-4999 to VLANs 1 to 1000 on VTEP4 - map VNIs 5000-5999 to VLANs 1 to 1000 on VTEP5 - map VNIs 6000-6999 to VLANs 1 to 1000 on VTEP6 - map VNIs 7000-7999 to VLANs 1 to 1000 on VTEP7 - map VNIs 8000-8999 to VLANs 1 to 1000 on VTEP8 - map VNIs 9000-9999 to VLANs 1 to 1000 on VTEP9 - map VNIs 10000-10999 to VLANs 1 to 1000 on VTEP10 - map VNIs 11000-11999 to VLANs 1 to 1000 on VTEP11 - map VNIs 12000-12999 to VLANs 1 to 1000 on VTEP12 - and so on... So overall on the whole VXLAN topology, you can use the full range of 16M VNIs, but on each individual switch, you still have the limitation of configuring up to 4K VLANs. But that limitation is not a problem, because a switch will quickly run out of memory before it runs out of VLAN IDs... Does that make sense?
In a sense, it is Layer 2 being tunneled or encapsulated in a Layer 4 UDP datagram, which itself is supported by a Layer 3 infrastructure. It is indeed on top of regular Ethernet and IP infrastructure. Because the underlay is based on IP, which doesn't have the scalability limitations of VLANs, its deployment is flexible and can even span physical locations. There are more videos to come that will further explain it...
Thank you for your kind words. Hmm, regarding interviews, that's a big question to answer. Knowing what VLAN is and what it is used for and how it can benefit a company is important. I belive that the content of this series of videos gives you a very good understanding of these things. Now if the job position you are interviewing for is highly technical, and specifically focused on implementing VXLAN in a variety of scenarios, then you may need a little more hands on experience to be able to rise to the challenge of such an interview. I am planning on doing a short series on interviews for telecom and networking positions in the future that may be helpful, so stay tuned!
My pleasure! I will be working on MPLS after VXLAN, and I will make a note to include EVPN over MPLS at some point in my videos. Thanks for the suggestion!
You look like a person with a good sense of humor. That's why I chose your video for MP-BGP. It takes a lot of intelligence to get all the jokes. I made the right decision. In tech it's hard to find simple concise explanations. The way you've isolated the components makes it much easier to understand. I've passed the latest CCNP and have a virtual SDWAN network in Cisco Modeling Lab. Still didn't really understand some of the finer points of VXLAN.
This playlist is very well stated. Seeing it yesterday I decided to go through the entire series. You are covering subjects that often come up in interviews. Thanks for the series.
Wow, thank you for the amazing feedback! I’m really glad you found the MP-BGP video and the playlist helpful! I try to make my presentation as fun as possible.
Networking can get pretty technical and dry at times, so I try to make it more approachable and engaging. It’s awesome to know it resonated with you. 😊
Congrats on passing your CCNP and for running a virtual SD-WAN network in CML! That’s no small feat. VXLAN can definitely have its tricky parts, but once you get the concepts of overlay/underlay and MP-BGP EVPN, it starts to click. Stick with it, and feel free to drop a question anytime-I’d love to help.
Best of luck on your networking journey, and I hope the rest of the series gives you even more value for those interview prep moments. You’ve got this! 🚀
Really great video as usual! Really like your overview of VXLAN and looking forward to your other videos.
Thanks so much for your kind words! More on the way!
Incredible explanation Thank you!!!!!.
My pleasure, and thank you too for your great comment!
This is great content, you something I heard about during CCNA studies which seemed difficult very easy to understand
I'm glad you like the content and that it's easy to understand. That's what I'm trying to achieve with this series... Thanks for the feedback!
You put a smile on my face! Really hope you make many more videos on VXLAN. Possibly some troubleshooting tips?
Your comment put a smile on my face!! :D I will continue my videos on VXLAN and I'll think about putting together a troublshooting section... I'll do my best!
In addition to increasing the number of VLANs, can you touch on using VXLAN to extend a VLAN between multiple autonomous datacenters? This is the function I keep hearing VXLAN used for mostly in my day to day. Thanks for the great videos!!!
Yes you're absolutely correct. I will touch on this topic in the upcoming videos as well...
@@telecomTech.explained Amazing as always thank you!
very informative, excellent explanation
Thanks! I'm glad you found it useful!
woow here we go the real studd begin thx a millon that'a what i was waiting for
Great, I'm glad it's what you're looking for! Stay tuned for more!
I appreciate how you explain things very simple starting from the basics and the reasons behind using newer or alternative technologies. I hope you'll consider posting some videos on firewalls in the future.
I'm so happy you find my style and approach informative! I will put firewalls and security in general on my to do list for the future... Thanks for the suggestion!
GR8 Explanation, thanks for the video
Glad it was helpful! I do my best!
Hi, when i use vxlan to extend a vlan over a ipsec tunnel, it change the MTU of the interface on fortigate firewall, from 1500 to 1357, and in my test i have to change the MTU at the windows server for example. How can i do this without change this mtu, what you recommend?
Very informative video, thank you sir
Glad it was helpful!
watch the whole playlist if you wanna understand vxlan. Very clear and helpful explanations for all vxlan-related terminologies. thanks
❤❤❤informative thread here,,, thanks for sharing your knowledge and insights!
You are so welcome! I'm glad you find it useful!
So the head of vxlan header is udp header? How can it pass through the network?
A VXLAN encapulated packet will use UDP as the transport layer protocol, and will thus prepend a UDP header. This UDP datagram still goes through further encapsulation into an IP packet, and into an Ethernet Frame (or whatever other Layer 2 potocol is being used). All of this takes place on the Underlay network. Everything that is on the inside of the VXLAN header is part of the overlay network. Take a look at the next few videos which clarify this point even more.
Great going!.. could you please continue the series with EVPN coverage.
Thanks! The EVPN solution for the VXLAN underlay is coming up! Watch for it!
Hellow Lazarus, wanted to clarify this point on vxlan...You can theoretically create as many as 16 million VXLANs in an administrative domain, compared to a maximum of 4094 traditional VLANs. I had a question on this. In a EVPN VXLAN network, we use VNI:s. Let say in a very big data center, we exceed 4096 VLANS. The good thing is we can use VNI and what I understand (correct me if Im wrong) of how EVPN VXLAN works is that you map a unique VNI to a VLAN, so for example VNI: 21500 to vlan 215. If we have used all vlans, so all 1-4096 VLANs, how can we then use VNIs? If we use all 4096 VLANs, how will we then use the VNI? How does it works if all 4096 VLANs are used and there are no more left?
This is an excellent question! In all of my examples, I keep a one to one relationship between the VNIs and the VLAN IDs. This is done to make it easier to keep track. And since our labs are always much smaller than 4K VLANs, we are able to achieve this. But what happens when you have, say 12000 VNIs in a VXLAN topology? How do you do VLAN to VNI mapping then? You will run out of VLANs! Well, the key is that in a VXLAN topology, the VLANs used at each switch only have local significance. What does this mean? Well, it means that within each switch, you can map your VNIs (which have global significance) to any local VLANs (local significance).
Practically, this means that you can achieve the following mapping:
- map VNIs 1000-1999 to VLANs 1 to 1000, on VTEP1
- map VNIs 2000-2999 to VLANs 1 to 1000 on VTEP2
- map VNIs 3000-3999 to VLANs 1 to 1000 on VTEP3
- map VNIs 4000-4999 to VLANs 1 to 1000 on VTEP4
- map VNIs 5000-5999 to VLANs 1 to 1000 on VTEP5
- map VNIs 6000-6999 to VLANs 1 to 1000 on VTEP6
- map VNIs 7000-7999 to VLANs 1 to 1000 on VTEP7
- map VNIs 8000-8999 to VLANs 1 to 1000 on VTEP8
- map VNIs 9000-9999 to VLANs 1 to 1000 on VTEP9
- map VNIs 10000-10999 to VLANs 1 to 1000 on VTEP10
- map VNIs 11000-11999 to VLANs 1 to 1000 on VTEP11
- map VNIs 12000-12999 to VLANs 1 to 1000 on VTEP12
- and so on...
So overall on the whole VXLAN topology, you can use the full range of 16M VNIs, but on each individual switch, you still have the limitation of configuring up to 4K VLANs. But that limitation is not a problem, because a switch will quickly run out of memory before it runs out of VLAN IDs... Does that make sense?
so vxlan is layer 2 floating on layer 3/4? ethernet floating on ip/udp? ip is on top of regular ethernet infrastructure?
Don't think of it as floating but as a layer2 network tunneled over a layer 3 network as if no layer 3 hops are between the point to point routers.
In a sense, it is Layer 2 being tunneled or encapsulated in a Layer 4 UDP datagram, which itself is supported by a Layer 3 infrastructure. It is indeed on top of regular Ethernet and IP infrastructure. Because the underlay is based on IP, which doesn't have the scalability limitations of VLANs, its deployment is flexible and can even span physical locations. There are more videos to come that will further explain it...
Yes, that's exactly it!
hi hope you good. thanks for effort for us really great i just want to know is this series will be enough regarding interview.
Thank you for your kind words. Hmm, regarding interviews, that's a big question to answer. Knowing what VLAN is and what it is used for and how it can benefit a company is important. I belive that the content of this series of videos gives you a very good understanding of these things. Now if the job position you are interviewing for is highly technical, and specifically focused on implementing VXLAN in a variety of scenarios, then you may need a little more hands on experience to be able to rise to the challenge of such an interview.
I am planning on doing a short series on interviews for telecom and networking positions in the future that may be helpful, so stay tuned!
@@telecomTech.explained thanks for reply. i am realy appricate why you are delivering i am waiting for MPLS series thanks again god bless
PLease cover how to configure vxlan and all the protocols involved.
Thanks for the tip! I will cover as many aspects of VXLAN as I can... Stay tuned!
Thanks for the great info can you talk about Evpn over mpls?
My pleasure! I will be working on MPLS after VXLAN, and I will make a note to include EVPN over MPLS at some point in my videos. Thanks for the suggestion!
thank you
Welcome! 🤗
Want to learn all types of network topology 😅
Great, I will do my best to cover as many topologies as I can in future videos.
@@telecomTech.explained a common interview question, design a rdma network cluster supporting 1000hosts. How to pick a topology, switches and others.