6.5u3P ---- Looking for your help in regards, recent vulnerbilities -- patching vCenter to 6.5u3p.

[VPXA]

As recommeneded by VMware upgraded vCenter to 6.5u3p (part of remidiation) towards recent vulnerbilities, i.e, https://www.vmware.com/security/advisories/VMSA-2021-0010.html.

vCenter previous Version  : 14020092

There after we are expressing, error messages with "HA Agent" on the clusters, reconfigured the HA agent, issue not fixed.

Alarm Definition:
([Event alarm expression: vCenter Server is unable to find a master vSphere HA agent; Status = Red] OR [Event alarm expression: vCenter Server connected to a vSphere HA master agent; Status = Green])

Event details:
vCenter Server is unable to find a master vSphere HA agent in cluster CVW03 in EPCDC-AP

[Ank_S]

Hello VPXA,

Did you attempt to disable the HA on the Cluster itself ?
If not , disable and then enable HA at the cluster level and then check the behavior.

If it does not work , then check the vpxa.log (On ESXI host)  for any communication error between the vCenter and the ESXI.

PS: Mark kudos or correct answer as appropriate

[VPXA]

Yes tried for disable / enable HA, still not working.,

in respective to communication error, can we suspect any network issues, opened a case a with GSS looking for their arrival.

[Ank_S]

Hello VPXA,

Network issues will cause connectivity errors.

The Event "vCenter Server is unable to find a master vSphere HA agent; Status = Red", does notify connectivity issues in most cases. Check connectivity issues between the vCenter and ESXI host.  (Check Ping , telnet and firewall)

However it may also relate to the fdm Agent (on ESXI Host) not working as expected.

Try the following steps :

1) Check the FDM status : /etc/init.d/vmware-fdm status ---------- It shld be running

2) Disconnect and re-connect the ESXI hosts.

3) Manually Uninstall and re-install the FDM vib on the ESXI host. Refer the following for more details :

https://kb.vmware.com/s/article/2011688

[VPXA]

Thanks for all your inputs AnK,

though we are using HPe BL's,  here the issue with AMS (Agentless Management Service), /tmp folder is fully occupied with 100% to push the FDM agent update into the AMS folder.

Observation : 

HA could not be configured on most of the hosts.
*/tmp partition  was at 100% on the hosts, where FDM agent was not pushed.
*ams-bbUsg.txt was filling up the space.

Resolution :

after removing the file, we got enough free space in the host partition.
*reconfigured HA at cluster level.
*HA configured successfully.

https://kb.vmware.com/s/article/78595