6.0.1

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 "false", whereby the rules are not
enforced. Can also be set to "true" and rules are enforced
(even if vSphere DRS is not enabled). 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.
See vSphere Resource Management for more information on
anti-affinity rules.
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.
NOTE If you change the value of any of the following advanced options, you must disable and then re-
enable vSphere HA before your changes take effect.
n
das.isolationaddress[...]
n
das.usedefaultisolationaddress
n
das.isolationshutdowntimeout
Chapter 2 Creating and Using vSphere HA Clusters
VMware, Inc. 39