Solved

Problem vMotioning a Virtual Server in VMWare

Posted on 2009-05-12
6
1,577 Views
Last Modified: 2012-08-14
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.
0
Comment
Question by:Jeremy Bromley
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 22

Expert Comment

by:65td
ID: 24364314
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
 
LVL 5

Assisted Solution

by:giovannicoa
giovannicoa earned 200 total points
ID: 24364453
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
 
LVL 19

Assisted Solution

by:vmwarun - Arun
vmwarun - Arun earned 200 total points
ID: 24372294
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
Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

 
LVL 5

Assisted Solution

by:bilco105
bilco105 earned 100 total points
ID: 24372663
Restart the hostd service on the affected host.
0
 
LVL 1

Accepted Solution

by:
Jeremy Bromley earned 0 total points
ID: 24373537
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
 
LVL 19

Expert Comment

by:vmwarun - Arun
ID: 24407978
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

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question