6.5.1

Table Of Contents
In an environment with multiple vCenter Server systems that are connected to the same vCenter Server
Single-Sign On domain, the vSphere Web Client that you congured for live refresh displays recent tasks
and alarms for all the vCenter Server instances in the domain. However, if you log in to a dierent
vSphere Web Client, you will not see live refresh for recent tasks or alarms for any of the vCenter Server
systems in the vCenter Server Single-Sign On domain.
In this example, you have two vCenter Server instances (A and B) connected to the same vCenter Server
Single-Sign On domain. With each of the vCenter Server instances, you installed a vSphere Web Client
instance.
You log in to vSphere Web Client A by using https://hostnameA/vsphere-client/.
You log in to vSphere Web Client B by using https://hostnameB/vsphere-client/.
You enable live refresh of recent tasks and alarms on vSphere Web Client A, and log out from it.
You can observe the following results:
n
You log in to vSphere Web Client A from https://hostnameA/vsphere-client/. You do not see any
recent tasks or alarms in the respective Recent Tasks or Alarms portlets.
n
You log in to vSphere Web Client A from https://hostnameA:9443/vsphere-client/. You can see live
refresh of recent tasks and alarms for all the users currently performing operations on both
vCenter Server systems in the vCenter Server Single-Sign On domain.
n
You log in to vSphere Web Client B from https://hostnameB/vsphere-client/. You can see the recent
tasks and alarms of only operations that you perform on vCenter Server system A or vCenter Server
system B. Only after you manually refresh the vSphere Web Client B you see the latest recent tasks and
alarms that result from operations performed by other users on vCenter Server system A and
vCenter Server system B.
Set an Alarm
You can monitor inventory objects by seing alarms on them. Seing an alarm involves selecting the type of
inventory object to monitor, dening when the alarm triggers, for how long the alarm is on, and dening
actions that are performed as a result of the alarm being triggered. You dene alarms in the alarm denition
wizard. You access the alarm denition wizard from the Monitor tab, under Issues.
When you create an alarm, you select the alarm type, the type of inventory object, and the type of activity
that trigger the alarm. An activity that triggers an alarm can be any of the following:
n
A specic condition or a state of the inventory object.
n
An event that occurs on the object.
Depending on the type of activity that you choose to monitor, the options on the Triggers page that follow
the General page in the alarm denitions wizard, change.
After dening the triggers, dene the actions that the trigger causes.
Prerequisites
Log in to the vSphere Web Client.
Required Privilege: Alarms.Create alarm or Alarms.Modify alarm
n
Create or Edit Alarms on page 111
To monitor your environment, you can create and modify alarm denitions in the vSphere Web Client.
You can view alarm seings from any object, but you can modify seings only through the object on
which the alarm is dened.
n
Specify Alarm Name, Description, and Type on page 111
General seings of an alarm denition include alarm name, description, and type. You can also enable
and disable the alarm from the general seings page.
vSphere Monitoring and Performance
110 VMware, Inc.