Yesterday, I came back to my job and first of all I went to review (as everyday) my vSphere system from vCenter and I noticed that a red alarm was waiting for me. HA was disabled because configuration had some error.
After read lots and lots of posts in Communities webpage, I tried to:
The result was the same, I can only configure HA in one host, and the other two are unnable to Reconfigure HA.
Thank you in advance!
I saw that you added the hosts to /etc/hosts, but I would still check name resolution.
SSH into a host that is failing to configure HA, try doing
vmkping <dns name of other host>
Ensure that it can resolve the name.
Additionally I would tail the hostd.log file and see what is happening during an HA reconfiguration.
tail -f /var/log/vmware/hostd.log
And of course check the aam log (HA = AAM).
this could also be a back record in your VCDB. What I would try as well is to disconnect and then drag the affected Host(s) out of the cluster. From there, one at a time, drag the Host(s) back into the cluster and "connect" See if the HA agent installs correctly. If you have bad record for the Host(s) you'll get a popup error in vCenter.
Worth a shot.....
After re-check every points of my list (first post) I disabled HA feature from Cluster I vMotioned every Vm's (from three Hosts) to one of them (doesn't matter which one). Then I entered the empty hosts in Manteinance mode and I rebooted them.
Second step, I created a new VmKernel port for vMotioning with the same Label, same ip range and same gateway for these two hosts.
Third step, I vMotioned every Vm's to these two hosts. Then I entered firts host to Manteinance mode and rebooted it.
Next step, I configured VmKernel like the other two hosts.
Finally I switched on HA feature and....Magic!! Done!
Thank you for your advices.
vmkping => Very very useful !!