Monitor Description | Configuration Files
Monitor Description
The Core Hardware monitor is designed to monitor the hardware contained in the System Processing Unit (SPU). This includes the power supplies and fans, the system bus, and the circuits which connect the I/O system to the main processor. The intake temperature is also monitored. If a problem with this hardware is detected, the monitor sends an event to Event Monitoring Service, which alerts you using the notification methods defined for the monitor. Clear, concise error messages identify the problem, what caused it, and what must be done to correct it.
The System Processor Unit (SPU) is the 'box(s)' which contains the processors (CPUs) and associated hardware.
The Core Hardware monitor employs both polling and event-driven event detection. At regular intervals, the monitor requests status information from the system hardware. The monitor then analyzes the data returned to determine if a hardware problem has occurred. If an error has occurred that warrants notification, an event is generated immediately. In addition, some information is delivered to the monitor directly as a result of logging by operating system drivers.
The monitor is launched automatically when the system is started, ensuring that SPU hardware is protected from undetected hardware failure.
Release History
June 2000 Release (Support Plus Media) and HP-UX 11i: Multiple-view ("Predictive-enabled") support.
June 1999 Release: Initial releaseSupported Products
Intake temperature is monitored on all SPUs. Other resources are monitored if supported on a particular SPU. For example, only the N-Class and future systems support the monitoring of the power supplies and fans, the system bus, and the circuits which connect the I/O system to the main processor.
Special Requirements
This monitored is offered only on HP-UX 11.x.
Resource Path
Event monitoring: /system/events/dm_core_hw
Status monitoring: /system/status/dm_core_hwMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
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_core_hw.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/dm_core_hw.cfg
Default settings:
Setting Name Before June 2000 June 2000 & after POLL_INTERVAL 15 minutes 15 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. REQUIRE_REDUNDANCY 1 1 TEMPERATURE_RESET_PERIOD 15 minutes of normal temperature 15 minutes of normal temperature 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) CLCFG_VERSION:A.01.00
File name: /var/stm/config/tools/monitor/default_dm_core_hw.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.
The Core Hardware Monitor does not support DEV_IDs.
PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/dm_core_hw.psmcfg
Default settings:
MONITOR_RESOURCE_NAME
/system/events/core_hwPSM_RESOURCE_NAME /system/events/core_hw MONITOR_STATE_HANDLING Requires the use of set_fixed to set UP state. DOWN SEVERITY THRESHOLD Serious and Critical map to DOWN