All fields are defined as optional. In case of a reconfiguration,
fields left unset are not changed.
|
Name
|
Type
|
Description
|
| admissionControlEnabled | xsd:boolean |
Flag to indicate whether or not strict admission control is enabled.
With strict admission control, a virtual machine cannot power on
if doing so would violate the configured failoverLevel.
|
| admissionControlPolicy | ClusterDasAdmissionControlPolicy |
Admission Control policy to use for VMware HA.
Since vSphere API 4.0
|
| defaultVmSettings | ClusterDasVmSettings |
Cluster-wide defaults for per-VM VMware HA settings. In the case where no settings
are specified for a specific VM in ClusterDasVmConfigInfo then the values here
will be used as the defaults.
Since VI API 2.5
|
| enabled | xsd:boolean |
Flag to indicate whether or not VMware HA feature is enabled.
|
| failoverLevel | xsd:int | Deprecated.
As of vSphere API 4.0, use
ClusterFailoverLevelAdmissionControlPolicy to set
admissionControlPolicy.
Configured failover level. This is the number of physical host failures
that can be tolerated without impacting the ability to satisfy the
minimums for all running virtual machines. Acceptable values range from one to
four.
|
| hostMonitoring | xsd:string |
This property indicates whether or not VMware HA Host Monitoring service is
enabled. The default value is "enabled" and meaningful only when HA is enabled.
When Host Monitoring service is disabled HA does not acting upon hosts'
failures. The rest of the cluster operations follow normal processing. While
disabled, no configuration information is lost and re-enabling the service
is a lightweight operation.When Host Monitoring is disabled, it does not
affect other services such as VM Health Monitoring.
Please see ServiceState
Since vSphere API 4.0
|
| option | OptionValue[] |
Advanced settings.
|
| vmMonitoring | xsd:string |
This property indicates whether or not VMware HA VM Health Monitoring service is
enabled. The default value is "disabled". Enabled is meaningful only when HA is enabled.
When VM Health Monitoring is disabled, reaction to VM failures is
temporarily disabled until the service is enabled again. While disabled, no
configuration information is lost and re-enabling the service is a lightweight
operation. When VM Health Monitoring is disabled, it does not affect other
services such as Host Monitoring.
Please see ServiceState
Since vSphere API 4.0
|
|
Properties inherited from DynamicData |
| dynamicProperty, dynamicType |