VXLAN Explainer 1
Вставка
- Опубліковано 14 лип 2024
- 📚VXLAN Use cases
💻Aruba AOS-CX VXLAN Config
🔍Encapsulation Deep Dive with 🦈 wireshark
⛓Links
👉datatracker.ietf.org/doc/html...
👉datatracker.ietf.org/doc/html...
⏰Timestamps:
00:00 Intro
00:17 VXLAN use cases
08:04 Aruba AOS-CX VXLAN config example
15:48 VXLAN packet deep dive with wireshark
22:32 A word about the state of the VXLAN header
24:38 Live packet capture
🐦
/ joeneville_ - Наука та технологія
These are awesome! Thank you Arubans for making these! "We're so excited about it, we're shouting about it"
One of the best videos for VXLAN explained step by step. Thanks and keep up the good work!
Can’t find simpler explanation anywhere. Great job.
One of the best, well structured, please keep posting more videos !!!
Same comment as below... One of the BEST videos about VXLAN explained step by step.
Many thanks for dedicate your time to explain for us.
Explained very clearly. I watched lots of videos about vxlan, and this is the best one.
Very good overview and explanation Joe, thanks!
Thanks Joe, love the delivery and content.
Very good Joe, thanks for the quality of the explanation.
I just love watching your videos. it is so engaging I just dont get bored. Please post more videos.
NICE work Joe!!! Thanx for the work / post :-)
Awesome! Best intro, just configure the tunnel and see how vxlan works!
been waiting for this! Great job Joe! :D
To the end, brother, your hair looks great. Thank you for your explanation
Excellent video. Thank you for making it so simple to understand.
Excellent video on Static VXLAN. Thanks
Once again, great video! Loving the content.
Excellent - I work with a network that is now 70% cx, as the network develops to 100% the use of vxlan will be a game changer
Great detailed video Joe, thank you
Cheers John!
Thanks for this content. It helps to clearly understand the concept.Appreciate this!
Nice video dude! Smooth end transition... SO REAL 😂
Ah, well, you might not believe this, but it isn't actually real. That's the magic of editing. 🪄🎩🐇
看到最后，小哥哥你的发型很帅，谢谢你的讲解
excelent video ! the first layer of the onion
Very well explained, a great video. Thanks
Thanks Joe
phew...Finally, someone explained from the very basic....Thanks
Excellent!! Thank You!!!
Very good explanation...
Well presented!
Absolute Clarity
Nice explained.Thanks
Great video!
Thankyou this explained a lot
Great explanation :)
Very nice 👌
Very well explained! Will the future parts be more centered around Campus or DC use cases? I would like to see more of VXLAN in the Campus network, especially since there a lot of videos regarding Spine/Leaf and DC use cases already out there.
Thanks! My approach is really about the protocol rather than the implementation. Understand the headers, encap and such like, then the implementation is a secondary concern.
But I do take your point about campus, and will try not to just replicate all that other 'VXLAN in the DC' content.
Thanks for the comment, that's a useful point of view to bear in mind for my planning.
This is great,
Hoping to see video that would give pointers how to build a large campus network with EVPN. All the documentation/examples are usually with only few switches but how does it work when there is 2000 switches? I guess something along line mostly using RT5 and not advertising RT2 and something like this?
thanks
14:03 I wish you captured the arp requests going over the vxlan interface to the peer and back, since this action takes place before the icmp can ever work.
Very good start with the simplest explanation possible. I will definitely go ahead with the rest of your videos. But one curious question- u started config with a condition that the ping was not working between servers but I did see that vlan 1 was passed as the native vlan on both of the switches on all interfaces facing each other as well as ubuntu server. How did u made the ping
stop in first place ?
I feel the 6300s don't have routes to reach the destination
Loving this content, where can I found more of these? I work with Cisco devices but man, this explanation was a game changer.
Thanks, there is a playlist here: ua-cam.com/play/PLsYGHuNuBZcZB8nMxgPwGlGEUscwP_RNH.html
Amazing. Can i use the vsx/active gateway IP on both sides as the vni source/destination ip? Is it supported?
Thanks for nice video. I have doubt how did you setup L3 network between two L2 switch in ping demo.
Good job👏, and for curious, what is the network emulating application you have used in the video?
Thanks. That's recorded on actual hardware (aruba 6300s).
Thanks for the video, @1:36 why are you adding a layer 3 link between the switches ? That should be a regular layer 2 trunk link….
It is L2 between the switches, the IP addressing is for the full end-to-end connection, from node1 to node2.
Thank you for this video> I had a very hard time wrapping my mind around VXLAN till now.
Now how does each side handle default gateways? For example, lets say the sides are at seperate but near by datacenters (Major city like Dallas, which a VPLS link). Side A has a GW of .254. Would Side B also use that same default gateway? Or would there be some other kind of method of using the same default gateway? Or would side by use a different default gateway.
VXLAN being data plane, if you’re talking inter-subnet flows (using a gateway) there’s a number of options.
Old style would be an IP only centralised router on a stick, here a VTEP decaps the VXLAN, passing IP traffic to a router, that routes then forwards back to the VTEP.
A better approach is to introduce EVPN for the control plane, with this you can utilise integrated routing and bridging (IRB) and anycast gateways.
Basically the VTEPs are able to route between subnets plus they are configured with a virtual IP and MAC address so that all the VTEP can route but the end clients only need to be configured with a single default gateway.
( yes, there is a lot of work involved in fixing the issue that you raise) 😅, but it’s all a part of EVPN-VXLAN.
@@null_zero Understood. I get how the any cast gateway can route out. But lets say you have a 3rd party connection coming into a set of servers that are on this EVPN-VXLAN, and it comes into the anycast gateway for the correct site, does the anycast gatyeway have a full mac/arp table of which macs are on which VTEP?
@@seantellsit1431 This detail comes from the type of IRB configured for EVPN. There’s two types:
1/ with asymmetrical IRB, the VTEP gway is configured with every VLAN/subnet/VNI that is can route to. The VTEP does carry the MAC and ARP table for all destination VLAN/subnets. This does not scale well because of all the finite resources on the VTEP that carrying those tables burns up.
2/ Symmetrical IRB - the VTEPs are only configured with, and carry the tables of, the locally attached VLAN/subnet PLUS a shared VNI. VTEPs use RT-5s to advertise IP prefixes, rather than needing all MACs to be advertised. When routing, the symmetrical VTEP can use the IP prefix to direct packets to the destination VTEP, and it uses the shared VNI to VXLAN encap the traffic. Note that because it is not configured with the destination VNI-VLAN mapping, it uses this shared VNI to transport the traffic to the destination VTEP, which then does the lookup to drop the packets onto the correct VLAN.
Symmetrical is more complex but more scalable because the VTEP only carries the local MAC/ARP tables.
Hang around for the transition at the end.
Liked that! Same for the rest of the video. Like with many things, when explained like this, it is not that hard to understand. You just need to get it. I got it.
@@hermanrobers Thanks Herman. It is just simple encapsulation of L2 in L3 (UDP) at its heart.
@@null_zero For future video topic, VXLAN and IPv4 multicast on the overlay
I am new to the VXLAN side of things. Regarding attaching VNI's to Vlan's, if we can have so many more VNI's than Vlan's (4096) - what happens when this number is exceeded. I've obviously missed something very simple here, but i don't know what :)
The large number of VNIs helps support multiple customers on shared infrastructure.
Imagine two customers are using the same VXLAN network, which is run by a third-party. Customer A uses VLANs 100-200, customer B also uses VLANs 100-200. The large number of VNIs means the third party can assign VNIs for both customers, and these can be values that are not 100-200, we can decouple local VLAN ID from VNIs.
So nothing actually “happens” the VNIs are just IDs.
Hi Joe ,cotton eye joe?
Where can I download the aruba simulator software?
asp.arubanetworks.com/downloads/software/RmlsZTpjYzU1YTdhYS1mMzBlLTExZWMtOTIxOC1jZjBjNDk2ZmU3ZTM%3D
Russel Brand knows networking?