snake97
Contributor
Contributor

vmotion failed after 10%

Hi all,

I have 2 esx server (sun X4600) who are working vmotion fine. (esx1 and es2)

I would like to a third esx server (the same as other) and enable vmotion. (esx3)

My problem is that I'm not able to make vmotion with this last server, I got a time out after 10% in the vmotion.

Cold migration of vm works fine but not hot migration.

Vmkping work only from the esx3 to other but not from esx1 and esx2.

I have update 1 for esx 302 and patch esx-1002424 on all esx servers.

Name resolution works fine on all esx.

Is somebody got any idea ?

Thank you for your help

Regards

0 Kudos
6 Replies
EGRAdmin
Enthusiast
Enthusiast

Is someone else on the network trying to use the same IP that you're using for your VMKnic?

Have you tested the vmkping command?

Or;

Try changing it's VMKNIC IP and see if that solves it.

I was having a similar problem when my IP's were incorrectly configured.

0 Kudos
snake97
Contributor
Contributor

Hi, thank's for your quick answer, i made some vmkping from esx1 and 2 to esx3 but that's don't work.

vmkping from esx3 to all other are ok.

I'm able to ping the ip of the vmotion of esx3 from my network, but vmotion ip of other esx server are not pingable.

I think it's something very stupid... I'm a really beginner with vmware ... Smiley Happy

Regards

0 Kudos
Chamon
Commander
Commander

Do you have a default gate way for your vmknic? Also did you check the vmotion box in the proporties of the vmkernel portgroup? Also do the VMs have the servers CDROM set to connect at start up?

0 Kudos
EGRAdmin
Enthusiast
Enthusiast

It could be an initial config thing as Chamon stated above.

If it's configured properly by enabeling it in the network properties I would make sure you have the correct IP in place.

Or that someone didn't use the IP.

All my VMotion address' are not pingable from my network and can resolve with vmkping.

It sounds like some device on your network is using your VMKnic address.

Try just for the heck of it, snagging the next unreserved IP in your list (ping it first) and try that out.

If it's an IP reservation problem that should solve it.

If it's a basic config problem, enabeling it should solve that.

0 Kudos
Chamon
Commander
Commander

did you get this worked out?

0 Kudos
snake97
Contributor
Contributor

Hello, I was really busy last week so, I just solved the problem last Friday.

I found a misconfigured vlan on the network side.

Thanks' everybody for help.

Regards

0 Kudos