Monitor Description | Configuration Files
Monitor Description
The High-Availability Disk Array monitor is designed to monitor the operation of all supported High-Availability Disk Arrays on your system. If a problem is detected with a disk array, the monitor immediately 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 High-Availability Disk Array monitor employs two types of event detection: asynchronous and polling. Using asynchronous detection, the monitor continuously watches for any errors or abnormal behavior reported by the device driver during I/O operations. If an error occurs, it is passed directly to the monitor for immediate analysis and event generation if necessary.
Using polling detection, the monitor requests status information from each disk array at regular intervals. 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.
The monitor is launched automatically when the system is started, ensuring that all supported High-Availability Disk Arrays are protected from undetected hardware failure.
Release History
December 2000 Release and HP-UX 11i: Multiple-view ("Predictive-enabled") support
February 1999 Release: Initial releaseSupported Products
Model 30/FC Fibre Channel Disk Array
Models 10 and 20 SCSI Disk ArraysSpecial Requirements
None
Resource Path
Event monitoring: /storage/events/disk_arrays/High_Availability
Status monitoring: /storage/status/disk_arrays/High_AvailabilityMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/ha_disk_array
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/ha_disk_array.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/ha_disk_array.cfg
The LPMC monitor began supporting Multiple-view (Predictive-enabled) in the June 2000 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 December 2000 December 2000 & after POLL_INTERVAL 15 minutes 15 minutes REPEAT_FREQUENCY 1440 minutes (1 day) Replaced by "Suppression Time" in the .clcfg file. DEBUG_FLAGS 31 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_ha_disk_array.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). Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_ha_disk_array.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_ha_disk_array.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 dev_inq_vendor On Inquiry Vendor ID dev_inq_prod On Inquiry Product ID dev_serial_num On Serial Number dev_fw_version On Firmware Revision dev_class On Device Class PSM Configuration File
File name: /var/stm/config/tools/monitor/ha_disk_array.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /storage/events/disk_arrays/High_Availability PSM_RESOURCE_NAME /peripherals/state/mass_storage/SCSI/High_Availability MONITOR_STATE_HANDLING NO_UP_CONTROL. UP state will be controlled by the set_fixed(1m) command. DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN