Monitor Description | Configuration Files
Monitor Description
The SCSI123 monitor is designed to monitor errors on SCSI1, SCSI2 and SCSI3 interface cards. For each error, the monitor will generate an EMS event, which will inform you of the problem, the cause of the problem, and what you can do to correct it.
The monitor is launched automatically when the system is started.
Release HistoryMarch 2001 Release: Multiple-view ("Predictive-enabled") support
September 1999: Initial releaseSupported Products
SCSI1, SCSI2 and SCSI3 interface cards on all HP-UX systems.
Special Requirements
None
Resource Path
Event monitoring: /adapters/events/scsi123_em
Status monitoring: /adapters/events/scsi123_emMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/scsi123_em
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/scsi123_em.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/scsi123_em.cfg
The SCSI Card monitor began supporting Multiple-view (Predictive-enabled) in the March 2001 Release. Note 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 Before March 2001 March 2001 & After POLL_INTERVAL 60 minutes (one hour) 60 minutes (one hour) 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. Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_scsi123_em.clcfg
If a monitor is Multiple-view (Predictive-enabled), it uses a client-configuration file (*.clcfg) to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_scsi123_em.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_scsi123_em.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 On Physical Device Path (H/W path of the SCSI card being monitored) PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/scsi123_em.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /adapters/events/scsi123_em PSM_RESOURCE_NAME /adapters/state/scsi123_em MONITOR_STATE_HANDLING Requires the use of set_fixed to set UP state. DOWN SEVERITY THRESHOLD CRITICAL and SERIOUS will map to DOWN state.