A few weeks ago I realized the storage Vmotion (svmotion) was not working.
Right after it started it stopped with an error message: Failed to connect to host
I did check several KBs and posts out there, but the common sense was about name resolution (DNS issues), deleting snapshots, restarting the VMware management services.
So I decide to look further, first I wanted to make sure Vmotion was working (the first 10% of svmotion task is a vmotion to the same host). It worked fine; my host was licensed to vmotion.
Then I looked at the host’s logs, /var/log/vmkernel, /var/log/vmkwarning, var/log/vmware/hostd.log and nothing in there gave me a clue.
A few more troubleshoot was.
Moved the guest to another cluster, to make sure the issue was not on the guest. It worked, so the problem was within the hosts.
I moved one of the hosts to a new cluster, just to make sure the problem was not with some cluster configuration. It was not.
Then looking at the Virtual Center logs (could be located at: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs )
Looks for the actual one, it starts from vpxd-0.log to vpxd-9.log
I found a very interesting log:
[VpxdInvtHost] IP address change for xxx.xxx.xxx.9 to xxx.xxx.xxx.106 not handled, SSL certificate verification is not enabled.
So, apparently Virtual Center was thinking I have changed the cOS IP (I have not) and just during svmotion it was getting lost in the middle of the process.
At this time, I put the host into maintenance mode (to move the guests off), then disconnect the host and remove it from VC.
I wait a few seconds and add it back. ( it will register the host with correct IP back on VC)
After that my svmotion started to work again.
Hope it can help someone out there.
Bye
Wednesday, November 17, 2010
Svmotion – Failed to connect to host
Marcadores:
svmotion,
virtual center,
VMWARE
Who am I

- Eduardo Meirelles da Rocha
- I’m an IT specialist with over 15 years of experience, working from IT infrastructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Consulting Architect, helping customers to embrace the Cloud Era and make them successfully on their journey. Despite the fact I'm a VMware employee these postings reflect my own opinion and do not represents VMware's position, strategies or opinions. Reach me at @dumeirell

Most Viewed Posts
-
vRealize Automation 7.1 brings several new features and functionalities, while the community is covering the fanciest...
-
I have to admit since I started playing with PowerCLI I’ve been enjoying it more and more. A few weeks ago I needed to delete 50 VMs from t...
-
Have you tried to set up or change a root's password for an ESXi host and got the following error message: Weak...
-
Do you know the LUNs on your environment might have different versions ? Yeah, that’s true!! To check tha LUN version, on the configuratio...
-
One of my blogs tradition is about demystifying vSphere Replication's operational limits; I've started it in 2...
-
Recently I’ve worked with one of my customers to scale-out their vRealize Automation (vRA) environment enabling High...
-
During the past few weeks, my NSX partner in crime, the Sr. Consultant Anderson Duboc and I have been working on a NSX Reference Poster...
-
If you just install VMware Converter and start running it with it’s default configuration, I’m sure you will be successfully. But, the...
-
VMware vSAN 6.2 Stretched Cluster & 2 Node Guide covers greatly all the network topologies supported and the configuration steps invo...
-
Once again I was working on a vSphere Site Recovery Manager project using vSphere Replication as a replication technology and had to exp...

1 comment:
Pavan @ nice one !
Post a Comment