6.0.1

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.
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 Virtual SAN datastores. If a
virtual machine's configuration and VMDK files are located only on Virtual SAN 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 Virtual SAN.
In addition to the previous restrictions, the following types of IPv6 address types are not supported for use
with the vSphere HA isolation address or management network: link-local, ORCHID, and link-local with
zone indices. Also, the loopback address type cannot be used for the management network.
NOTE To upgrade an existing IPv4 deployment to IPv6, you must first disable vSphere HA.
Creating and Configuring a vSphere HA Cluster
vSphere HA operates in the context of a cluster of ESXi (or legacy ESX) hosts. You must create a cluster,
populate it with hosts, and configure vSphere HA settings before failover protection can be established.
When you create a vSphere HA cluster, you must configure a number of settings that determine how the
feature works. Before you do this, identify your cluster's nodes. These nodes are the ESXi hosts that will
provide the resources to support virtual machines and that vSphere HA will use for failover protection. You
should then determine how those nodes are to be connected to one another and to the shared storage where
your virtual machine data resides. After that networking architecture is in place, you can add the hosts to
the cluster and finish configuring vSphere HA.
vSphere Availability
32 VMware, Inc.