Monitor Description | Configuration Files
Monitor Description
The Chassis code monitor is designed to monitor all system chassis logs. It reads all the chassis logs from the file /var/stm/logs/os/ccbootlog. This log is created by the chassis code logging daemon (cclogd). Cclogd reads all logs from the Guardian Service Processor (GSP) and writes them to the ccbootlog file. An EMS event will be generated for each chassis log that has been defined to trigger an event.
The Chassis Code monitor polls the ccbootlog file periodcially for new chassis logs. By default, the polling interval is one (1) minute. This can be changed in the dm_chassis.cfg file.
Cclogd is launched by diagmond (if the OnlineDiag product is installed on the system) automatically when the system is started. It then begins reading chassis logs from the GSP and writing them to ccbootlog. All chassis logs with alert level of 0 or greater are logged to ccbootlog.
Release History
June 2001 Release (Support Plus Media) and HP-UX 11i: Multiple-view ("Predictive-enabled") support.
June 2001 Release: Initial release.Supported Products
The dm_chassis monitor runs on all PA Superdome class, rp74XX and rp84XX systems with processors prior to the PA8800.
Special Requirements
The chassis code logging daemon (cclogd) must be up and running to capture all system chassis logs.
Resource Path
Event monitoring: /system/events/chassis
Status monitoring: /system/status/chassisMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/dm_chassis
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_chassis.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/dm_chassis.cfg
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 settings:
Setting Name Details POLL_INTERVAL 1 minutes REPEAT_FREQUENCY Replaced by "Suppression Time" in the .clcfg file. SEVERITY_ACTION See the .clcfg file for specific event info. Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_dm_chassis.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_chassis.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_dm_chassis.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.