HA/Vmotion error (hostmisconfigured: host ip x.x.x.x can not be resolved to

[SafetyMan]

I am having problems setting up my HA VM cluster.

The error I am getting when added the 2nd host to the cluster and then trying to initialize it is as follows:

hostmisconfigured: host ip x.x.x.x can not be resolved to shortname esx1.mydomain.com.

and notice: this is the other host in my cluster(esx1.mydomain.com initializes just fine). it is the esx2.mydomain.com host which is giving me this problem with VMWARE Vmotion /HA.... notice I also enabled DRS on this cluster.

I have tried several different arrangements, but nothing I tried was able to

"reconfigure for HA".

Please help

[cheeko]

What ESX version(s) are you running?

HA came with Virtual Infrastructure 3 and does not work with 2.x.

[SafetyMan]

ESX 3.1 and VI/Virtual Center 2.0

[wobbly1]

can you resolve via dns the short and fqdn of ESX1 from ESX2 and vice versa? It looks like your DNS is not working 100%

[SafetyMan]

Based on searching "hostmisconfigured" on all the message boards.

I found some help which did work.

Solution

======

Go to each ESX host and login as root or some administrator type

>nano /etc/hosts

add entries for all servers in the cluster

When complete each hosts file on all servers

should look identical.... In my case:

both hosts files should look like this....

127.0.0.1 localhost.localdomain localhost

10.1.1.10 esx1.mydomain.com esx1

10.1.1.20 esx2.mydomain.com esx2

Things that did not work:

deleting and re-adding the cluster

deleting and re-adding the servers

Yes I did verify:

network settings on each host

ping's for shortname and ip addresses (they all resolved correctly)

I also verified the /etc/resolv.conf file on both esx1 and esx2 looked

the same(esx2 had search mydomain.com on the 3rd line and not the 1st line)

resolv.conf should look something like this

==============================

search mydomain.com

nameserver 10.2.3.20

nameserver 10.3.2.21

Anyways...I believe based on the other message boards ..this is a

bug in either esx server or VMWARE (VI)Virtual Center 2.0.1.

Of course, after I got it working completely...I rebooted..It still worked too.

[grasshopper]

please don't forget to award points for those that helped you, as "wobbly1" technically did have the correct answer, or at least helpful.

[wobbly1]

glad that you have got it working. I would suggest that there is something not quite right with name resolution in your environment hence explicit settings in your hosts files rather than a bug otherwise everyone would be having the same problem. Maybe, if possible, you could test further to try to narrow down the issue by only having settings in the host file of one server at a time?

[SafetyMan]

If I turn one server on at a time....The HA will work for the given server.

But once a turn the 2nd server on (does not matter which box becomes the 2nd server), the 2nd server does not resolve correctly.

hmmm.

[SafetyMan]

This also could have something to do with the reverse lookup zones for my DNS SERVERS. Upon further search I looked into this:

At each ESX Server I ran the command

>nslookup esx1.mydomain.com

Correct IP ADDRESS came back (10.1.1.1)

BUT NOW NOTICE:

>nslookup (10.1.1.1)

\** server can't find 10.1.1.1.in-addr.arpa: NXDOMAIN

so I logged into my DNS SERVERS.

Once logged in, I found out the Reverse Lookup Zone for my ESX HOST Network did not exist.... I added the zone...and deleted/readded all the servers for my ESX HOST NETWORK.

search engine reference

=================

lmhosts

hosts files

IP ADDERESSES FOR DNS SERVERS

ESX SERVERS DNS REVERSE LOOKUP

Message was edited by:

SafetyMan