Online Diagnostics (EMS and STM) Administrator's Guide March 2012
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 16 PSM Status
DescriptionCondition
Hardware is operating normally.UP
An event has occurred that indicates a hardware failure.DOWN
Unable to determine the status of the hardware. Treat this state as DOWN.UNKNOWN
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 17 PSM Configuration File Fields
DescriptionValuesKeyword
Identifies the monitor to which the entry
applies.
A valid monitor resource path nameMONITOR_RESOURCE_NAME
(required)
Relates to MONITOR_RESOURCE_NAME.A valid PSM (status) resource path
name
PSM_RESOURCE_NAME (optional)
If not specified, the default is created in the
MONITOR_RESOURCE_NAME by replacing
the word “events” with the word “status”.
Peripheral Status Monitor 39