topic Re: vMotion issues in VMware vCenter™ Discussions

vMotion issues

seanm1832 — Mon, 29 Feb 2016 14:21:47 GMT

Having issues doing a vMotion, has anyone any insight into the errors below?

Migration [-1062724889:1456753412128804] failed to connect to remote host <10.0.0.17> from host <192.168.26.228>: Timeout.

vMotion migration [-1062724889:1456753412128804] vMotion migration [-1062724889:1456753412128804] stream thread failed to connect to the remote host <10.0.0.17>: The ESX hosts failed to connect over the VMotion network

The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration.

vMotion migration [-1062724889:1456753412128804] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

Failed waiting for data. Error 195887167. Connection closed by remote host, possibly due to timeout.

Re: vMotion issues

photofalk — Mon, 29 Feb 2016 15:39:16 GMT

Hi,

there is a bad vmk configuration in your cluster.

Migration [-1062724889:1456753412128804] failed to connect to remote host <10.0.0.17> from host <192.168.26.228>: Timeout.

The vMotion cabability is enabled on vmKernels in different subnets.

One of your hosts has vMotion enabled on the VMK with the following IP address: 10.0.0.17

The second host has vMotion enabled on the VMK with an IP address of the 192.168.26.0 subnet.

I think your hosts have multiple VMKs. Please enable vMotion only on VMKs which are in the same Subnet (10.0.0.0 or 192.168.26.0)

Greetings

Falk

Re: vMotion issues

vmEck — Mon, 29 Feb 2016 15:44:21 GMT

What version of ESX? If you're on 6.0 then we can route vMotion traffic. But the underlying network has to be able to route between those two subnets. If not on v6 then photofalk has it covered.