Login or Register
FULL AI ANALYSIS

LAN devices intermittently lose connectivity after enabling jumbo frames on mixed‑vendor switches

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

Analysis summary

Symptoms indicate MTU mismatch / inconsistent jumbo frame support across the path (mixed vendor switches + LACP). When one hop uses MTU 9000 and another remains 1500, large frames are fragmented or dropped; LACP partner messages may indicate negotiation failures for aggregation settings. Fragmentation, DF handling, and offload interactions on ESXi can cause retransmits and partial outages for flows that exceed 1500 bytes.

Possible causes

MTU mismatch across switches and ESXi physical NICs causing dropped jumbo frames

95%

NIC offloads (GSO/GRO/TSO) on ESXi creating large frames that intermediate switches cannot handle

75%

LACP/port-channel negotiation differences between switch vendors leading to inconsistent hashing or path MTU handling

70%

Firmware bug on one switch that mishandles VLAN tagged jumbo frames or fragments larger than 1500 over trunks

25%

Suggested fixes

1

Diagnostic step 1

Document current MTU on every hop: on ESXi use esxcli network nic list and ethtool-equivalent output; on Linux servers use ip link show; on switches use show interface mtu or vendor CLI. Revert all devices to a consistent MTU (1500) as a safe baseline and verify stability before further changes.

2

Diagnostic step 2

In a maintenance window, enable jumbo frames end-to-end: set MTU=9000 on both switches, ESXi physical NICs, VM kernel adapters, and servers. Do one LAG/trunk at a time and monitor for drops.

3

Diagnostic step 3

Temporarily disable large send/receive offloads on ESXi and affected VMs (no data loss): on Linux VMs ip link set dev eth0 tx off rx off; on ESXi, consider advanced NIC offload settings. Check if packet fragmentation behavior changes.

4

Diagnostic step 4

Run tcpdump on ESXi uplink and on a server to confirm whether large packets are being truncated or dropped; capture TTL/hop MTU with tracepath to identify first-hop MTU mismatch.

5

Diagnostic step 5

If mixed vendors cannot reliably carry jumbo frames, prefer keeping MTU at 1500 and optimize other layers (e.g., jumbo only on single-vendor segment). If firmware or hardware limitations suspected, escalate to switch vendors with packet captures, LACP configs, and firmware versions recorded.

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