1. What is Geneve? (The Big Picture)
Geneve (Generic Network Virtualization Encapsulation) is a tunneling protocol. Its job is to take an Ethernet frame from a VM (Layer 2) and "wrap" it inside an IP packet (Layer 3) so it can travel across your physical network switches and routers.
The "Envelope" Analogy:
The Letter: The original data being sent by your VM.
The Envelope: The Geneve Header (contains the Network ID/VNI).
The Shipping Label: The UDP/IP Header (contains the TEP IP addresses of the physical hosts).
2. How the Packet Moves (Step-by-Step)
Communication happens between two TEPs (Tunnel End Points). A TEP is simply a special IP address assigned to your ESXi host specifically for this purpose.
Encapsulation (The Wrap): VM-A on Host 1 sends a packet. Host 1 sees the packet, realizes it's destined for an Overlay network, and wraps it in a Geneve Header.
Transmission (The Journey): The host sends this as a UDP packet over Port 6081. To your physical Cisco or Arista switches, this just looks like standard web-like traffic between two servers. They don't see the VM traffic inside.
Decapsulation (The Unwrap): Host 2 receives the packet on its TEP IP, strips off the Geneve "envelope," and hands the original clean Ethernet frame to VM-B.
3. Why Geneve? (Vs. VXLAN)
In the old days of NSX-V, we used VXLAN. So why the change? One word: Flexibility.
VXLAN had a "Fixed" header. If VMware wanted to add a new feature (like a security tag), they couldn't fit it in the header without breaking the protocol.
Geneve is "Extensible." It uses TLV (Type-Length-Value) fields. This means VMware can add "Metadata" (extra info) to the header whenever they want. It’s like an envelope that can expand to hold extra documents without needing a new mailbox.
4. Deep Dive: The Geneve Header Format
The header is designed to be lightweight but powerful. Here are the key components your readers should know:
UDP Port 6081: This is the standard "door" Geneve uses to enter and exit.
VNI (Virtual Network Identifier): A 24-bit number. This is the "ID Card" of the segment. With 24 bits, you can have up to 16 million separate networks (compared to only 4,094 with traditional VLANs).
Options (The Secret Sauce): This is the variable part of the header (0 to 252 bytes). This is where NSX stores metadata for advanced features like distributed tracing or security context.
5. Critical Requirements for Success
If you are a Consultant setting this up, there are two "Golden Rules" you cannot ignore:
A. The MTU Rule (Minimum 1600)
Because Geneve adds an "envelope" around the original packet, the packet gets bigger. A standard packet is 1500 bytes. With the Geneve header, it can grow up to 1550+ bytes.
Result: You must increase your physical network MTU to at least 1600 bytes (though most professionals set it to 9000 for Jumbo Frames) to prevent the network from dropping or fragmenting the packets.
B. Hardware Offloads
Even though Geneve is software-defined, it can be CPU-intensive for the host to "wrap and unwrap" millions of packets per second.
The Fix: Modern NICs (Network Interface Cards) support Geneve Offload. This means the hardware on the NIC does the wrapping/unwrapping, freeing up the CPU for your VMs.
6. Key Benefits for the Enterprise
Control Plane Independence: Geneve doesn't care if you use NSX, KVM, or a third-party controller. It’s an open standard.
Standard Tool Support: You can troubleshoot Geneve traffic using familiar tools like Wireshark or tcpdump, which are fully capable of "looking inside" the Geneve envelope.
ECMP Ready: Because Geneve uses UDP, physical routers can use Equal-Cost Multi-Pathing (ECMP) to spread the traffic across multiple physical links, preventing bottlenecks.
Comments
Post a Comment