vmotion stops at 14% on one ESXI 5.1 host . vmotion appears to work on all other hosts in cluster

[thomasross]

When I try to vmotion a running VM on one esxi host, i get:

"A general system error occurred:

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. "

A powered off VM vmotions just fine.

running ps |grep vmotion shows "8881 vmotionserver"

I cannot ping any other vmotion vmkernel IP addresses from this ESXI host.

From any other esxi host, I can ping all vmotion vmkernel IP addresses except this one.

I can ping the mgmt network IP

I tried restarting the services using services.sh restart.... I had to reconnect the host after doing this, and it showed up connected again in vcenter, but this made no difference.

i tried disabling and re-enabling vmotion on the vmkernel port, and I tried changing the IP address. No change

This appears to have failed immediately after after a 3rd party application, DocAve was used to make a clone of a VM and store the copy on a mapped drive.

Any ideas on how to get vmotion running again on this host ?

[a_p_]

I cannot ping any other vmotion vmkernel IP addresses from this ESXI host.

From any other esxi host, I can ping all vmotion vmkernel IP addresses except this one.

It's hard to assist without knowing how the virtual networking on the host is configured. Please provide details about the setup, e.g. whether vMotion runs on dedicated vmnics and subnet, ...

In case of dedicated vmnics, you may also want to double-check the physical switch port(s).

André

[Marmotte94]

Hello,

Do you the same Familly CPU for all your ESXi Host ?

Do you have upgrade your Hardware for your VMs ?

Thank you,

Regards,