 |
» |
|
|
|
This section addresses the following topics: Default Monitoring Requests | |
A set of default monitoring requests is available for each monitor.
These default requests provide complete monitoring and protection
for the hardware resources under the control of the monitor. Table 3-1 describes the default monitoring requests that are
common for all monitors. Table 3-1 Default Monitoring Requests for Each Monitor Severity Levels | Default Notification Method |
|---|
All | textlog: /var/opt/resmon/log/event.log | MAJOR WARNING, SERIOUS, CRITICAL | syslog | | MAJOR WARNING,
SERIOUS, CRITICAL | console Note: Messages are not sent to the console by
default. | | MAJOR WARNING,
SERIOUS, CRITICAL | E-MAIL address: root |
| | | |  | NOTE: To gain greater control over what notification methods are used
to alert you when events occur, you must modify or add new monitoring
requests. You can add new notification methods or remove those that
are not required. Creating custom monitoring requests also enables
you to manage which severity levels you want reported. | | | | |
Table 3-2 describes the monconfig settings. Table 3-2 Monitoring Request Configuration Settings Setting | Description |
|---|
Criteria Thresholds | Identifies the severity level used
in conjunction with the criteria operator to generate an event message. | Criteria Operators | Identifies the arithmetic operator
used with the criteria threshold to control the events that are reported.
Following are the valid operators: < (less than)
<= (less than or equal to)
> (greater than)
>= (greater than or equal to)
! (not equal to) Following are
the numeric values corresponding to each severity level: CRITICAL = 5
SERIOUS = 4
MAJOR WARNING = 3
MINOR WARNING = 2
INFORMATIONAL = 1 |
The criteria
operators enable you to direct events of several severity levels using
the same notification method. For example, to direct both SERIOUS
and CRITICAL events using the same method, you must use the condition
>= SERIOUS. | Notification Method | Following are the available notification
methods: E-MAIL — Sends notification to the specified e-mail address
textlog — Sends notification to the specified file
SNMP — Sends notification using the SNMP traps
console — Sends notification to the system console
TCP — Sends notification to the specified target host and port
UDP — Sends notification to the specified target host and port
OPC — Sends notification to OpenView ITO applications (available only on systems with OpenView installed)
syslog — Sends notification to the system log You can select only one notification method for each monitor request.
Subsequently, you can create multiple requests to direct event notifications
to different targets. |
Table 3-3 describes the event severity levels. Table 3-3 Event Severity Levels Event Severity Level | Description | HP Serviceguard Response |
|---|
| CRITICAL | The event causes data loss, system
down time, or loss of other services. System operation
is impacted if the problem is left uncorrected, and the hardware must
not be used until the problem is corrected. You must take
immediate action to correct the problem. | If HP Serviceguard is installed and the device on which the
error is detected is CRITICAL, a
package failover occurs. | | SERIOUS | The event can cause data loss, system
down time, or loss of other services if left uncorrected. System operation and normal use of the hardware might be impacted. You must repair the problem as soon as possible. | If HP Serviceguard is installed and the device
on which the error is detected is SERIOUS, a package failover occurs. | | MAJOR WARNING | The event can escalate to a SERIOUS condition if left uncorrected. System operation might not be impacted and normal use of the hardware
can continue. You must repair the problem at a convenient
time. | If HP Serviceguard is
installed and the device on which the error is detected is MAJOR WARNING, a package fail-over does not occur. | | MINOR WARNING | Event escalation to a more severe
condition does not occur if the problem is left uncorrected. System operation is not interrupted and normal use of the hardware
can continue. You can repair the problem at a convenient
time. | If HP Serviceguard is
installed and the device on which the error is detected is MINOR WARNING, a package failover does not occur. | | INFORMATION | The event occurs as part of the
normal operation of the hardware. No action is required. | If HP Serviceguard is installed
and the device on which the error is detected is INFORMATION, a package failover does not occur. |
EMS Hardware Monitor Configuration Files | |
The following configuration files control the operation of the
EMS Hardware Monitors: Global Monitor Configuration File: The Global Monitor Configuration
File includes settings that are common to all monitors. All monitors
use these settings unless the settings are overridden by the settings
in the Monitor-Specific Configuration File. Monitor-Specific Configuration File: Each monitor includes a Monitor-Specific Configuration File with optimized settings.
The settings in the Monitor-Specific Configuration File are specific
to the monitor. The settings defined in the monitor-specific file
override the settings defined in the Global Configuration File. Client Configuration File:
Multiple-View monitors enable you to create a different Client Configuration
File for each target. Settings defined in the Client Configuration
File override comparable settings defined in either the Global or
the Monitor-Specific Configuration File.
Monitor-Specific and Global Configuration File ParametersThe Monitor-Specific and Global Configuration files include
a set of parameters that you can use to configure the monitors. Following
are the common operating parameters of the Monitor-Specific and the
Global Configuration Files for all non-Multiple-View monitors: Polling Interval — Identifies the frequency
at which the monitor polls the hardware for status. This interval
is selected to provide current device status without seriously impacting
system performance. Repeat Frequency — Indicates how often the
same event must be reported. A value of once a day is used as the
default repeat frequency. Severity Action — Determines whether the severity
level is communicated to EMS for reporting or ignored Event Definition — Identifies each event generated
by the monitor, defines its severity level, and determines what action
must be taken. Actions include ignoring the event, sending it to EMS,
or using the default action defined by the Severity Action setting.
| | | | | NOTE: Changes made to a Monitor-Specific Configuration File are invoked
at the next polling interval or when an event is generated, which
ever happens first. In either of these situations, the monitor reads
its configuration file for any change and implements any new settings. | | | | |
Startup Configuration FileEach monitor has its own Startup Configuration File, which contains the monitoring
requests currently defined for the monitor. The entries in the Startup
Configuration File are used to create monitoring requests for the
monitor at startup, after the execution of the IOSCAN utility or when
using the monconfig utility to manage
monitoring requests. Each monitoring request in the Startup Configuration File is
applicable to all instances of the monitor's hardware resources. An
identical set of default requests is included in the Startup Configuration
File for each monitor. You can modify the contents of the Startup Configuration File
by using the Hardware Monitoring Request Manager. When you use the
Hardware Monitoring Request Manager to create or to manage monitoring
requests, the result is stored as an entry in the monitor's Startup
Configuration File. If you select the All Monitors option for the
request, an entry is logged in the Startup Configuration File to all
the monitors. | | | | | NOTE: Changes made to a Startup Configuration File are invoked when
the system is restarted, after the execution of the IOSCAN utility,
or when you use the Hardware Monitoring Request Manager to manage
monitoring requests. For example, when you add, delete, or modify
a monitoring request using the Hardware Monitoring Request Manager,
the changes to the Startup Configuration File take effect immediately. | | | | |
Considerations for Modifying the Startup Configuration File
Settings HP recommends that you use the monconfig utility to create and manage your monitoring requests. Using the
monconfig utility, you can create requests for multiple monitors simultaneously.
The monconfig utility ensures that all request entries are formatted
correctly. Editing the configuration file enables you to use the COMMENT setting to add information that is included
in the event. Table 3-4 describes the Startup Configuration File entries. Table 3-4 Startup Configuration File Entries Keyword | Values | Description |
|---|
MONITOR (required) | A valid event monitor resource path | Identifies the monitor to which
the entry applies. All entries use the resource path for the monitor
being configured. | Criteria Threshold (required) | Following are the valid values: CRITICAL
SERIOUS
MAJOR_WARNING
MINOR_WARNING
INFORMATIONAL | Defines the severity level. It is used as the notification criteria
threshold. | Criteria Operator (required) | Following are the valid operators: < (less than)
<= (less than or equal to)
> (greater than)
>= (greater than or equal to)
! (not equal to) | Identifies the arithmetic operator used along
with the Criteria Threshold to control the events that must be 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. |
Table 3-5 describes the target entries of the Startup Configuration
File. Table 3-5 Startup Configuration File Target Entries Keyword | Values | Description |
|---|
Target Type (required) | Following are the valid values: UDP
TCP
OPC
SNMP
textlog
syslog
E-MAIL
console | The
method of notification used. | Target Type Modifier
required for the following target types: | Target UDP Host | Host name of the system to
which UDP events are sent | Target UDP Port | Port number on the
host that is used for network connection | Target TCP Host | Host name of the system to
which TCP events are sent | Target TCP Port | Port number on the
host that is used for network connection | Target USERLOG | Name of the log file to which
TCP events are sent | Target E-MAIL Address | E-mail address of the recipient
of the events | COMMENT: (Optional) | Any text string | An optional field, which is presented
as user data for each event meeting this criterion |
File Locations | |
Table 3-7 describes the files used in hardware monitoring. Table 3-6 File Locations Directories and Files | Description |
|---|
/usr/sbin/stm/uut/bin/tools/monitor/monitor_name | Monitor executable files. | /var/stm/config/tools/monitor/Global.cfg | Default Monitor Configuration
File. | /var/stm/config/tools/monitor/monitor_name.cfg | Monitor-Specific Configuration File. | /var/stm/config/tools/monitor/<monitor_name>.clcfg | Monitor Client Configuration
File. Available only for hardware monitors converted to Multiple-View
(predictive-enabled). | /var/stm/config/tools/monitor/<monitor_name>.sapcfg | Monitor Startup Configuration
File. | /var/stm/config/tools/monitor/<monitor_name>.psmcfg | PSM configuration file. | /etc/opt/resmon/lbin/monconfig | Hardware Monitoring Request
Manager file. | /etc/opt/resmon/lbin/startcfg_client | Startup client file. | /etc/opt/resmon/lbin/set_fixed | PSM set_fixed utility file. | /etc/opt/resmon/dictionary/<monitor_name>.dict | Monitor dictionary file. |
In the Table 3-7, monitor_name is the name
of a particular monitor, such as armmon. |
Printable version
