6.7

Table Of Contents
n
VM-Host affinity rules place specified virtual machines on a particular host or a member of a defined
group of hosts during failover actions.
When you edit a DRS affinity rule, you must use vSphere HA advanced options to enforce the desired
failover behavior for vSphere HA.
n
HA must respect VM anti-affinity rules during failover -- When the advanced option for VM anti-
affinity rules is set, vSphere HA does not fail over a virtual machine if doing so violates a rule.
Instead, vSphere HA issues an event reporting there are insufficient resources to perform the failover.
n
HA should respect VM to Host affinity rules during failover --vSphere HA attempts to place VMs
with this rule on the specified hosts if at all possible.
For more information, see vSphere HA Advanced Options.
Note vSphere HA can restart a VM in a DRS-disabled cluster, overriding a VM-Host affinity rules
mapping if the host failure happens soon (by default, within 5 minutes) after setting the rule.
Other vSphere HA Interoperability Issues
To use vSphere HA, you must be aware of the following additional interoperability issues.
VM Component Protection
VM Component Protection (VMCP) has the following interoperability issues and limitations:
n
VMCP does not support vSphere Fault Tolerance. If VMCP is enabled for a cluster using Fault
Tolerance, the affected FT virtual machines will automatically receive overrides that disable VMCP.
n
VMCP does not detect or respond to accessibility issues for files located on vSAN datastores. If a
virtual machine's configuration and VMDK files are located only on vSAN datastores, they are not
protected by VMCP.
n
VMCP does not detect or respond to accessibility issues for files located on Virtual Volume
datastores. If a virtual machine's configuration and VMDK files are located only on Virtual Volume
datastores, they are not protected by VMCP.
n
VMCP does not protect against inaccessible Raw Device Mapping (RDM)s.
IPv6
vSphere HA can be used with IPv6 network configurations, which are fully supported if the following
considerations are observed:
n
The cluster contains only ESXi 6.0 or later hosts.
n
The management network for all hosts in the cluster must be configured with the same IP version,
either IPv6 or IPv4. vSphere HA clusters cannot contain both types of networking configuration.
n
The network isolation addresses used by vSphere HA must match the IP version used by the cluster
for its management network.
n
IPv6 cannot be used in vSphere HA clusters that also utilize vSAN.
vSphere Availability
VMware, Inc. 29