To resolve this issue, change the (vMotion) vmkernel MTU size to match the physical network interface.
- You can use vmkping tests with the packet size and do not fragment flags to verify MTU size, e.g. 8972 for MTU 9000 or 1472 for MTU 1500
- Example:
vmkping -I vmk2 -s 8972 -d <destination IP>
- Note: When dealing with MTU issues, ensure every interface in the packet path is using the same MTU value. For example, this issue can occur when the vMotion vSwitch has a different MTU than the vMotion vmkernel port.
Workaround:
You can perform the following solution as a workaround or troubleshooting step until you verify physical network MTU size:
- Edit vMotion vmkernel and add default value 1500 instead of jumbo frames.
Note: It is still recommended that you set every interface in the packet path to the exact same MTU value (vmkernel and physical interface).