I am recieving the above error message when trying to enable HA on a particular hosts. The first IP is the SC of the host, and for some reason the host is also resolving an IP address of a Windows server. I am pulling my hair out trying to figure this out. The other host in this cluster is fine. No issue...
Confirmed both ESX servers within the cluster have the exact same host file entries
Both the servers in the cluster are in the host file correctly.
Both servers are listed on the Virtual Center server's host file correctly as well.
What am I missing?
Maybe I am missing something, but the IP address seems to be identical. But from the message, I'd say it was telling you something is wrong with your DNS.
They are the SAME! Have you verified that the Windows box AND your ESX server are DIFFERENT IP's?
Check the /etc/opt/vmware/aam/FT_HOSTS file for incorrect entries. You can also rename the file and then reconfigure HA
I just left off the third and forth octets due to security reason...for arguement sake well call host 1 10.200.64.250, and host 2 as 10.200.64.253...
I don't see a FT_HOSTS file in /etc/opt/vmware/aam. The aam folder is there, but nothing in it. However on the other host in that cluster has the following files
-rw-rr 1 root root 3156 Oct 6 13:25 backup.def.run
-rw-rr 1 root root 111 Oct 6 13:25 ftbb.prm
-rw-rr 1 root root 190 Oct 6 13:25 ftbb.prm.bck
-rw-rr 1 root root 104 Oct 6 13:25 ftbbprm.old
-rw-rr 1 root root 119 Oct 6 13:25 FT_HOSTS
-rw-rr 1 root root 124 Oct 6 13:25 NicInfo
-rw-rr 1 root root 16 Oct 6 13:25 socket_
-rw-rr 1 root root 446 Oct 6 13:25 .cfg
-rw-rr 1 root root 90 Oct 6 13:25 vmware-sites
That means that HA never enabled on the host w/o the file. What are the contents of the file on the other host? Did you ever change the ip of this host?
With regards to the host where HA seems to be running, the FT_HOSTS file has two entries, both the same server name but with different IPs for example:
10.233.0.145 goodhostservername
10.233.0.235 goodhostservername
both these IP are the IPs of Service Console1 and my secondary Service Console.
I have not change IPs of this host, however I did assign the second IP to the Second Service Console, and this was net new. Was running off of a single SC with no redundancy, and was working on getting rid of the "Host currently has no management network redundancy" error message when a second SC is not present.
Found the issue...the second IP that the ESX host was responding to was on the other ESX host. Must have over looked it 5-6 times...