VMware Cloud Community
s1m0nb
Enthusiast
Enthusiast
Jump to solution

Storage Vmotion fails after Service Console IP change

Hi

I recently had to change my service console & vmotion ip addresses - and to be clever about it I added a second vswitch configured it as a second service console and then removed the original vswitch0.

Everything works fine, I can vmotion between hosts etc....

However Storage vmotion fails to connect to host.....Is there some setting I am missing? (to fully remove the original service console....I am suspecting something along those lines..)

Anyhoo thanks in advance for any ideas..

Reply
0 Kudos
1 Solution

Accepted Solutions
depping
Leadership
Leadership
Jump to solution

remove the host from the cluster

check the file, if it's still there delete the file

add the host back to the cluster

there are a couple of other resolutions mentioned on my blog in the comments of the following article:

http://www.yellow-bricks.com/2008/01/24/clone-and-roll-out-template-fail-with-failed-to-connect-to-h...




Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

Reply
0 Kudos
5 Replies
depping
Leadership
Leadership
Jump to solution

i would start with flushing DNS on the hosts that you are using to kick off SVmotion. Next step would be checking /etc/opt/vmware/vpxa/vpxa.cfg on the ESX host that causes this problem.




Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
s1m0nb
Enthusiast
Enthusiast
Jump to solution

Yes we are on the right tracks here..the vpxa.cfg file has the old host ip address in there

So I changed it to the correct address and restarted the mgmt-vmware service -- and it changes the ip back to the old one Smiley Sad

How do I change the address permanently?

Reply
0 Kudos
depping
Leadership
Leadership
Jump to solution

remove the host from the cluster

check the file, if it's still there delete the file

add the host back to the cluster

there are a couple of other resolutions mentioned on my blog in the comments of the following article:

http://www.yellow-bricks.com/2008/01/24/clone-and-roll-out-template-fail-with-failed-to-connect-to-h...




Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
s1m0nb
Enthusiast
Enthusiast
Jump to solution

Exactly correct

I stopped the vpxa service on the hosts - stopped Virtual Center service - hacked the sql database (changed to old host addresses) and restarted everything - all works fine now

Reply
0 Kudos
depping
Leadership
Leadership
Jump to solution

Great thanks for the feedback, will add that bit of info to my blog... seems like more people are experiencing the fact that the database needs an update.




Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos