Failed to vMotion – What does VSAN have to do with it?
vMotion migration [167772244:1439137055175670] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout
Migration to host <10.0.0.66> failed with error msg.vmk.status.VMK_MIG_CONN_CLOSED (195887167).
Migration [167772244:1439137055175670] failed to connect to remote host <10.0.0.84> from host <10.0.0.66>: Timeout.
vMotion migration [167772244:1439137055175670] failed to create a connection with remote host <10.0.0.84>: The ESX hosts failed to connect over the VMotion network
Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.
Those have seen error 195887371 know it as the great MTU mistake where the MTU sizes don’t match up and vMotion fails to work properly. However, what was interesting about this error message is it references my VSAN’s VMkernel network. I flip over to the vCenter web interface and eye spy with my little eye that the VSAN VMkernel also is enabled as vMotion interface. Well that can’t be! I admittedly don’t know why or how this happened but case closed, problem solved.
Rookie mistake? Probably, but it happens to the best of us.