A consultant configures a Nutanix cluster and integrates the hosts into vCenter using VMware best practices. The customer has requested that the…

When a vSphere High Availability (HA) advanced setting, such as das.ignoreInsufficientHbDatastore, is modified, the change is not applied dynamically. The vSphere HA service, which runs on each ESXi host in the cluster, must be reconfigured to read and apply the new setting. The standard administrative procedure to force this reconfiguration is to disable HA on the vCenter cluster object and then immediately re-enable it. This action pushes the updated configuration, including the new advanced setting, to all hosts in the cluster, which should then clear the alert.

B. Make sure the DRS setting is turned on: DRS is for workload balancing and is a separate feature from HA. Enabling it will not re-read or apply changes made to HA advanced settings.
C. Create a second container: This would resolve the underlying HA warning but directly violates the customer's requirement to have only a single datastore. The goal is to suppress the warning, not re-architect.
D. Whitelist the vCenter IP address within Prism: This is a Nutanix security feature for API access control and has no interaction with or influence on the internal operations of VMware's vSphere HA feature.

1. Nutanix, vSphere Administration Guide for AOS 6.5, Section: "Creating a vSphere HA Cluster", Sub-section: "Configuration". The guide notes that for single datastore configurations, das.ignoreInsufficientHbDatastore should be set, and implies that HA must be configured for this to take effect. The standard procedure for re-reading such settings is to toggle the service.

2. VMware, vSphere Availability Guide (vSphere 8), Chapter 4: "vSphere HA Cluster Settings". This document details that changes to advanced options require HA to be reconfigured on the hosts, which is accomplished by turning the feature off and on.