This article provides information about enabling Jumbo Frames in a virtual switch, vDS, and VMkernel adapters.
Note: If vmkernels on a virtual switch are set to 9000 MTU, the virtual switch must also be set to 9000 MTU. However, if the virtual switch is set to 9000 MTU, it is not a requirement to set all vmkernels on the virtual switch to 9000 MTU.
Note: Ensure that the network card, physical switches, and storage devices support Jumbo Frames before configuring.
Note: With vCenter Server 7.0 Update 3, you can set the size of the maximum
transmission unit (MTU) on a vSphere Distributed Switch to up to 9190 bytes
to support switches with larger packet sizes.
Note: With vCenter Server 7.0 Update 3, you can set the size of the maximum
transmission unit (MTU) on a vSphere Distributed Switch to up to 9190 bytes
to support switches with larger packet sizes..
Changing the MTU on a virtual switch does not automatically change the MTU on VMkernel adapters.
For more information on configuring Jumbo frames, see iSCSI and Jumbo Frames configuration on ESX/ESXi (1007654). Jumbo frames must be configured similarly across the board on both virtual and physical infrastructure, such as vSwitch, Portgroups, VMkernel, and physical switch port.
For more information on troubleshooting host Jumbo Frame issues, as well as how to test that Jumbo Frame connectivity is working as it should be, see Troubleshooting disk latency when using Jumbo Frames with iSCSI or NFS datastores (2002197).
iSCSI and Jumbo Frames configuration on VMware ESXi/ESX (318937)
Troubleshooting disk latency when using Jumbo Frames with iSCSI or NFS datastores (2002197)
Impact/Risks:
Changing the MTU size on a vDS temporarily brings the attached physical NICs down and back up, causing a brief network outage on the vDS.