houghtp
Contributor
Contributor

SVMotion - Failed to connect to Host

Hi,

We're having some problems with SVmotion

It has worked in the past but now I get a message - "Failed to connect to host". We had a planned mass downtime the weekend but I'm not exaclty sure when Svmotion stopped working so not sure if this is related?

We've also upgraded our database to sql 2005 recently - again not sure if this is related?? These are the only things that have changed in our environment for a while..

I've seen a previous thread regarding this where they fixed it by removing Hosts from VC and re-adding. But before I try this I was wondering what troubleshooting steps I could try. I get the problem wether I use Svmotion or a cold storage migration.

any help appreciated!!

0 Kudos
10 Replies
sbeaver
Leadership
Leadership

Have you looked in the logs? What kind of error messages are you getting? If you DO NOT have autostart and stop enabled you can try these commands

service vmware-vpxa restart

service mgmt-vmware restart

Steve Beaver

VMware Communities User Moderator

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

Coming soon to a store near you!

*Virtualization is a journey, not a project.*

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
houghtp
Contributor
Contributor

ok checked general logs..

vmkernel

vmkwarning

messages

hostd

and also restarted both services (we haven't got any autostart / stop options configured)

tried to run another SVmotion still same result...

are there any more logs I should be checking?

0 Kudos
sbeaver
Leadership
Leadership

Next step is to remove and re-add the hosts

Steve Beaver

VMware Communities User Moderator

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

Coming soon to a store near you!

*Virtualization is a journey, not a project.*

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
houghtp
Contributor
Contributor

Ok cheers I'll try that later.

Just for info by re-adding the hosts what is that reseting /changing?

0 Kudos
sbeaver
Leadership
Leadership

If I am not mistaken it should re-install the VirtualCenter client

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
houghtp
Contributor
Contributor

ok cheers!

0 Kudos
SaltyWalty
Contributor
Contributor

We are experiencing the same issue. Was this problem ever resolved?

Thanks,

-Salty

0 Kudos

Was this ever resolved? I'm having the same issue.

Cheers,

Bradley Sessions

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Cheers! If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
0 Kudos
BostonFan
Contributor
Contributor

Credit BigRollTide from yellowbricks.com with this fix, albeit modified slightly. If any VMware developers are reading this, put this bug in the "Lame" column.

Stop the VMware VirtualCenter Server service

Run this script on the database:

UPDATE VCDB.dbo.VPX_HOST

SET IP_ADDRESS = ‘x.x.x.x’

WHERE DNS_NAME = ‘fully.qualified.domain.name’

Start the VMware VirtualCenter Server service. No need to touch your hosts, they should all update accordingly within a few minutes of the service start.

0 Kudos
MacGaiver
Contributor
Contributor

Thanks!

This solution worked for me, on the DB the entry of the IP address of the servers contained old addresses, we have changed the address of the Service Console recently, maybe this is a bug or something.

0 Kudos