Problem vMotioning a Virtual Server in VMWare

Hi folks, 500 pointer :)

I need to migrate some live servers around on an ESX farm. I have 4 VMWare servers, let's call them S1, S2, S3 and S4

I need to move VServer1 from S2 to S4.

I have succesfully moved VServer3 from S3 to S4 using vMotion.

When I try to move I get the error...
----------------------------------------------------------------------------------------------------------------------
Failed to migrate Virtual Machine Win2k3APP  UKI-WMS01 from host 10.210.252.182 to host 10.210.252.184. Reason: Migration failed. Source: Migration to host <10.210.252.194> failed with connection attempt failed (host unreachable?) (0xbad0055)  Destination: Timed out waiting for migration data.
---------------------------------------------------------------------------------------------------------------------

I have tried to ping 10.210.252.182 and get no response, whereas if I ping 10.210.252.184 I get an immediate response.

I suspect that there is a problem with the vMotion port on S2, but need a way to check this/reconfigure or restart, obviously without restarting the server(s)...

Any advise would be most appreciated.
LVL 1
Jeremy BromleyIT ConsultantAsked:
Who is Participating?
 
Jeremy BromleyIT ConsultantAuthor Commented:
Okay @ arunraju - Checked the Network Adapters and there is indeed one of them that says it is DISCONNECTED... However, looking "physically" at the server, all ports are green-lit properly. Can't really unplug any of the ports to check cables whilst live server is running.
0
 
65tdRetiredCommented:
Is this ESX 3i or 3.5 uX?

If there is service console access use vmkping to check the vmkernal port.

http://kb.vmware.com/selfservice/viewContent.do?externalId=1003728&sliceId=1
0
 
giovannicoaCommented:
Hi,

here's what I do in your situations.

a) I suppose you have the VMotion separated physically or throught a VLAN from the normal network.
b) Put a laptop on the same vmotion network (physical or logical) and try to ping all the esx servers.
c) If you cannot ping one of them, you need to check the network configuration on that server.
d) Also check the cabling and connections, you network card for VMotion need to be on the correct physical network or logic VLAN.
e) Also check for DNS resolutions, configure and verify DNS contains the correct info about your ESX server.
f) If you have corrected basic network problems you can try again to do a VMotion.

Hope this can help you,
Giovanni Coa
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
vmwarun - ArunCommented:
Login to the ESX Host, S2 using VI Client and check under Configuration -> Network Adapters to check whether the vmnic assigned to the vSwitch (VMKernel Portgroup) is in a connected state.

I also suggest that you set all you speed and duplex settings of your NICs manually instead of setting it to Auto-Negotiate.
0
 
bilco105Commented:
Restart the hostd service on the affected host.
0
 
vmwarun - ArunCommented:
Have you labeled your cables at the physical switch end ? If yes then check whether there is a duplex mismatch at the switch end.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.