Monitor Description | Configuration Files
Monitor Description
The Disk Array FC60 monitor is designed to monitor the operation of the HP SureStore E Disk Array FC60. If a problem is detected with a disk array, 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 Disk Array FC60 monitor employs polling event detection. At regular intervals, the monitor requests status information from each disk array. 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 disk arrays are protected from undetected hardware failure.
Release HistoryDecember 2000 Release - HP-UX 11i: Multiple-view ("Predictive-enabled") support.
(Not Multiple-view in Dec 00 release for 10.20 and 11.00)
June 1999 Release: Initial releaseSupported Products
HP SureStore E Disk Array FC60
Special Requirements
Patches:
- 10.20 PHCO_26822
- 11.00 PHCO_26823
- 11.11 PHCO_26824
Resource Path
Event monitoring: /storage/events/disk_arrays/FC60
Status monitoring: /storage/status/disk_arrays/FC60Monitor Name
/usr/sbin/stm/uut/bin/tools/monitor/fc60mon
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)
Event History File
Events are kept in the event.log file and in the fc60mon.log file.
Configuration Files
Startup Configuration File (.sapcfg)
File name: /var/stm/config/tools/monitor/fc60mon.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/fc60mon.cfg
Default settings:
Setting Name Before March 2001 March 2001 & after POLL_INTERVAL 15 minutes 15 minutes REPEAT_FREQUENCY 1440 minutes (1 day) For 11i, replaced by the Suppression Time in .clcfg stop_mon_ivl Stop Monitor Interval 5 minutes Stop Monitor Interval 5 minutes 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.
PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/fc60mon.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /storage/events/disk_arrays/FC60 PSM_RESOURCE_NAME /storage/events/disk_arrays/FC60/state MONITOR_STATE_HANDLING NO_UP_CONTROL (default)
Requires the use of set_fixed to set UP state.DOWN SEVERITY THRESHOLD Serious and Critical map to DOWN Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_fc60mon.clcfg
Monitors containing the client-configuration files (.clcfg) are Multiple-View enabled monitors. From March 2001 Release version 11.i, FC60 Disk Array Monitor is Multiple-View enabled. Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_fc60mon.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