Peripheral Status Monitor

This section addresses the following topics:

PSM Components

PSM is installed along with the EMS Hardware Monitors. PSM comprises the following components:

The psmctd daemon — The Peripheral Status Client or target daemon used to monitor the status of hardware resources.
The psmmon utility — A utility used to monitor the status of resources recognized by the psmctd daemon.
The set_fixed utility — The utility used to manually change the status of a hardware resource from DOWN to UP. You can use this utility for monitors that cannot perform the operation automatically.

For more information on the PSM components, see psmctd(1M), psmmon(1M), and set_fixed(1M).

PSM States

The PSM can have three status conditions. You can use these values to define a monitoring request.

Table 3-8 describes PSM conditions.

Table 3-8 PSM Status

Condition	Description
`UP`	Hardware is operating normally.
`DOWN`	An event has occurred that indicates a hardware failure.
`UNKNOWN`	Unable to determine the status of the hardware. Treat this state as `DOWN`.




	NOTE: You can use the PSM to create hardware status monitoring requests using EMS even if you are not using HP Serviceguard. This option enables you to receive notification for changes in the hardware resource status. After creating a PSM monitoring request, when a hardware event occurs, you might be alerted twice—once for the event itself and again if the event causes the status of the resource to change to `DOWN`.

Peripheral Status Monitor Configuration File

The PSM Configuration File controls the interaction between the PSM and a monitor. This file defines what severity levels result in the DOWN status being reported and what action, if any, is required to return the hardware to UP status. A monitor that does not include a PSM Configuration File is not monitored by the PSM.




	NOTE: The PSM checks its configuration files every 10 seconds and executes the changes in the file. If the hardware configuration has changed, and the PSM is communicating with all the monitors to determine what their resources are, it may take a few minutes for changes to a configuration file to take effect.

Table 3-9 describes the fields in the PSM Configuration File.

Table 3-9 PSM Configuration File Fields

Keyword

Values

Description

MONITOR_RESOURCE_NAME (required)

A valid monitor resource path name

Identifies the monitor to which the entry applies.

PSM_RESOURCE_NAME (optional)

A valid PSM (status) resource path name

Relates to MONITOR_RESOURCE_NAME.

If not specified, the default is created in the MONITOR_RESOURCE_NAME by replacing the word “events” with the word “status”.

MONITOR_STATE_HANDLING (optional)

Following are the valid values:

NO_UP_CONTROL (default) — The monitor uses the severity mapping of events to control the DOWN state. The UP state is controlled by the set_fixed command.
UP_STATE_CONTROL — The monitor uses the severity mapping of events to control the DOWN state. The monitor itself controls the UP state.
ALL_STATE_CONTROL — The monitor controls both states.

Identifies the type of state handling the monitor performs.

DOWN_SEVERITY_THRESHOLD (optional)

Following are the valid values:

CRITICAL
SERIOUS (default)
MAJOR WARNING
MINOR WARNING INFORMATIONAL

Defines the event severity level used with DOWN_SEVERITY_OPERATOR.

This keyword is required only if DOWN_SEVERITY_OPERATOR is specified).

DOWN_SEVERITY_OPERATOR (optional)

Following are the valid values:

=
!=
<
<=
>
>= (default)

Defines the operator used with the event severity and DOWN_SEVERITY_THRESHOLD as operands.

The event severity received is the left operand and the DOWN_SEVERITY_THRESHOLD value is the right operand.

Monitoring Request Parameters

This section discusses the monitoring request parameters.

Specifying When to Send Events — <Notify>

Table 3-10 describes the PSM status.

Table 3-10 PSM Status

Option

Description

When value is ...

Enables you to define the conditions under which you want to be notified. Following are the available operators:

=
not equal
>
>=
<
<=

Values returned by the monitor are UP, DOWN, and UNKNOWN. Text values are mapped to numerical values.

When value changes

Notifies you when the value changes. You can use this parameter for a resource whose value does not change frequently, but you need to know each time the value changes.

At each interval

Notifies you at each polling interval. You can use this option to set reminders or to gather data for system analysis. However, you must use this option for only a small number of resources at a time, and with long polling intervals of several minutes or hours. Otherwise, it affects system performance.

Determining the Frequency of Events — <Options>

When you select When value is ... from the <Notify> options, the <Options> window is displayed. You must select one or more options listed in Table 3-11 to specify the frequency of events.

Table 3-11 describes the options for the frequency of events.

Table 3-11 PSM Settings

Option	Description
Initial	Enables you to test a new request to ensure that it is sending alerts to the specified destinations.
Repeat	Sends an alert at each polling interval as long as the notify condition is met. You must use this option for important alerts. Otherwise, it increases CPU usage and populates log files and alert windows.
Return	Enables you to track the status when a condition returns to its previous value.

When you select When value changes or At each interval from the <Notify> options, the following values are selected by default:

Initial — Selected
Repeat — Not selected
Return — Not selected

Setting the Polling Interval — <Polling Interval>

The polling interval specifies how often EMS checks the PSM for changes in the hardware status. A short polling interval ensures that you have recent data. However, a short polling interval can cause increased usage of CPU and system resources.

Consider the following points before setting the polling interval:

