gwelsh123
Contributor
Contributor

HA failure since VC upgrade 2.02

Jump to solution

Have just upgraded our VC installation to v 2.02, since then HA cannot be configured. Configuration fails on all (5 hosts). Checked the usual, dns/name resolution etc, all seems fine (HA was working fine until the virtual centre upgrade).

Have seen similar problems before, and we had to recreate the cluster, there werent >120 VMs with multiple resource pools at that point tho

0 Kudos
1 Solution

Accepted Solutions
limey36
Enthusiast
Enthusiast

We had to make entries in /etc/hosts after upgrading so HA could resolve the other hosts. One small point here too - you have to enter the host names in lower case within /etc/hosts no matter how they're actually configured........

View solution in original post

0 Kudos
4 Replies
peetz
Leadership
Leadership

Hi,

see this (rather long) thread for the 2.0.2 upgrade discussion, HA failures and how to resolve them:

http://www.vmware.com/community/thread.jspa?threadID=94534

\- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
limey36
Enthusiast
Enthusiast

We had to make entries in /etc/hosts after upgrading so HA could resolve the other hosts. One small point here too - you have to enter the host names in lower case within /etc/hosts no matter how they're actually configured........

View solution in original post

0 Kudos
gwelsh123
Contributor
Contributor

yep, after posting this, i had a dig about, found the multipleshorthostname error, and found that /etc/hosts contained uppercase values for the hostname. changing that, and re-enabled HA with no problems

cheers

0 Kudos
KlinikenLB
Contributor
Contributor

Hi limey,

great hint. I also had yesterday exactly the same problem (at the same time) as gwelsh and waiting for the answer of my support request until now ...

But now I changed my server names in the /etc/hosts all my six ESX hosts to lower case and then it worked again.

Thanks an regards,

Dietmar

0 Kudos