6.5.1

Table 11‑2. vCenter Server Events (Continued)
Event Type Event Name
Exiting Standby mode (about to power on the host)
DrsExitingStandbyModeEvent
Successfully exited Standby mode (power on succeeded)
DrsExitedStandbyModeEvent
For more information about creating and editing alarms, see the vSphere Monitoring and Performance
documentation.
If you use monitoring software other than vCenter Server, and that software triggers alarms when physical
hosts are powered o unexpectedly, you might have a situation where false alarms are generated when
vSphere DPM places a host into standby mode. If you do not want to receive such alarms, work with your
vendor to deploy a version of the monitoring software that is integrated with vCenter Server. You could also
use vCenter Server itself as your monitoring solution, because starting with vSphere 4.x, it is inherently
aware of vSphere DPM and does not trigger these false alarms.
Using DRS Affinity Rules
You can control the placement of virtual machines on hosts within a cluster by using anity rules.
You can create two types of rules.
n
Used to specify anity or anti-anity between a group of virtual machines and a group of hosts. An
anity rule species that the members of a selected virtual machine DRS group can or must run on the
members of a specic host DRS group. An anti-anity rule species that the members of a selected
virtual machine DRS group cannot run on the members of a specic host DRS group.
See “VM-Host Anity Rules,” on page 88 for information about creating and using this type of rule.
n
Used to specify anity or anti-anity between individual virtual machines. A rule specifying anity
causes DRS to try to keep the specied virtual machines together on the same host, for example, for
performance reasons. With an anti-anity rule, DRS tries to keep the specied virtual machines apart,
for example, so that when a problem occurs with one host, you do not lose both virtual machines.
See “VM-VM Anity Rules,” on page 87 for information about creating and using this type of rule.
When you add or edit an anity rule, and the cluster's current state is in violation of the rule, the system
continues to operate and tries to correct the violation. For manual and partially automated DRS clusters,
migration recommendations based on rule fulllment and load balancing are presented for approval. You
are not required to fulll the rules, but the corresponding recommendations remain until the rules are
fullled.
To check whether any enabled anity rules are being violated and cannot be corrected by DRS, select the
cluster's DRS tab and click Faults. Any rule currently being violated has a corresponding fault on this page.
Read the fault to determine why DRS is not able to satisfy the particular rule. Rules violations also produce
a log event.
N VM-VM and VM-Host anity rules are dierent from an individual host’s CPU anity rules.
Create a Host DRS Group
A VM-Host anity rule establishes an anity (or anti-anity) relationship between a virtual machine DRS
group with a host DRS group. You must create both of these groups before you can create a rule that links
them.
Procedure
1 Browse to the cluster in the vSphere Web Client navigator.
2 Click the  tab.
vSphere Resource Management
86 VMware, Inc.