How do I handle jumbo frames in industrial networks?

Jumbo frames are Ethernet frames larger than the standard 1518-byte MTU, typically 9000 bytes.

Benefits

• Better throughput for large transfers (fewer headers per data)
• Reduced CPU overhead on endpoints
• Useful for storage (iSCSI, NFS), backup, video

Considerations

• All devices in path must support and be configured for jumbo frames
• MTU mismatch causes silent drops — very hard to diagnose
• Some real-time protocols don't benefit (small packets)
• Fragmentation adds latency if MTU is exceeded

Configuration

Common sizes: 4470 (SDH inherited), 9000 (typical), 9216 (Cisco default when enabled).

Configure MTU on:

• Every switch port in the path
• Every host NIC
• Any routers or firewalls in path

Industrial Use Cases

• Historian data backup: Large transfers benefit
• Video surveillance NVR: Storage traffic
• PLC firmware updates: Occasional large files

When NOT to Use

• Real-time control (PROFINET IRT, EtherCAT) — small frames
• IEC 61850 GOOSE (already small)
• Mixed networks where some devices don't support

MTU Discovery Issues

Path MTU Discovery relies on ICMP "Fragmentation Needed" messages. Firewalls that drop ICMP cause connections to hang. Ensure ICMP Type 3 Code 4 is allowed on inter-subnet paths.

Testing

Use ping with DF (Don't Fragment) and size options: ping -M do -s 8972 target tests 9000-byte MTU (8972 + 28 header).