Hi guys,
Having a problem with one of our 3 hosts. The host says it's "disconnected". The virtual servers which are running on it say they are disconnected, however they are still physically working as servers.
I have now put the server into maintenance mode. After rebooting and bringing back into the Cluster I get the following message when trying to enable HA - "An error occurred during configuration of the HA Agent on the host"
The cluster is set up for HA. However if select the properties of the other two hosts it does give me the option to "configure for HA" which is strange. Any ideas?
After reading some other posts I checked DNS which seems fine. I can ping the host server from the others, not using the FQDN. I can ping the gateway no problem.
I should have said the server has worked in HA, but now
G
null
You don't have to do all that..
Use SSH to connect to ESX 3.5 server and use cat,more or vi command..
Are we talking about the same version? The version of ESX I am using is the one without the service console.
I just was experiencing the same symptoms... In my case it was also a case miss-match
It looks like Vcenter displays the Hostname line in the "/etc/sysconfig/network" file.
Before
HOSTNAME=ESXSERVER.domain.com
After ( I changed in in VC... Required a reboot of the host)
HOSTNAME=esxserver.domain.com
I've been experiencing this issue every time I disable/re-enable HA on my cluster one or two of the hosts get this error and not always the same host. I've always been able to get them to finally enable the HA agent by one of the usual methods mentioned earlier here but after reading this post again I decided to audit all my hosts files. what I found was that they all contained the correct IP for both the fqdn and short name and that all name entries both in DNS and the hosts files are all lower case. The only anomaly I found was that in 3 of the 9 hosts in the cluster, there were two tabs between the IP address and host names in the entry. I changed these entries so that they all matched in format. The first time I enabled HA on the cluster it worked without issue. I didn't think that would make a difference but something there sure helped.