Vsphere HA agent cannot be correctly installed or configured.

[GokulVeeramani]

Hi All,

I have recently update the ESXI host from 5.5 U1 to 5.5U2 (2143827) as my Cluster has 4host with 2 with update 2 and other 2 with update after the update Iam unable to configure the HA as it shows error like

Vsphere HA agent for the host has an error:Vsphere HA agent cannot be correctly installed or configured.

Note: the Remaning 2 host which was not update can able to install the HA agent

Need Your help to resolve this issue.

[Anjani_Kumar]

Simply right click on the affected host and right click and select <Reconfigure  HA Agent >.

This will try to reconfigure the host against the cluster.

[GokulVeeramani]

Hi Anjani,

I have tried that the same error occur..

[Anjani_Kumar]

Did you checked if locked down mode is not enabled after upgrading the host.

if its enabled just disabled it and then configure it for HA.

Also suggest you to check the esxi host logs

fdm-installer.log/var/log file or syslog.log/var/log

and vcenter log too. vpxd.log

[GokulVeeramani]

the FDM log is empty and please find the syslog .attached

[Anjani_Kumar]

I checked out and didnt find anything specific to the HA. Everything is normal there.

Try removing and adding the host again in to the host. See if it works. else we need to see on the vpxd.log for some errors if there.

[GokulVeeramani]

HI Anjani,

Thanks for helping me let  me share you what are the steps i did, i have removed the host from the cluster and removed the VPX user id from local user and added again to the cluster and the same issue presist  and i cant able to find any log entry in FDM and pls find the log

[admin]

Try this:

SSH into the host in question and run:

cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp

chmod +x /tmp/VMware-fdm-uninstall.sh

/tmp/VMware-fdm-uninstall.sh

After this go back to vCenter server --> Right Client Esxi host and Reconfigure HA Agent.

Good Luck !!  :smileyhappy:

[GokulVeeramani]

Hi shazy,

Its an ESXi5.5 U2 so we wont be having uninstallers it will VPXa :smileysad:

[brunofernandez1]

VMware KB: Reinstalling the vpxa or aam agent without losing the host record from the vCenter Server database

[GokulVeeramani]

Hi Bruno,

I have removed the Vpx User and the rejoined the host in cluster the same issue faces..

[brunofernandez1]

do you also have updated vCenter Server to U2?

whab about rebooting? allready tried?

[GokulVeeramani]

Burno,

No vcenter was  not updated to U2 and yes restarted ...

[brunofernandez1]

you have to FIRST update vCenter and then the esxi host...you actually don't have a supported state...

[GokulVeeramani]

As checked the version is compatable for the 5.5 U2 . currently its 5.5 X..please find the below screen shot and i have same config on the another cluster it works with out any issue

[admin]

Gokul,

Did you try to uninstall FDM agent using below commands:

cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp

chmod +x /tmp/VMware-fdm-uninstall.sh

/tmp/VMware-fdm-uninstall.sh

[admin]

Gokul,

Enable SSH on the Esxi host from vCenter server and then Login to this host using putty or other thirst party software with root account and password. Once you login, run the commands I sent you before. I can confirm that the commands work on Esxi 5.5 version.

Good Luck !! :smileyhappy:

[GokulVeeramani]

shazy,

It works on 5.5  In ESXi 5.5 U2, vpxa is now a part of the esxi-base package.please find the error and url

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919

[TEST1981]

Thanks,this works perfect on our stucked HA agent.

Just connect then host back to cluster and all green.

[dsritter0]

Just performed a 6.0u2 to 6.0u3d vCenter upgrade, had the same HA agent errors on a few of the hosts in a cluster. Completely disabling HA and re-enabling it fixed it.

[PaulB2]

HA would not configure on one of my clusters after upgrading vcsa 6.7 to 7.02c.

I turned off HA on the cluster, ran your steps on each of the 4 hosts (v6.7) in that cluster, then

enabled HA successfully.  Thanks!

[GokulVeeramani]

As i  Found the VPXd log as the below error

[08488 error 'DAS' opID=FDA5FF7A-00002707-56-34] [VpxdDas::StartFdmService] Failed to start FDM service on host

[GokulVeeramani]

Any Help..?

[TomKalabis]

hi, i had same problém...

http://tomaskalabis.com/wordpress/vmware-vsphere-ha-agent-cannot-be-correctly-installed-or-configured/

[Starbringer888]

Thank you TomKalabis, disabling HA on the cluster and re-enabling did the trick.

[ckava]

Thank you TomKalabis!

[sasser1970]

same error vCenter Server 6.0U3 -> Thank you TomKalabis, its works fine!

[Joseph Kim]

That fixed it for me as well! Thanks.

[dgingeri]

It would be NICE if VMWare would actually attempt to fix this problem.  I have this same problem with about half my hosts at work, where we have in excess of 120 across 6 states.  Each time, we have to remove the hosts from the cluster, make a new cluster, an moving the hosts to the new cluster, VMWare's official "fix" for this issue.  Well, that's a whole heck of a lot of work, and doesn't work permanently.  Every single time I have to reboot hosts, I hope to God that it doesn't happen again, and guess what, it happened again tonight, with a cluster that's had this problem twice before.  Before you ask, yes, this cluster is on the most recent patching level of 6.5, so it's current. 

It's not fixed.  It's been ongoing for over 6 YEARS now, and across 5.1, 5.5, 6.0, and 6.5!  (I haven't used 5.0 or 6.7 enough to know if it affects those, but likely.)

Hey, VMWare, FIX THIS.

[NathanosBlightc]

For ancient versions before vSphere 6.0, it's better to don't use them, upgrade to new versions (on stable build numbers), and don't waste your time ...

And never forget this point: You couldn't say every problem you may be seen, is always a VMware's BUG! For example in this mentioned problem (vSphere HA), when you encounter an issue, you should first check the log files like the: /var/log/fdm.log, vpxa.log, hostd.log to find more detail about the problem, then if you couldn't fix it and it will persist and aware the company about the problem, you can say it may be a bug in a product.