Table of Contents
Advertisement
Hardware Monitor Configuration Files
Startup Configuration File
Considerations for Modifying the Startup Configuration File Settings
While you can edit the contents of the startup configuration file directly, the better approach is to use the
Hardware Monitoring Request Manager (monconfig) to create and manage your monitoring requests. Using
the monitoring request manager you can create requests for multiple monitors simultaneously. And the
Hardware Monitoring Request Manager ensures that all request entries are formatted correctly.
The only benefit that editing the configuration file offers is that you can use the COMMENT setting to add
information that will be included with the event.
Table 5-2
Startup Configuration File Entries
Keyword
MONITOR (required)
Criteria Threshold (required)
Criteria Operator (required)
118
Values
A valid event monitor
resource path
Valid values include:
CRITICAL
SERIOUS
MAJOR_WARNING
MINOR_WARNING
INFORMATIONAL
Valid operators are:
%< (less than)
%<= (less than or equal to
)
> (greater than)
>= (greater than or equal
to)
! (not equal to)
Description
Identifies the hardware
event monitor to which
the entry applies. All
entries must use the
resource path for the
monitor being
configured.
Note: This must the first
keyword in each entry
Defines the severity
level used as the
notification criteria
threshold.
This value identifies the
arithmetic operator
used with the criteria
threshold to control
what events are
reported. The operator
treats each severity
level as a numeric value
assigned as follows:
Critical = 5
Serious = 4
Major warning = 3
Minor warning = 2
Informational = 1
The event severity
received is the left
operand and the
Criteria Threshold value
is the right operand.
Chapter 5
Advertisement
Table of Contents
