6.5.1

Table Of Contents
Create VM-VM Affinity Rules for MSCS Virtual Machines
For MSCS virtual machines in a cluster, you must create VM-VM anity or anti-anity rules. VM-VM
anity rules specify which virtual machines should be kept together on the same host (for example, a
cluster of MSCS virtual machines on one physical host). VM-VM anti-anity rules specify which virtual
machines should be kept apart on dierent physical hosts (for example, a cluster of MSCS virtual machines
across physical hosts).
For a cluster of virtual machines on one physical host, use anity rules. For a cluster of virtual machines
across physical hosts, use anti-anity rules.
N vMotion is supported only for a cluster of virtual machines across physical hosts with pass-through
RDMs. For a cluster of virtual machines on one physical host and a cluster of virtual machines across
physical hosts with non-pass-through RDMs, vMotion is not supported.
Procedure
1 Browse to the cluster in the vSphere Web Client navigator.
2 Click .
3 Under , click VM/Host Rules.
4 Click Add.
5 In the Create VM/Host Rule dialog box, type a name for the rule.
6 From the Type drop-down menu, select a rule.
n
For a cluster of virtual machines on one physical host, select Keep Virtual Machines Together.
n
For a cluster of virtual machines across physical hosts, select Separate Virtual Machines.
7 Click Add.
8 Select the two virtual machines to which the rule applies and click OK.
9 Click OK.
Enable Strict Enforcement of Affinity Rules (MSCS)
To ensure that anity and anti-anity rules are strictly applied, set an advanced option for vSphere DRS.
Seing the advanced option ForceAnePoweron to 1 will enable strict enforcement of the anity and anti-
anity rules that you created.
Procedure
1 Browse to the cluster in the vSphere Web Client navigator.
2 Click .
3 Under Services, select vSphere DRS and click Edit.
4 Expand Advanced Options and click Add.
5 In the Option column, type ForceAffinePoweron.
6 In the Value column, type 1.
7 Click OK.
Setup for Failover Clustering and Microsoft Cluster Service
30 VMware, Inc.