VMotion faild with timedout Error

[MBEngsch]

Hello All,

first i will give you some information about my vi environment:

3x ESX 3.0.2 + all Patches within today

VC 2.0.2

HP Prolaint DL 580 G4 16 GB RAM

EVA 4100 Storage

Ok, now, here is my issue:

I can migrate vms from esx1 to esx2 or esx2 to esx1 without any problems.

when i try to migrate an running vm to esx3 i get the following error:

operation timed out

all the servers have the same network configuration und the same storage configuration. every server has attach to the san.

vms which are not running can be succesfully move to and from the esx3

has anyone an idea?!

what can i do?

Thank you all for your support!

[TCronin]

You can try restarting the management agents on the host.

As root on the service console use:

service mgmt-vmware restart

service vmware-vpxa restart

Also make sure that your vmotion/vmkernel vswitch is setup correctly, especially speed and duplex. If you are on GB nics and both the nic and switch port aren't set to the same setting (auto/auto is correct for most GB infrastructures) you can have problems with vmotion. If the nic and the port are correct but you're at less than 1000/full then check for bad punch downs or cabling. Losing even 1 pair in a cable path for GB will cause it to fall back to lower speed and/or duplex. 100 mbit only requires 2 pair, GB requires all 4 to work.

[MBEngsch]

i checked it. but its ok.

what con i do next?

[dfgl]

We get the same issue on the same hardware - we have our vmo nics manually set to 1000/full (as they don't negotiate with our switches properly) & occiasionally they just drop out & we get the symptoms you have seen. All we do is set the speed back to auto/auto, apply the change then set it back to 1000/full & the nic springs back into life. You may like to try setting the speed manually - it works for us!

[jccoca]

Hi,

Can you vmkping to the vmotion IP at the esx3 from esx2 or esx1?

Can you put the /var/log/vmkwarning and /var/log/vmkernel from the host where vm is running and from esx3 host?

[MBEngsch]

Hi,

i checked it all. But the Problem still occur.

Here are the logs: vmwarnigs and vmkernel. I hope we can solve that issue!!

[TCP]

Hi!

First: check your license configuration on big-esx3 (vmoution).

Second: check vmoution checkbox on big-esx3 Vmoution Switch.

Third: try to restart VC.

[jccoca · Accepted solution]

The log says that it can't connect to the vmotion ip at the other host. If you do vmkping 210.5.229.29 from the host 210.5.229.30 what are the times that it is returning?

[Erik_Zandboer]

Indeed, it appears to be an issue with the networking. I guess when you look in Virutalcenter, you see vmotion hanging at 10% and then failing right?

Could you try to connect both hosts via a direct patch? This to rule out any switching problems between the hosts. As soon as you see a vmotion job go beyond 10%, it means that network connection is available between the hosts for vmotion.

[MBEngsch]

Hi all,

the cause was the switch. it has an invalid vlan configured.

So my VMotion is running.

Thank you fpr supporting me

Marcus