Information Technology Reference
In-Depth Information
Alarms can have more than just one trigger condition. The alarms you've created so far had
only a single trigger condition. For an example of an alarm that has more than one trigger con-
dition, look at the built-in alarm for monitoring host connection and power state. Figure 13.5
shows the two trigger conditions for this alarm. Note that that
ALL
is selected in the “Trigger if”
drop-down menu; it ensures that only powered-on hosts that are not responding will trigger the
alarm.
Figure 13.5
You can combine
multiple triggers to
create more com-
plex alarms.
It might seem obvious, but it's important to note that you can have more than one alarm for
an object.
As with any new alarm, testing its functionality is crucial to make sure you get the desired
results. You might i nd that the thresholds you coni gured are not optimized for your environ-
ment and either are not activating the alarm when they should or are activating the alarm when
they shouldn't. In these cases, edit the alarm to set the thresholds and conditions appropriately.
Or, if the alarm is no longer needed, right-click the alarm, and choose Remove to delete it.
You'll be able to edit or delete alarms only if two conditions are met. First, the user account
with which you've connected to vCenter Server must have the appropriate permissions granted
for you to edit or delete alarms. Second, you must be attempting to edit or delete the alarm from
the object on which it was dei ned. Think back to the discussion on alarm scope and this makes
sense. You can't delete an alarm from the datacenter object when that alarm was dei ned on the
vCenter Server object. You must go to the object where the alarm was dei ned to edit or delete
the alarm.
Now that you've seen some examples of creating alarms—and keep in mind that creating
alarms for other objects within vCenter Server follows the same basic steps—let's take a look at
managing alarms.
Managing Alarms
Several times so far in this chapter we've directed you to the Alarms Dei nitions tab within the
vSphere Web Client. Until now, you've been working with the dei nitions, looking at dei ned
alarms. There is, however, another view to the alarms, and that's the Triggered Alarms view.
Figure 13.6 shows the Triggered Alarms view, which you access by selecting an object within the
vCenter Web Client, then clicking the Monitor tab
➢
➢
Issues
Triggered Alarms.
