In vSphere architectures, networking often feels like an abstraction layer disconnected from physical reality. However, when latency spikes occur or packets are dropped during vMotion, understanding the literal physical traversal of frames across virtual switches is crucial.
1. From vNIC to Distributed Port (dvPort)
When a guest operating system writes an Ethernet frame to its virtual NIC (typically vmxnet3),
the driver performs zero-copy ring buffer writes into VMkernel shared memory. The frame arrives at the
distributed port assigned to the VM on the local host proxy switch.
2. Teaming & Failover: Route Based on Physical NIC Load (LBT)
Unlike static LACP or Port ID hashing, Route Based on Physical NIC Load (Load-Based Teaming) dynamically monitors uplink traffic. If a physical uplink exceeds 75% utilization over a consecutive 30-second window, the VMkernel migrates the offending virtual port to a quieter uplink:
3. Physical Uplink Traversal & MTU Boundaries
When packets leave the hypervisor, jumbo frames (MTU 9000) are vital for storage networks (vSAN, iSCSI, NFS) to minimize interrupt frequency. Always ensure the entire packet path—vNIC, VMkernel port, vDS, switch port, and storage controller—shares identical MTU settings.
4. Debugging Drops with pktcap-uw
If packets are dropping before reaching the physical wire, pktcap-uw is the most granular
diagnostic tool in the ESXi engineer's arsenal:
.pcap file via SCP and open it in Wireshark with the
tcp.analysis.flags display filter to instantly isolate TCP retransmissions or out-of-order
deliveries.
vSphere 9.1 Licensing Update: The vSphere Distributed Switch (VDS) is now included in Broadcom's entry-level 128-core pack! Read our VMware vSphere Express 9.1 Licensing Breakdown to see how VDS, HA, and vMotion are bundled.