VXLAN encapsulation

The VXLAN encapsulation works as follows:

Source: https://docs.microsoft.com/en-us/windows-server/networking/media/Hyper-V-network-virtualization-technical-details-in-windows-server/vxlan-packet-header.png

The VXLAN with the RFC 7348 has increasingly become an industrial standard as most of the vendors support it out of the box. The protocol itself used UDP port 4789 as the destination port and the UDP source port is based on the hash information the the packet itself. The VXLAN header will be enhanced by a reserved 4-byte field and a 3-byte field for the VXLAN Network Identifier (VNI)-VSID-and finally another reserved 1-byte field. Finally, the VXLAN header adds the original CA L2 frame.

RFC 7348 can be accessed using this URL: http://www.rfc-editor.org/info/rfc7348.

The hierarchy from vSwitch to the VPH header can be described as follows:

The VFP technology supports MAC forwarding for VXLAN and NVGRE capsulation as well as VLAN forwarding using MAC. It always has a so-called slow path and a fast path for traffic transmission. The first package always needs to go through each layer of rules, but later on, the flow table will have a list of actions and will process it for all unified flow entries.

Table of Contents for VXLAN encapsulation

Create new playlist

Sign In

Sign Up

Table of Contents for
VXLAN encapsulation