EVPN VXLAN - Learn The Basics

EVPN & VXLAN which stands for Ethernet Virtual Private Network and Virtual Extensible Local Are Network. These are two independent protocols which, when working together, offer a great deal of routing capabilities to service provider, data center and enterprise networks. In this video, part 1 of this series, the basic concepts of both EVPN and VXLAN will be introduced such as:
- What has been the traditional approach to networking
- What have the limitations to this approach been and why the need to change
- Where does EVPN and VXLAN come into it and what benefits do they bring
- What are the key terms you need to be aware of when talking about or configuring these protocols
- What is the control and data plane and where does EVPN and VXLAN reside.
👇👇 You can find me on 👇👇
www.linkedin.com/in/davidtownsend1983
=====================================================
💯 Subscribe to keep up with the best Juniper & Junos content 💯:
www.youtube.com/@Netcademy
=====================================================
#junipernetworks #juniper #routing #evpn #network #networksolutions #telecommunications #networkengineer #technology #tech #techtalk

[@Montage614]

Fantastic video really strips it down and provides a clear reason why you would use it and how too!

[@Netcademy]

Loving this! Thanks 👍 I need to work on my writing skills with an Apple Pencil. Harder than I thought it’d be 😂

[@Montage614]

@Netcademy always going to be super hard!! By any chance do you have any plans for certification videos like CCNP or NSE7

[@Netcademy]

@@Montage614 honestly no as they’re Cisco related. However remember the standard routing protocols, in terms of theory, will be the same (more or less) between vendors such as Juniper & Cisco. Of course the configuration style will differ significantly! Any particular protocols or areas you’re thinking of?

[@omaralsedahmad2167]

Thank you for the great efforts and the simple explanations! Great work

[@Netcademy]

You are welcome!

[@mariabolbotenko1525]

Wow thank you, so far the best video on this topic.

[@Netcademy]

Thanks very much much for the positive feedback. There’s more in this series on my channel and one or two more to come Thanks for the support 😁👍

[@Townaset]

Thank you for sharing this excellent overview! I have to re-watch the last EVPN section as there's so much info to digest (not a knock to you, rather It's so much solid information to learn!)

[@Netcademy]

What’s not to love about this feedback. Thanks so much. If I could request that you share my channel (I’m on LinkedIn too) that would be so helpful Next and probably last video in this series I am doing next week and is on the various “show” commands. It’s not as exciting I’ll admit! But blooming very handy if & when you need to troubleshoot Thanks once again

[@quisherkhan6592]

Super explanation, just loved it..

[@Netcademy]

Thank you so much 🙂Subscribe for all the extra content that’s coming weekly 👍

[@Thomas-oh6os]

Hi. I am from Germany and I found your channel randomly. Thi is an absolute great video ov evpn vxlan theier basics und differences bettween this protocols. thumbs up and keep it up. Greetings from Germany 👍

[@Netcademy]

Thanks so much for the positive feedback! I don’t have many followers from Germany so please feel free to share my channel 😁👍 More content coming soon! Thanks 🤩 nice again for the great feedback

[@0812sonu]

Very well explained… gonna see more of these that have been released so far . Keep going 🎉

[@theccieguy]

Good Job 👍

[@Netcademy]

Thanks 😁

[@dadelaar650]

Thanks for this video. Very clear and concise explanation. Couldn't get a grip on these protocols until this video.

[@Netcademy]

Thanks very much! Check out the next video which is around the benefits of EVPN routing. Oh, this week I'll be releasing a video on the Type 1 and Type 2 EVPN route types. It's going to be mega haha

[@dadelaar650]

Great thanks. I will definitely check them out.@@Netcademy

[@benedictagyemang3862]

Hello David, thanks for this amazing channels, I just found it and I am going to be a regular visitor to your channel.

[@Netcademy]

Absolutely loving this! Thanks for the amazing feedback. Lots more content to come and at some point I plan on showing Juniper solutions like Mist.

[@MrWinfil]

bien expliqué :) , thank you David.

[@Netcademy]

You’re welcome 👍

[@user-rv1ou3ke6q]

Tanks for such a detailed and clear explanation, if possible please make one video on route type 5.

[@Netcademy]

You’re welcome! Don’t worry it’s on my radar 👍

[@faisalak7]

thnk you

[@Netcademy]

You're welcome!

[@mohammedimran8855]

Hi, One of the best video I have found on the internet for VXLAN, only one question you mean to 2 to the power of 12? I hope so.

[@Netcademy]

Haha yes you’re correct. I remember making this mistake and cringed when I saw it. To confirm it’s 2^12 = 4096. Thanks for the support 👍

[@ZbyszekJot]

Nice, easily digestible video. Plus not in punjabenglish.

[@Netcademy]

haha glad to hear. Honestly sometimes I get tongue-tied and that can sound like a language in itself. Thanks for the support

[@cankaranisoner9208]

Greetings, first of all, thank you very much for an excellent video. I have a question in my mind. We talked about mapping VLANs to VNIs. Well, when I use 4096 vlans in the Data Center, there is no longer a vlan to map to VNI. How can I use 17 million VNIs like this? Can VNI alone work without VLAN? Or can I put a host into a VNI without including it in a VLAN (here is also confusing, how will an L2 switch do VNI operation)?

[@Netcademy]

Thanks for the positive feedback 👍 Answer to questions in order: 1 - Yes this makes sense as the vlan header is 12 bits which equals 4096. So if you try to create a vlan id of 4097 it’ll fail and thus there’s no vlan to map to a vni 2 - So vlan identifiers stop at 4096. A general good practice is to use vni’s from 5000+. So for example vlan 1 (default & native) could map to vni5000, vlan 10 to 5010 etc. 3 - so look at it from the case if that leaf device that’s mapping the vlan to the vni. It needs some traffic to map to that vni to carry (tunnel) over that layer 3 core. So you would need a vlan to map to a vni otherwise there’s no traffic both in & out for VXLAN to associate to that vni and transport over that vetp. However you could probably have other layer 2 traffic associated to a vni but I’ve not seen it heard of this. Finally, depending on vendor, the vlan id can be kept for advertisement between vtep’s with that vni or the vtep can strip it off. Hope that helps

[@mahikris9625]

Thank you so much David ... Very clear and Crisp explanation .. I watched this video like a suspense movie its like I started it and I don't want to stop it really 😀 However only thing which is NOT clear for me is the RT concept. I understood why we need RD but I couldn't appreciate why we need RT's ? what will happen if we don't have RTs ? Any good example you wanna showcase ?

[@Netcademy]

Hi, so this is actually explained in either part 2 or part 3 of this series. Part 1 is more about going over the fundamentals of EVPN routing and VXLAN tunnelling. However to answer your question directly the route target is a value, or really two values, which are configured to be routed in particular route update. These route updates contain various information including NLRI and path attributes (hello BGP). Now if the receiving device receives these EVPN packets and updates but do not have the RT defined, then simply it will drop those advertisements/ updates. Therefore for RT there are two areas - there is an export and import. The advertising device will advertise the update with an export RT and the receiving device MUST be configured with the same RT as the import.

[@rajeshdotaniya9113]

16 million i think not 17 milions, by the way thanks you so much for sharing informative information

[@Netcademy]

Well it's actually between 16-17 million. A lot of people say 16 million. In a later video I say it's just below 17 million. The exact number is 16,777,215. Wow that's a lot! Guess that's why no one says the exact number haha. Thanks for the great feedback :)