Symptoms:

• vMotion fails with the error : 

• You may also see an error similar to:

 

• In the /var/log/vmkernel.log file, you see the error:
  
  vMotion vmknic is undefined.vMotion will attempt to proceed, but may not reach optimal performance.

Note: This can prevent a host from going into maintenance mode due to running virtual machines.

VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.0
VMware vSphere ESXi 7.0.0

This issue occurs if there is a mismatch between the Jumbo frame size in the physical network and the vmkernel MTU settings.

To resolve this issue, change the (vMotion) vmkernel MTU size to match the physical network interface.

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.

For information on changing the MTU size for a Standard Switch, see Change the Size of the MTU on a vSphere Standard Switch

Workaround:
You can perform the following solution as a workaround or troubleshooting step until you check physical network MTU size:

• Edit vMotion vmkernel and add default value 1500 instead of jumbo frames.

iSCSI and Jumbo Frames configuration on VMware ESXi/ESX
VMware ESXi 6.x にアップグレードすると vMotion がエラー「Failed waiting for data. Error 195887179. Connection reset by peer」で失敗する
在 ESXi 6.x 中，vMotion 失败并出现错误“等待数据失败。 错误 195887179。 连接由对等重置”