Set a short polling interval of 30 seconds or less when making a quick failover decision.
Set a polling interval of 5 minutes for monitoring less critical resources.
Set a polling interval of 4 hours to monitor failed disks that are not essential to the system. However, you must replace the disk in the next few days.

Selecting Protocols for Sending Events — <Notify Via>

You can specify the method that EMS must use to send events by using the <Notify via> option. Following are the notification methods:

The opcmsg ITO Method

This option sends messages to IT Operations (ITO) applications using the opcmsg daemon. You must install IT Operation 4.0 or later on the resource server to use this option.

Following are the ITO message severity options:

Critical
Major
Minor
Warning
Normal

A specified severity level other than Normal is returned under the following conditions:

The When value is ... condition is TRUE.
The When value changes condition is TRUE.

For more information about configuring notification severity levels, see the HP OpenView IT/Operations Administrators Task Guide at:

http://www.docs.hp.com

You can also find templates for configuring ITO and network node events at:

http://www.hp.com/go/ha

To set the opcmsg ITO, complete the following steps:

Specify the notification type in the <Notify> list.
Select the opcmsg ITO option in the <Notify via> list.
Select the severity level in the <Severity> list.

Events conforming to the selected settings are sent to ITO applications.

SNMP Traps

The SNMP option sends messages to applications using SNMP traps, such as Network Node Manager. For more information about configuring SNMP traps, see HP OpenView Using Network Node Manager (P/N J1169-90002) at:

http://www.docs.hp.com

The following traps are used by EMS:

EMS_ENTERPRISE_OID     "1.3.6.1.4.1.11.2.3.1.7"
EMS_NORMAL_OID         "1.3.6.1.4.1.11.2.3.1.7.0.1" - Normal notification
EMS_ABNORMAL_OID       "1.3.6.1.4.1.11.2.3.1.7.0.2" - Abnormal notification
EMS_REBOOT_OID         "1.3.6.1.4.1.11.2.3.1.7.0.3" - Reboot notification
EMS_RESTART_OID        "1.3.6.1.4.1.11.2.3.1.7.0.4" - Restart notification
EMS_NORMAL_SEV_OID     "1.3.6.1.4.1.11.2.3.1.7.0.5" - Problem Event w/Normal Severity notification
EMS_WARNING_SEV_OID    "1.3.6.1.4.1.11.2.3.1.7.0.6" - Problem Event w/Warning Severity notification
EMS_MINOR_SEV_OID      "1.3.6.1.4.1.11.2.3.1.7.0.7" - Problem Event w/Minor Severity notification
EMS_MAJOR_SEV_OID      "1.3.6.1.4.1.11.2.3.1.7.0.8" - Problem Event w/Major Severity notification
EMS_CRITICAL_SEV_OID   "1.3.6.1.4.1.11.2.3.1.7.0.9" - Problem Event w/Critical Severity notification

You must specify the following ITO message severity levels for both normal and abnormal events:

Critical
Major
Minor
Warning
Normal

Certain SNMP trap monitoring requests can map directly to severity levels. For these requests, a toggle button <Map severity from value> is displayed. If you select this, options selected in <Severity> are ignored.

A specified severity level other than Normal is returned under the following conditions:

The When value is ... condition is TRUE.
The When value changes condition is TRUE.

To set the SNMP trap, complete the following steps:

Specify the notification type in the <Notify> list.
Select the SNMP option in the <Notify via> list.
Select the severity level in the <Severity> list.

The TCP and UDP Options

Both of these options send TCP or UDP encoded events to the target host name and the port specified for the specified request.

To set the TCP or UDP options, complete the following steps:

Select TCP or UDP, as appropriate, in the <Notify via> list.
Specify the target host name and the port.

The E-mail Option

The e-mail option sends events to the specified e-mail address.

To set e-mail notification, complete the following steps:

Select the E-mail option from the <Notify via> list.
Specify the complete e-mail address in the E-mail Address field.

The syslog Option

The syslog option sends events to the system log.

For an abnormal event, a system logging level error is associated with the logged message.

An abnormal event message (error) is returned under the following conditions:

The When value is . . . condition is TRUE.
The When value changes condition is TRUE.

To set for a system log notification, select syslog in the <Notify via> list.

The console Option

The console option sends events to the system console.

To set the console notification, select console in the <Notify via> list.

The textlog Option

The textlog option sends events to the specified file.

To set textlog notification, complete the following steps:

Select the textlog option in the <Notify via> list.
A default path, /var/opt/resmon/log/event.log, is displayed when you select textlog.
Specify the file name and path in the File Path field.

Adding a Notification Comment — <Comment>

The notification comment is useful for sending task reminders to the recipients of an event. For example, you can add the name of the person to contact if an event occurs. If you have configured HP Serviceguard package dependencies, you can enter the package name as a comment in the corresponding request.

Peripheral Status Monitor

Technical documentation

» Table of Contents

» Glossary

» Index

PSM Components

PSM States

Peripheral Status Monitor Configuration File

Monitoring Request Parameters

Specifying When to Send Events — <Notify>

Determining the Frequency of Events — <Options>

Setting the Polling Interval — <Polling Interval>

Selecting Protocols for Sending Events — <Notify Via>

Adding a Notification Comment — <Comment>