What is VXLAN || How VXLAN works || Ethernet Header || VXLAN Header || VXLAN Frame || What is vxlan

Рет қаралды 4,012

tannetpro

Күн бұрын

Пікірлер: 26

@abdulali5901 2 жыл бұрын

Excellend work !!!, you breakdown the complex things & explain it in very digestible terms

@tannetpro 2 жыл бұрын

Thanks a lot Abdul Ali

@tonybrar1126 4 ай бұрын

Best video on VXLAN ever, many Thanks.

@tannetpro 4 ай бұрын

Thanks for your feedback

@SyedNisarAhmed-s4c 5 ай бұрын

Excellent work Sir, waiting for next part of Vxlan video..

@tannetpro 5 ай бұрын

Very soon

@tanvirhri2726 Жыл бұрын

Thank you for your excellent explanation, Waiting for more videos on it.

@tannetpro Жыл бұрын

Thank you Kazi Sure I will....

@syednisar768 Жыл бұрын

Excellent work, waiting for next part of this series.

@tannetpro Жыл бұрын

Thanks for watching.Yes i will upload subsiqent video...

@guthipraveenkumar1229 Жыл бұрын

Thanks a lot for excellent explanation and your hard work and dedication .... really appreciate your effort ...

@tannetpro Жыл бұрын

Thanks

@arpandeyrock 2 жыл бұрын

Great

@balvir6 10 ай бұрын

Excellent brief thanks sir

@tannetpro 10 ай бұрын

Thanks for watching and your support.

@joeharyar9873 Жыл бұрын

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

@tannetpro Жыл бұрын

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.