beautypg.com

Client configuration file, Clients: targets for events, Creating a client configuration file (*.clcfg) – HP B6191-90029 User Manual

Page 95: Verifying monitors with a test event

background image

Chapter 5

Hardware Monitor Configuration Files

Client Configuration File

95

Client Configuration File

As of the June 2000 release, several of the hardware monitors have been converted to be multiple-view. These
monitors use an additional file for configuration, the Client Configuration File (for example,
default_disk_em.clcfg.)

The immediate purpose of this change is to enable HP Support Applications to work with hardware monitors.
There will also be long-term benefits, as well.

Clients: Targets for Events

When a hardware monitor detects an event, it can send an event message to one or more targets (“clients”).
Previously, EMS hardware monitors generated events in the same way for all targets. The problem is that
different targets, such as HP Support, may have different requirements for events.

The June 2000 release introduced the Multiple-View feature to several monitors; this feature will be added to
most hardware monitors in future releases.

Creating a Client Configuration File (*.clcfg)

With Multiple-View hardware monitors, you can create a different Client Configuration File (*.clcfg) for each
target. In this file, you can specify:

The text to be included in event messages.

“Qualification requirements”: the time or value thresholds a problem must meet in order to generate an
event. For example, the default time threshold might be to send an event if the problem is seen six times
in 24 hours; however, HP Support may want to see the event three times in 24 hours. Another example:
the default value threshold might be to send the event when the value associated with the problem is
greater than or equal to 80, but HP Support may want to see the event when the value is greater than or
equal to 70.

Events to be enabled/disabled for a given target. For example, event 1 may be enabled for target #1, but
disabled for target #2.

Severity level for an event sent to a given target. For example, event 3 may have a severity level of
CRITICAL for target #1, but a severity level of MAJOR_WARNING for target #2.

The default Client Configuration File (*.clcfg) is:

/var/stm/config/tools/monitor/default_MONITOR_NAME.clcfg

For example:

/var/stm/config/tools/monitor/default_disk_em.clcfg

The Client Configuration File for the HP Support Applications client would be:

/var/stm/config/tools/monitor/xxx_disk_em.clcfg

Verifying Monitors with a Test Event

As of the June 2000 release of the diagnostics, a standalone program is available to cause multiple-view EMS
hardware monitors to generate a test event:

/opt/resmon/bin/send_test_event