6.7

Table 2‑4. vSphere HA Advanced Options (Continued)
Option Description
fdm.isolationpolicydelaysec
The number of seconds system waits before executing the
isolation policy once it is determined that a host is isolated. The
minimum value is 30. If set to a value less than 30, the delay will
be 30 seconds.
das.respectvmvmantiaffinityrules
Determines if vSphere HA enforces VM-VM anti-affinity rules.
Default value is "true", whereby the rules are enforced. In this
case, vSphere HA does not fail over a virtual machine if doing
so violates a rule, but it issues an event reporting there are
insufficient resources to perform the failover. Can also be set to
"false" and rules are not enforced. For more information on anti-
affinity rules, see vSphere Resource Management.
das.maxresets
The maximum number of reset attempts made by VMCP. If a
reset operation on a virtual machine affected by an APD
situation fails, VMCP retries the reset this many times before
giving up
das.maxterminates
The maximum number of retries made by VMCP for virtual
machine termination.
das.terminateretryintervalsec
If VMCP fails to terminate a virtual machine, this is the number
of seconds the system waits before it retries a terminate attempt
das.config.fdm.reportfailoverfailevent
When set to 1, enables generation of a detailed per-VM event
when an attempt by vSphere HA to restart a virtual machine is
unsuccessful. Default value is 0. In versions earlier than
vSphere 6.0, this event is generated by default.
vpxd.das.completemetadataupdateintervalsec
The period of time (seconds) after a VM-Host affinity rule is set
during which vSphere HA can restart a VM in a DRS-disabled
cluster, overriding the rule. Default value is 300 seconds.
das.config.fdm.memreservationmb
By default vSphere HA agents run with a configured memory
limit of 250 MB. A host might not allow this reservation if it runs
out of reservable capacity. You can use this advanced option to
lower the memory limit to avoid this issue. Only integers greater
than 100, which is the minimum value, can be specified.
Conversely, to prevent problems during master agent elections
in a large cluster (containing 6,000 to 8,000 VMs) you should
raise this limit to 325 MB.
Note Once this limit is changed, for all hosts in the cluster you
must run the Reconfigure HA task. Also, when a new host is
added to the cluster or an existing host is rebooted, this task
should be performed on those hosts in order to update this
memory setting.
vSphere Availability
VMware, Inc. 42