Some Hewlett-Packard products include their own monitors within their
product hierarchy. For example, ATM Adapter for HP/9000 Servers,
HP OTS 9000 or STM (Support Tools Manager) for HP 9000 hardware
monitoring. If this type of product is installed on the system,
then its top-level resource class also appears in the Add or Copy Monitoring Request screen.
NOTE: After installation some monitors must be enabled before
their resource classes appear in the EMS Add or Copy Monitoring Request screen. For example, the STM hardware monitors.
Refer to the documentation for your monitor for instructions on
enabling or starting your monitor.
Similarly, top-level resource classes belonging to user-written monitors,
created using the procedures described in Writing Monitors for
the Event Monitoring Service (EMS) (HP Part Number B7611-90016),
are discovered and displayed here.
To obtain additional information about any particular monitor:
Review the monitor dictionary file:
From the command line, go to the /etc/opt/resmon/dictionary directory.
Information about each monitor can be found in the .dict files.
View the monitor dictionary file.
The file name corresponds to its monitor. The file extension
is .dict. For example, the MIB Monitor dictionary filename is mibmond.dict.
Review the man page.
The man page name can be found in the dictionary file with
the monitor's name. If a man page was created it is listed
in the MONITOR entry section of the dictionary file.
View the resource class or instance description
through EMS.
The EMS Monitoring Request Parameters screen has a View Resource Description button that displays additional information supplied
by the selected resource. See Figure 2-2 “EMS Monitoring Request
Parameters Screen”.
When you monitor a resource, you actually monitor one or more specific
instances of its resource class. View the resource instances associated
with the selected resource class in the Resource Instance field. See Figure 2-3 “Add or Copy Monitoring Request Screen”.
If the resource class has subclasses, those subclasses are
listed in the Resource Classes field.
Asynchronous monitors are event-driven, rather than polled.
They generate messages as events occur, without regard for relative importance.
Therefore, if the resource instance is an asynchronous monitor,
the Current Value field does not apply, and the field displays n/a.
Figure 2-3 Add or Copy Monitoring Request Screen
Select a specific instance or the wildcard (All
Instances).
The (*) wildcard is a convenient way to create
many requests at once. Most systems have more than one disk or network
card, and many have several disks. To avoid having to create a monitor
request for each disk, select *(All Instances) in
the Resource Instance box. The *(All Instances) listing
is always the first item on the list. See the figure above.
Wildcards are available only when all instances of a subclass
are of the same resource type and there are multiple instances.
Selecting the wildcard applies the monitor to all the instances
of that resource type. Wildcards are not available for resource
classes. For example, a wildcard is available for the status instances
in the subclass, /system/filesystem/availMb. A wildcard is not available for the entire volume
group resource class, /vg.
Click OK.
You see the Monitoring Request Parameters screen. See Chapter 4, "Defining a Monitoring
Request."
Printable version
