6.7
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
- How Fault Tolerance Works
- Fault Tolerance Use Cases
- Fault Tolerance Requirements, Limits, and Licensing
- Fault Tolerance Interoperability
- Preparing Your Cluster and Hosts for Fault Tolerance
- Using Fault Tolerance
- Best Practices for Fault Tolerance
- Legacy Fault Tolerance
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- 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
Table 2‑4. vSphere HA Advanced Options
Option Description
das.isolationaddress[...]
Sets the address to ping to determine if a host is isolated from
the network. This address is pinged only when heartbeats are
not received from any other host in the cluster. If not specified,
the default gateway of the management network is used. This
default gateway has to be a reliable address that is available, so
that the host can determine if it is isolated from the network. You
can specify multiple isolation addresses (up to 10) for the
cluster: das.isolationaddressX, where X = 0-9. Typically you
should specify one per management network. Specifying too
many addresses makes isolation detection take too long.
das.usedefaultisolationaddress
By default, vSphere HA uses the default gateway of the console
network as an isolation address. This option specifies whether
or not this default is used (true|false).
das.isolationshutdowntimeout
The period of time the system waits for a virtual machine to shut
down before powering it off. This only applies if the host's
isolation response is Shut down VM. Default value is 300
seconds.
das.slotmeminmb
Defines the maximum bound on the memory slot size. If this
option is used, the slot size is the smaller of this value or the
maximum memory reservation plus memory overhead of any
powered-on virtual machine in the cluster.
das.slotcpuinmhz
Defines the maximum bound on the CPU slot size. If this option
is used, the slot size is the smaller of this value or the maximum
CPU reservation of any powered-on virtual machine in the
cluster.
das.vmmemoryminmb
Defines the default memory resource value assigned to a virtual
machine if its memory reservation is not specified or zero. This
is used for the Host Failures Cluster Tolerates admission control
policy. If no value is specified, the default is 0 MB.
das.vmcpuminmhz
Defines the default CPU resource value assigned to a virtual
machine if its CPU reservation is not specified or zero. This is
used for the Host Failures Cluster Tolerates admission control
policy. If no value is specified, the default is 32MHz.
das.iostatsinterval
Changes the default I/O stats interval for VM Monitoring
sensitivity. The default is 120 (seconds). Can be set to any value
greater than, or equal to 0. Setting to 0 disables the check.
Note Values of less than 50 are not recommended since
smaller values can result in vSphere HA unexpectedly resetting
a virtual machine.
das.ignoreinsufficienthbdatastore
Disables configuration issues created if the host does not have
sufficient heartbeat datastores for vSphere HA. Default value is
false.
das.heartbeatdsperhost
Changes the number of heartbeat datastores required. Valid
values can range from 2-5 and the default is 2.
vSphere Availability
VMware, Inc. 41