VMware Cloud Community
caseyfriese
Contributor
Contributor
Jump to solution

HA Configuration Issues

Probably a simply and silly question but...

I'm having an issue with HA on one of my Clusters.  At the cluster level I have a message stating "Insufficient resources to satisfy HA failover level on cluster <cluster name> in <datacenter name>.  Unable to contact a primary HA agent in cluster <cluster name> in <datacenter name>

Each of the 6 hosts in the cluster show a an error with the HA Agent on <host> in cluster <cluster name> in <datacenter name> has an error : Error while running health check script.

Now, looking at the HA configur at the cluster level, I see someone (to many ahnds in the kitchen I guess) enabled DPM under Admission Control.  I've disabled that so it matches my other clusters who happen to be working just fine.  I selected "reconfigure HA" on all the hosts but the process is failing. "Cannot complete the configuration of the HA agent on the host.  Unable to contact primary HA agent."

So I'm thinking that if I just turn off HA on the cluster, and turn it back on that it might straighten out the issue.

2 questions:

1. Will that fix my issue

2. If #1 will, does turning off HA affect the running VMs on the 6 hosts other than putting them at risk temporarily?

Thanks,

Casey

Casey Friese, Sr. Enterprise Architect
0 Kudos
1 Solution

Accepted Solutions
peetz
Leadership
Leadership
Jump to solution

Disabling and re-enabling HA on the cluster will probably fix the issue.

See here: http://kb.vmware.com/kb/1021173

And you should do that ASAP, because NOW your VMs are at risk already, because HA is currently not working properly.

Turning HA off and on will not affect the VMs in any way except from putting them at the risk of not being restarted automatically in case of a host failure.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

0 Kudos
2 Replies
peetz
Leadership
Leadership
Jump to solution

Disabling and re-enabling HA on the cluster will probably fix the issue.

See here: http://kb.vmware.com/kb/1021173

And you should do that ASAP, because NOW your VMs are at risk already, because HA is currently not working properly.

Turning HA off and on will not affect the VMs in any way except from putting them at the risk of not being restarted automatically in case of a host failure.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
caseyfriese
Contributor
Contributor
Jump to solution

All good - thanks Andreas!

Casey Friese, Sr. Enterprise Architect
0 Kudos