EMS Hardware Monitors (logo)

UPS Monitor (dm_ups)


Monitor Description | Configuration Files


Monitor Description

The UPS Monitor is designed to monitor all Uninterruptible Power System (UPS) devices connected to a system through RS-232 cables and configured to communicate with the UPS daemon named ups_mond. The UPS communications can be configured through the HP System Administration Manager (SAM). Once this communication is established, ups_mond will interact directly with each configured UPS on the system. The ups_mond daemon will send information it receives from each UPS to dm_ups.

The communication channel between ups_mond and dm_ups is a fifo pipe. Basically, dm_ups will sleep until data is sent from ups_mond down the pipe. Then it will awake, read the data and generate an event. During each polling interval, the monitor will check that the fifo connection with ups_mond still exists. If not, it attempts to reconnect to ups_mond.

The monitor is launched automatically when the system is started, ensuring that the UPS hardware is protected from undetected hardware failure.

Release History

September 2000 Release (Support Plus Media) and HP-UX 11i: Initial release. Includes Multiple-view ("Predictive-enabled") support.

Supported Products

 HP PowerTrust
A2941A (600VA)
A2994A (1300VA)
A2996B (1.3kVA)
A2997B (1.8kVA)
A2998B (3.0kVA)
A3589B (5.5kVA)
 HP PowerTrust II-LR
A1353A (2.0kVA 120V)
A1354A (2.0kVA 240V)
A1356A (3.0kva 240V)
 HP PowerTrust II-MR
A6583A (4.0kW 240V)
A6584A (6.5kW 240V)
A6585A (8.0kW 240V)

Special Requirements

Does not support S700 systems (HP-UX workstations).
For September 2000 releases to present the following patches are needed:

Resource Path

Event monitoring: /system/events/dm_ups
Status monitoring: /system/status/dm_ups

Monitor Name

/usr/sbin/stm/uut/bin/tools/monitor/dm_ups

PSM State Control

The set_fixed utility must be used to return a hardware resource to the UP state following a failure. The monitor does not support automatic state control. (See "Using the set_fixed Utility to Restore Hardware UP State" in the EMS Hardware User's Guide.)


Configuration Files

Startup Configuration File (.sapcfg)

File name: /var/stm/config/tools/monitor/dm_ups.sapcfg

Default Entries: The monitor uses the standard default monitor request entries. See the Generic Monitor Data Sheet.

Monitor Configuration File (.cfg)
File name: /var/stm/config/tools/monitor/dm_ups.cfg

Default settings:

 Setting Name  Before September 2000  September 2000 & after 
POLL_INTERVAL 60 minutes  60 minutes
REPEAT_FREQUENCY 1440 minutes (1 day)  Replaced by "Suppression Time" in the .clcfg file.
SEVERITY_ACTION Notify for all levels  See the .clcfg file for specific event info.

As a Multiple-view (Predictive-enabled) hardware monitor, the Repeat Frequency and Severity Action are no longer set in the Monitor Configuration file (.cfg) but are now set in the Default Client Configuration file (.clcfg) described below.

Default Client Configuration File (.clcfg)

File name: /var/stm/config/tools/monitor/default_dm_ups.clcfg

Monitors containing the client-configuration files (.clcfg) are Multiple-View enabled monitors. Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_dm_core_hw.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_dm_core_hw.clcfg) are used to control the text sent to specific targets (in this example, to Predictive Support).

HOST_ID tags in the .clcfg files control the System Information, which is reported under the "Additional System Data" label in the event messages. If a HOST_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message.

HOST_IDs available for all monitors are described in the Generic Monitor Data Sheet.

DEV_ID tags in the .clcfg files control the Monitor-specific information, which is reported under the "Component Data" label in the event messages. If a DEV_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message. DEV_IDs available for this monitor include:

DEV_ID tag Default Text label
dev_pdev Off Physical Device Path

PSM Configuration File (.psmcfg)

File name: /var/stm/config/tools/monitor/dm_ups.psmcfg

Default settings:

MONITOR_RESOURCE_NAME /system/events/ups
PSM_RESOURCE_NAME /system/status/ups
MONITOR_STATE_HANDLING Requires the use of set_fixed to set UP state.
DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN
DOWN_SEVERITY_OPERATOR default

Top of Page / Diagnostics HOME
URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_ups.htm
Last updated: Monday April 29 9:13:22 CDT 2002