ronald_higgins
Contributor
Contributor

VirtualCenter IP Address change, no host management to ESX's in Cluster

Jump to solution

Greetings All,

Our MS Team moved our VirtualCenter server to a new IP Address. But since then i've had particular problems with a cluster i had previously set up.

Since the change, the cluster with 2 esx hosts cannot be destroyed, the esx hosts themselves cannot be dragged out, disconnected or slotted ito maintenace mode.

I suspect this is because the hosts are still sending heartbeats to the old VCenter IP Address . Any action to the cluster or hosts within just hangs.

Is there anyway, from the ESX Servers themselves to be removed from VCenter so i can re-added ?

Trying to readd the host in VC will prompt me that it's managed under a VCenter Server (old IP) and if you override you get an error "the host is already connected to this VirtualCenter server)

Any ideas/thoughts will be appreciated.

0 Kudos
1 Solution

Accepted Solutions
benma
Hot Shot
Hot Shot

Have you tried to restart your Windows VC service?

View solution in original post

0 Kudos
6 Replies
benma
Hot Shot
Hot Shot

The old IP is stored in the vpxa agent.

The easyst way ist to disconnect and reconnect your host.

ronald_higgins
Contributor
Contributor

Hmmm.... wish i could disconnect & reconnect.

Unfortunately disconnect / connect are grayed out on the hosts.

VC

|-> CLUSTER

|-> esxhost1

|-> esxhost2

####################

Cant disconnect/reconnect, cant destroy the cluster ... got myself into a right mess here i have Smiley Wink

0 Kudos
benma
Hot Shot
Hot Shot

Have you tried to restart your Windows VC service?

View solution in original post

0 Kudos
PabloOttawa
Enthusiast
Enthusiast

Ronald,

- Connect to each ESX host using SSH.

- Edit one of the following files:

/etc/opt/vmware/vpxa/vpxa.cfg (ESX3.5)

/etc/vmware/vpxa.cfg (esx 3.0.x) (ESX3.0)

and change the vCenter server IP

- Restart vpxa

service vmware-vpxa restart

Let me know how it goes.

Pablo

Troy_Clavell
Immortal
Immortal

don't know if you've seen this KB, but it should be useful.

http://kb.vmware.com/kb/5850444

0 Kudos
ronald_higgins
Contributor
Contributor

Thanks all for the help.

Guess the whole thing was just overthought, restarting the VC Service made all the problems go away Smiley Happy

Thanks!

0 Kudos