How its is decide that which vtep join in multicast group, as if host -1 send packet to Host-2 first time then , how fabric sw-2 vtep know that it has to join the same multicast grp, which sw-1 joined ?
You manually configure on the VTEP what multicast group to join and this has to be consistently configured across the VXLAN on each switch. You may choose to configure a different multicast group per VXLAN or you can choose to configure the same group across all VXLANs it depends how you wish to scale. If you choose the same group the switch will inspect the multicast packet for the VNI (VXLAN) to see if has the VNI and if it needs to act even if it does not have the the VNI. Or you can increase the amount of multicast groups so switches only receive BUM traffic they require at the cost of more multicast groups. Edit: Typo
Hi Lewis, As I am new to vxlan having few doubts. Could you plz let me know mapping of vlan 10 to vxlan 10010 in sw-1 and vlan-20 to vxlan 10020 in sw-2 is it a inter vlan communication happened or same vlan communication happened bit confused . As per my understanding same vlan-10 should be mapped to vxlan 10010 in sw-1 and sw-2 then host1 and host2 can communicate which are having same vlan as well as same vxlan I'd in overlay network? Plz correct me . Could not get the correct answer from anyone else. Hope you clear my doubt..
You have a gift to breakdown complex things & explain them in very digestible terms. Can you please make a video on BGP-EVPN & how it all works together with VxLAN?
This is the closest I've got to understanding VxLAN. I'm looking forward to understanding BGP EVPN also as I have to automate few testcases. Need to understand what exactly the whole configuration is doing. Thank you so much.
Very good overview. This is what i needed, an overview, not enough to try to design my own, that said, this alone helped me troubleshoot an issue with my hosts in a UCS environment (some hosts were missing VTEP vlan on the adapters on one fabric)!
Your spine device is supporting your leaf switches connectivity. It needs the features that will allow your underlay routing of choice to provide full reachability of all interfaces/loopbacks you intend to use to build the VXLAN overlay on and it needs to support the physical media depending on the connectivity types/speed. Typically the spine is going to be high speed connectivity for east/west traffic. You would be using leaf switches to bring connectivity in from the user traffic connecting into the overlay, you're north/south traffic.
Yes as long as you have end to end reachability you can use anything to do the underlay routing. consider you will not have dynamic routing for fail over though so your tunnels will only form over the static path.
Thank you Its a great video understood concept. Could you please do a continuation video with BGP EVPN in terms of data center traffic flow like spine, tor, ger thank you.
At 5:10, you talk about having 2 different VLANs on the same VNI being able to talk to eachother, where the VLAN numbers are different but the VNI is the same. Is it possible to have 2 VLANs with the same number (VLAN10 and VLAN10) on 2 different VNIs (10010 and 10020), which therefore would mean that there are two things I'm calling VLAN10 but that can't get confused with one another by the rest of network?
Hey, on a different switches it is possible to have two different vlan ID but make them belong to same VNI. Probably not a good thing to do but possible to configure and communicate across. If you configured two different VLANs on different switches and make them use two different VNI then you wouldn't have layer 2 Comms on them. The same goes if you used the same VLAN on different switches but used different VNI for this VLAN on each switch, you wouldn't get layer two Comms between them. This is providing you are using VXLAN tunneling to communicate and not using a trunk between the switches.
Great video, nice explanation.. A question : is this EVPN-VXLAN only used to interconnect datacenters? Is it being used to create a HQ-Branches WAN overlay network?
Lewis, do you have some configurations of each device in this example? How would I do this with a 3 tier design using a legacy vPC layout? Also, I am confused as to where do the gateways live for each of these vlans associated with each VNI? Thanks mate!
Hey sorry for the delay, I haven't been involved with using three tiers aka using "super spines" generally it allows you to scale further. The VTEP is still at the leaf so you are effectively adding more bandwidth to a solution is my understanding. VXLAN is able to be built out over an IP network as long as your edge devices support the VXLAN features. You also need to consider Multicast or Ingress replication on your legacy IP network acting as the underlay. If you are trying to build out a VXLAN design on a legacy 3-tier design I would suggest adding another distribution layer off your core or connect to the core with a new VXLAN designed focused on a well supported design approach like a CLOS topology. For your gateway question using distributed anycast IP, this will act as your gateway. The IP address is identical on all your switches and has the same MAC address defined this is configured consistently for each of your VXLAN. This will allow the host to arrive on any of your switches and able to use the default gateway based on the information the host has already cached. How you route that over tunnels can be done using symmetric or asymmetric IRB which you should understand. I do not have any configuration I can share for this, however there are many good examples using Google that break down sections of the configuration
Hi Sarvesh, The book Building Data Centers with VXLAN BGP EVPN: A Cisco NX-OS Perspective is very good and the only book I have gone through for this. Other than that I have used odd bits off Google searches and blogs.
Some applications/storage solutions still use L2 would be one use case. Ideally you would leave the L2 domain at the top of rack and keep it simple but it all depends on the needs.
Hi Prateek, the Cat9500 and Nexus 9300's are quite similar in price I believe and at the moment you don't have to buy DNS licensing for the Nexus. Off the top of my head the 9500's are capable of VXLAN but I haven't looked into it in much detail. Thanks for watching!
Taking the concept of VXLAN - we can go further and use VX-WAN. We can extend a WAN in a virtual WAN and virtual tunnels across thousands of WAN. With this growing we will reach the overlay layer so we can virtually manage all the network of the planet by software defined. And YANG data modelling will "unify" all of the networks across the globe. The unify language RFC6020 will be the unique language overlaying the physical networks. The Nature - the Tree concept and the analogy with the Nature it´s the unification of everything. This is just the beginning of "Trees". VXLAN it´s the Evolution, like Darwin said: species have the capacity for adaption and evolution. The Trees - the Spines - will grow into more Leafs. and leafs will generate leaves. I believe that prime numbers factorization will be applied in networks topologies as a tree selection hierarchy. Primes numbers are factorized and we can built a tree topology.
Hey, thank you. I have been meaning to pick up the channel again. I'd like to go a bit further into it on the channel hopefully I will make some time to do some more videos soon
Hope it's clear and gives you an understanding how the east-west comms works, if you have any questions let me know.
How its is decide that which vtep join in multicast group, as if host -1 send packet to Host-2 first time then , how fabric sw-2 vtep know that it has to join the same multicast grp, which sw-1 joined ?
You manually configure on the VTEP what multicast group to join and this has to be consistently configured across the VXLAN on each switch. You may choose to configure a different multicast group per VXLAN or you can choose to configure the same group across all VXLANs it depends how you wish to scale. If you choose the same group the switch will inspect the multicast packet for the VNI (VXLAN) to see if has the VNI and if it needs to act even if it does not have the the VNI. Or you can increase the amount of multicast groups so switches only receive BUM traffic they require at the cost of more multicast groups.
Edit: Typo
@@LewisBowerbank Thanks for replying , if i have more queries, can i ask again ?
@@vikrantpandey569 sure no problem
Hi Lewis,
As I am new to vxlan having few doubts. Could you plz let me know mapping of vlan 10 to vxlan 10010 in sw-1 and vlan-20 to vxlan 10020 in sw-2 is it a inter vlan communication happened or same vlan communication happened bit confused .
As per my understanding same vlan-10 should be mapped to vxlan 10010 in sw-1 and sw-2 then host1 and host2 can communicate which are having same vlan as well as same vxlan I'd in overlay network?
Plz correct me . Could not get the correct answer from anyone else.
Hope you clear my doubt..
Best video on youtube for understanding VXLAN. Big thumbs up!!
Well done mate! I understood the whole concept in 10min's.
Excellent job in explaining the complex stuff so easily in step by step manner 👍
You have a gift to breakdown complex things & explain them in very digestible terms. Can you please make a video on BGP-EVPN & how it all works together with VxLAN?
Thx - brilliant technical delivery -- just the right details -- hope you've gone in details in the next series --!
This is the closest I've got to understanding VxLAN. I'm looking forward to understanding BGP EVPN also as I have to automate few testcases. Need to understand what exactly the whole configuration is doing. Thank you so much.
Great I'm glad it helped you! Good luck with your BGP EVPN research.
Very good overview. This is what i needed, an overview, not enough to try to design my own, that said, this alone helped me troubleshoot an issue with my hosts in a UCS environment (some hosts were missing VTEP vlan on the adapters on one fabric)!
That's cool, glad it helped you out!
Really superb explanation, I went through many videos but here my concept cleared 👍
Any more videos u can share on DC..?
@@ramkrish9098 Hi Ram Krish, I will be picking my videos up again very soon. Sorry for the late response I did not see your question.
Amazing explanation.
Job well done.
Perfect Explanation Ever!!!!!!
Very nice explanation. Thank you
Awesome presentation: clear, precise and direct.
Thx U!
Great explaination. Clear and very concise!
Thanks, I'm glad you found it useful
Fantastic video! Thank you very much!
Great explanations, thanks!
Nice work, easy enough to work it through, thanks.
fantastic! one of the best ten minutes.
splendid explanation ...Must say ..Thank You
Short and bang on target. Very good video.
fantastic overview - thank you!
great explanation
nice clean and on point...useful for any beginner to get an fair idea. Keep posting.
Best explanation
This is amazing work !
Thats a gold video lewis.
SuperB Explanation!!!
So neat. Thank you Lewis!
I'm glad you liked it, thanks for watching Mey
greate, step by step brieft
useful video. short and crisp
Very Well Explained
very helpful thank you so much
very clear. Appreciated
Hii lewis ,can you please upload bgp evpn as u mentioned last in above video i undertood above
Thank you!
What is the spine device? can it be any layer 3 device in between the sites? (SDWAN, MPLS, IPSEC)
Your spine device is supporting your leaf switches connectivity. It needs the features that will allow your underlay routing of choice to provide full reachability of all interfaces/loopbacks you intend to use to build the VXLAN overlay on and it needs to support the physical media depending on the connectivity types/speed. Typically the spine is going to be high speed connectivity for east/west traffic.
You would be using leaf switches to bring connectivity in from the user traffic connecting into the overlay, you're north/south traffic.
Hi Lewis ..With static route between SW1, SW2, Spine Switch is it possible to create VTEP tunnel ?
Yes as long as you have end to end reachability you can use anything to do the underlay routing. consider you will not have dynamic routing for fail over though so your tunnels will only form over the static path.
Clear enough. Thanks.
Thank you Its a great video understood concept. Could you please do a continuation video with BGP EVPN in terms of data center traffic flow like spine, tor, ger thank you.
nice explanation !!
At 5:10, you talk about having 2 different VLANs on the same VNI being able to talk to eachother, where the VLAN numbers are different but the VNI is the same. Is it possible to have 2 VLANs with the same number (VLAN10 and VLAN10) on 2 different VNIs (10010 and 10020), which therefore would mean that there are two things I'm calling VLAN10 but that can't get confused with one another by the rest of network?
Hey, on a different switches it is possible to have two different vlan ID but make them belong to same VNI. Probably not a good thing to do but possible to configure and communicate across.
If you configured two different VLANs on different switches and make them use two different VNI then you wouldn't have layer 2 Comms on them. The same goes if you used the same VLAN on different switches but used different VNI for this VLAN on each switch, you wouldn't get layer two Comms between them. This is providing you are using VXLAN tunneling to communicate and not using a trunk between the switches.
Thank you so much, you are the men! :D
Awesome!!!
Great video, nice explanation..
A question : is this EVPN-VXLAN only used to interconnect datacenters? Is it being used to create a HQ-Branches WAN overlay network?
Lewis, do you have some configurations of each device in this example? How would I do this with a 3 tier design using a legacy vPC layout? Also, I am confused as to where do the gateways live for each of these vlans associated with each VNI? Thanks mate!
Hey sorry for the delay, I haven't been involved with using three tiers aka using "super spines" generally it allows you to scale further. The VTEP is still at the leaf so you are effectively adding more bandwidth to a solution is my understanding.
VXLAN is able to be built out over an IP network as long as your edge devices support the VXLAN features. You also need to consider Multicast or Ingress replication on your legacy IP network acting as the underlay.
If you are trying to build out a VXLAN design on a legacy 3-tier design I would suggest adding another distribution layer off your core or connect to the core with a new VXLAN designed focused on a well supported design approach like a CLOS topology.
For your gateway question using distributed anycast IP, this will act as your gateway. The IP address is identical on all your switches and has the same MAC address defined this is configured consistently for each of your VXLAN. This will allow the host to arrive on any of your switches and able to use the default gateway based on the information the host has already cached. How you route that over tunnels can be done using symmetric or asymmetric IRB which you should understand.
I do not have any configuration I can share for this, however there are many good examples using Google that break down sections of the configuration
Hi Lewis thanks for the video. can you please advice me where can I find more literature on VXLAN.
Hi Sarvesh, The book Building Data Centers with VXLAN BGP EVPN: A Cisco NX-OS Perspective is very good and the only book I have gone through for this. Other than that I have used odd bits off Google searches and blogs.
Hello, can I ask you why is it good to tunnel L2 these days when everything uses IP?
Some applications/storage solutions still use L2 would be one use case. Ideally you would leave the L2 domain at the top of rack and keep it simple but it all depends on the needs.
Thanks Lewis!, can spine-leaf fabrix be created by new Cat 9500 or we only can do it with nexus series
Hi Prateek, the Cat9500 and Nexus 9300's are quite similar in price I believe and at the moment you don't have to buy DNS licensing for the Nexus. Off the top of my head the 9500's are capable of VXLAN but I haven't looked into it in much detail. Thanks for watching!
What a pity you haven't done a second presentation about BGP EVPN. Geetings
Thanks for watching, sorry I do want to come back to this and resume the channel.
Taking the concept of VXLAN - we can go further and use VX-WAN. We can extend a WAN in a virtual WAN and virtual tunnels across thousands of WAN. With this growing we will reach the overlay layer so we can virtually manage all the network of the planet by software defined. And YANG data modelling will "unify" all of the networks across the globe. The unify language RFC6020 will be the unique language overlaying the physical networks. The Nature - the Tree concept and the analogy with the Nature it´s the unification of everything. This is just the beginning of "Trees". VXLAN it´s the Evolution, like Darwin said: species have the capacity for adaption and evolution. The Trees - the Spines - will grow into more Leafs. and leafs will generate leaves. I believe that prime numbers factorization will be applied in networks topologies as a tree selection hierarchy. Primes numbers are factorized and we can built a tree topology.
Great effort mate, clear my concepts, do you have any video regarding BGPEVPN in VXLAN?
Hey, thank you. I have been meaning to pick up the channel again. I'd like to go a bit further into it on the channel hopefully I will make some time to do some more videos soon
@@LewisBowerbank Thanks i will wait :)
Is it possible to map multiple VLANs to a single VNI?
Why do ppl make nice channels, upload few nice videos and then just run away? Lewis would you please enlighten me?
I will come back to it soon, it has been far too long...
あなたが好きなすべてのグループメンバーに投票することができます
Young Donald Rodriguez Jason Wilson Laura
Miller Daniel Brown Amy Garcia Margaret
Young Eric Davis Elizabeth Robinson Ronald
你的口音让我想起了我远在苏格兰的奶奶。视频很棒。
Bum traffic lol
Again in english please?...