What is VXLAN || How VXLAN works || Ethernet Header || VXLAN Header || VXLAN Frame || What is vxlan
ฝัง
- เผยแพร่เมื่อ 1 พ.ย. 2024
- #what is #vxlan
#how VXLAN works in #datacentre
#overlay #network
#ethernet #header
VXLAN #header
#ethernet #frame
VXLAN #frame
#introduction to VX-LAN
#networking
Best video on VXLAN ever, many Thanks.
Thanks for your feedback
Excellent work Sir, waiting for next part of Vxlan video..
Very soon
Excellend work !!!, you breakdown the complex things & explain it in very digestible terms
Thanks a lot Abdul Ali
Thank you for your excellent explanation, Waiting for more videos on it.
Thank you Kazi
Sure I will....
Thanks a lot for excellent explanation and your hard work and dedication .... really appreciate your effort ...
Thanks
Great
Excellent work, waiting for next part of this series.
Thanks for watching.Yes i will upload subsiqent video...
Excellent brief thanks sir
Thanks for watching and your support.
Hi..nice.... (1)anyway how many vtep perswitch? (2)the mapping of vni and vlan 1:1? (3) do we need each vlan have its own multicast group to multicast the vxlan traffic?..Thanks
Your 3 query itself vast. its not possible to understand with this single basic VXLAN video that is what i will bring series, though you can check ACI series for now. below is the explanation. Thanks for watching please share and like.
1. A VTEP is responsible for encapsulating and decapsulating Ethernet frames into VXLAN packets and vice versa.The number of VTEPs per switch depends on the network design and requirements. In a VXLAN network, each switch that needs to participate in VXLAN-based communication will require a VTEP. Therefore, the number of VTEPs per switch will be equal to the number of VXLAN-enabled interfaces on that switch.In a typical VXLAN deployment, switches at the network edge (e.g., leaf switches) are the ones that often require VTEPs. Core switches may not need to encapsulate/decapsulate VXLAN packets and may only need to forward them between different VXLAN segments.
2.n some VXLAN deployments, you may have a one-to-one mapping between a VNI and a VLAN, where each virtual network is associated with a corresponding VLAN. This can simplify network design, as you can use VLAN IDs to correlate with VNI values.
However, it is not mandatory to have a direct one-to-one mapping between VNIs and VLANs. In more complex deployments, you might have multiple VNIs associated with a single VLAN, or a single VNI might span multiple VLANs.
3.In traditional VXLAN implementations, multicast groups were used for flooding VXLAN traffic in the network. Each VXLAN segment (identified by its VNI) was associated with a multicast group, and multicast-based replication was used to forward traffic to the appropriate receivers. This approach allows efficient multicast-based flooding within the VXLAN domain.
However, newer VXLAN implementations have evolved to use different forwarding mechanisms, such as unicast or ingress replication (also known as head-end replication), to avoid reliance on multicast for VXLAN traffic replication.
Boss , Pls Continue the Series , aka add other Parts
Hi Ali,
Thanks for watching...
Sure..
Just pause for LAB readiness..
Hi I have watched your complete video it was very informative. Can you please share the link for Part-2. I didn’t find it in your channel also
Thanks for watching. It's not uploaded yet..
@@tannetpro ok waiting for it… hope you upload ASAP……
Don't we have any routing protocol running in-between spine and leaf switches
Of course it is there only.
do we have part-2 for this series?
Stay tuned