6.5.1
Table Of Contents
- vSphere Availability
- Contents
- About vSphere Availability
- Business Continuity and Minimizing Downtime
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- vCenter High Availability
- Plan the vCenter HA Deployment
- Configure the Network
- Configure vCenter HA With the Basic Option
- Configure vCenter HA With the Advanced Option
- Manage the vCenter HA Configuration
- Set Up SNMP Traps
- Set Up Your Environment to Use Custom Certificates
- Manage vCenter HA SSH Keys
- Initiate a vCenter HA Failover
- Edit the vCenter HA Cluster Configuration
- Perform Backup and Restore Operations
- Remove a vCenter HA Configuration
- Reboot All vCenter HA Nodes
- Change the Appliance Environment
- Collecting Support Bundles for a vCenter HA Node
- Troubleshoot Your vCenter HA Environment
- Patching a vCenter High Availability Environment
- Using Microsoft Clustering Service for vCenter Server on Windows High Availability
- Index
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-anity
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 insucient
resources to perform the failover.
See vSphere Resource Management for more information on
anti-anity rules.
das.maxresets
The maximum number of reset aempts made by VMCP. If
a reset operation on a virtual machine aected 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 aempt
das.config.fdm.reportfailoverfailevent
When set to 1, enables generation of a detailed per-VM
event when an aempt 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 anity 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 congured
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 specied. 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.
N Once this limit is changed, for all hosts in the cluster
you must run the Recongure 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 seing.
vSphere Availability
36 VMware, Inc.