FULL AI ANALYSIS

Managed switch drops 802.1Q tagged frames on trunk when MTU set above 1500 to ESXi host

Generated Oct 3, 2026, 12:35:03 AM

Analysis summary

The behavior indicates an MTU mismatch or device limitation where the switch either does not account for the extra VLAN tag bytes when performing MTU checks or its hardware forwarding path cannot handle jumbo frames that include 802.1Q headers. Some lower-end managed switches compute MTU per physical payload and erroneously drop frames when VLAN overhead pushes frame size beyond internal thresholds, or their CPU-based VLAN processing path cannot handle large frames at wire speed. Since lowering MTU on ESXi fixes the issue, the problem is either a device firmware limitation or a misconfiguration across link endpoints.

Possible causes

Switch firmware/hardware bug that drops tagged jumbo frames or treats 802.1Q-tagged frames as exceeding MTU.

95%

Switch uses CPU-based processing for VLAN tagging that cannot handle large frames at line rate and drops them silently.

75%

NIC offload features on ESXi (GSO/TSO) producing frames larger than the switch can handle, causing network fragmentation failures.

30%

MTU configured inconsistently across all devices in the path (ESXi, intermediate switches, storage targets), including not accounting for 4‑byte VLAN tag.

20%

Suggested fixes

Diagnostic step 1

Verify MTU end‑to‑end, accounting for VLAN tag: when testing, use iperf3 with --mtu or ping with large payload and DF flag to locate first-hop drop. Ensure MTU is set consistently on ESXi pNIC, vSwitch, vmkernel interfaces, physical switch trunk ports, and any downstream switches.

Diagnostic step 2

Temporarily set MTU to 9000 on both ends of a single trunk link and test only that link to prove whether the issue is localized to one switch model/port.

Diagnostic step 3

Disable NIC offloads (GSO/TSO/LRO) on ESXi for a test to see if that affects frame sizes sent to the switch.

Diagnostic step 4

Update the managed switch firmware to the latest recommended release and review vendor release notes for jumbo frame and VLAN fixes; if vendor confirms a hardware limitation, consider replacing with switch model supporting tagged jumbo frames in hardware.

Diagnostic step 5

If replacing switch is not immediate, consider using a separate VLAN or link for jumbo‑enabled traffic only across devices that support it, or set MTU to 1600 on all devices if storage workloads only require slightly larger frames.

Contact • Help • API Docs • Careers • Terms • Privacy • Cookies • Ads