Duplicate host entry problem

[jornlux]

Having a strange problem with an unaccessible host entry within the host list in vSphere client.

The problem occured after I had trouble getting HA to work due to VMkernel port order (found it referred to as "normal" behaviour in 4.0/4.1). In the attempt to create a workaround I removed/re-added ports to each host in the cluster, and removed/added hosts from/to the cluster.

The host within the cluster with the same IP adress as the "bastard brother" was unable to complete HA configuration until I removed/readded this on the entire cluster.

Not sure what this really means and if there are possible other implications due to this.

[logiboy123]

That is a pretty strange problem.

I would try to move your good hosts off to another second cluster, then delete this cluster with the orphaned esx host object.

Failing this you could do a restore of the vCenter database.

Failing that you could do a reinstall of vCenter and then import the good hosts into it.

[jornlux]

I considered the option of porting the whole setup to a new cluster within a new datacenter.  Being fairly new to vSphere administration, I'm not sure what implications this could give me - and how much extra work I would have to go through.

Was (is still) hoping this could be a simple task.

[a_p_]

I moved your question to the "VMware vCenter Server" forum.

André

[jornlux]

Logiboy: Tried what you suggested.  Moving the hosts and vm's to a new cluster went fine :smileyhappy:

However - the other cluster remains with the unaccessible host listed, only generating an error if I try to remove it.

Also - the storage service reports not to be started whenever I try to access 'Storage views'. Could this be caused by the bogus host ?

Any suggestions on doing a total cleanup ?