VCSA 6.5.0d and ESXi 6.5.0d HA - insufficient configured resources despite adequate resources

[5mall5nail5]

Hi all - I have a lab running 2 hosts in a cluster on the latest ESXi and VCSA.  I have plenty of experience setting up clusters so I am a bit baffled with this one.  My CPU load on each host is ~5 - 10% and my memory load is about 30%.

I've changed admission control to hosts failures tolerated, % of resources reserved for failure (from 5% - 50%), admission control disabled, etc.  Nothing changes the yellow ! on the cluster and the attached summary message.  I have plenty of datastores for heartbeating and I cannot see anything else wrong.  The hosts are in a cluster, vMotion works, Storage vMotion, etc.  I am using valid (VMUG) licensing for this cluster, so I have all features.  I just cannot figure out why it's complaining.  I haven't actually tried to test HA yet but I never like an alert or "issue" on the cluster.

Anyone else experiencing this?  Have a 6.0 cluster that's similar without issue!

Thanks,

Jon

[depping]

Have you tried clicking "reconfigure for HA"?

[PCTechStream]

This can help!

"in your case you have vSphere HA with number of host failure to tolerate as admission control policy set. that means system is going to calculate CPU and Memory slots out of available resources in your cluster, and from those total number of slots, it will keep some resources as reserved for failover and remaining are going to be available to be used. All depends upon how many hosts failure that you want to tolerate."

MARKED AS CORRECTED

LINK: who can help me with "Insufficient resources to satisfy configured failover level for vSphere ...

Raul.

VMware VDI Administrator.

http://ITCloudStream.com/

Stay Connected :smileyplus: Don't forget to:

Like > Share > Comment > Reply > Helpful > Answered

[5mall5nail5]

Thanks all - yes I clicked "reconfigure for HA" on each host.

Also, I have set admission control to disabled, 5% CPU/RAM, etc. and nothing suppresses that warning.  It's not a true alarm that can be reset to green, its a "configuration issue" on the cluster and it's really driving me nuts.

[PCTechStream]

TRY THIS!

Put the host on maintenance

Disconnect the host

Remove the host from the Cluster

Add the host back into the cluster

Raul.

VMware VDI Administrator.

http://ITCloudStream.com/

Stay Connected :smileyplus: Don't forget to:

Like > Share > Comment > Reply > Helpful > Answered

[5mall5nail5]

I'll give it a shot - assuming for both hosts?

Remove HA first?  Maintenance mode, reconnect, and turn HA back on?

[selmamgj]

Any solution to this?

We seem to have the same problem. Since we dont do reservations I need to rely on the percentage based HA. (We're on ESXi 6.5)

[depping]

I have reproduced this internally in my lab, then I started digging and noticed that there's a bug on it. Let me internally try to figure out when this will be fixed. For now you can safely ignore the error

[Schoko81]

Hi,

I have the same behaviour/issue - are there any news/feedback on that?

Thx in advance!

[sicnarf_latosa]

For me I just uncheck and check the Override calculated failover capacity and leave it default 50%

[sicnarf_latosa]

It is NOT an alarm VMware global support services confirmed the issue described is a bug. Expect a resolution in some upcoming patch for vSphere (possibly vCenter, possibly ESXi, possibly both).