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
4 Click Failures and Responses and expand VM Monitoring.
5 Select VM Monitoring and Application Monitoring.
These seings turn on VMware Tools heartbeats and application heartbeats, respectively.
6 To set the heartbeat monitoring sensitivity, move the slider between Low and High or select Custom to
provide custom seings.
7 Click OK.
Your monitoring seings take eect.
Configure Proactive HA
You can congure how Proactive HA responds when a provider has notied its health degradation to
vCenter, indicating a partial failure of that host.
This page is editable only if you have enabled vSphere DRS.
Procedure
1 In the vSphere Web Client, browse to the Proactive HA cluster.
2 Click the tab.
3 Select vSphere Availability and click Edit.
4 Select Turn on Proactive HA.
5 Click Proactive HA Failures and Responses.
6 Select from the following conguration options.
Option Description
Automation Level
Determine whether host quarantine or maintenance mode and VM
migrations are recommendations or automatic.
n
Manual. vCenter Server suggests migration recommendations for
virtual machines.
n
Automated. Virtual machines are migrated to healthy hosts and
degraded hosts are entered into quarantine or maintenance mode
depending on the congured Proactive HA automation level.
Remediation
Determine what happens to partially degraded hosts.
n
Quarantine mode for all failures. Balances performance and
availability, by avoiding the usage of partially degraded hosts
provided that virtual machine performance is unaected.
n
Quarantine mode for moderate and Maintenance mode for severe
failure (Mixed). Balances performance and availability, by avoiding
the usage of moderately degraded hosts provided that virtual machine
performance is unaected. Ensures that virtual machines do not run
on severely failed hosts.
n
Maintenance mode for all failures. Ensures that virtual machines do
not run on partially failed hosts.
Host.Config.Quarantine and Host.Config.Maintenance privileges
are required to put hosts in Quarantine mode and Maintenance mode,
respectively.
To enable Proactive HA providers for this cluster, select the check boxes. Providers appear when their
corresponding vSphere Web Client plugin has been installed and the providers monitor every host in
the cluster. To view or edit the failure conditions supported by the provider, click the edit link.
7 Click OK.
vSphere Availability
32 VMware, Inc.