Monitor Description | Configuration Files
Monitor Description
The HP StorageWorks MSA 60 and MSA 70 SAS Enclosure Monitor (msamon_sas) is designed to monitor the operations of the MSA 60 and MSA 70 storage enclosure on your system.
The msamon_sas monitor polls the device at regular intervals for the status of each enclosure. If an error that warrants notification occurs on a disk enclosure or Just A Bunch Of Disks (JBOD), the monitor sends the error details to the Event Monitoring Service (EMS) framework. Depending on the event monitoring requests, the EMS framework alerts the user about the event. Events include a description of the problem, its causes, and the recommended solution.
The monitor launches automatically when the system starts, ensuring that all supported disk enclosures are protected from undetected hardware failure.
Release History
The msamon_sas monitor is introduced in the HP-UX 11i v2 and HP-UX 11iv3 March 2008 release.
Supported Products
- Starting with HP-UX 11i v2 and HP-UX 11i v3 March 2008 release of OnlineDiag, msamon_sas monitors HP StorageWorks MSA 60 and MSA 70 that is supported on HP SC44Ge Host Bus Adapter (SAS HBA).
- Starting with the HP-UX 11i v2 and HP-UX 11i v3 March 2008 release, msamon_sas monitors HP StorageWorks MSA 60 and MSA 70.
Special Requirements
None
Resource Path
Following is the resource path for event monitoring:
/storage/events/enclosures/msamon_sasFollowing is the resource path for status monitoring:
/storage/status/enclosures/msamon_sasMonitor Name
The name of the monitor is:
/usr/sbin/stm/uut/bin/tools/monitor/msamon_sasPeripheral Status Monitor State Control
When the defective hardware is repaired, its state is changed to UP automatically by the Peripheral Status Monitor (PSM).
Configuration Files
The following sections describe the configuration files:
Startup Configuration File (.sapcfg)
The name of the Startup Configuration File (.sapcfg) is:
/var/stm/config/tools/monitor/msamon_sas.sapcfgThe monitor uses standard default monitor request entries.
Monitor Configuration File (.cfg)The name of the monitor configuration file (.cfg) is:
/var/stm/config/tools/monitor/msamon_sas.cfgThe following table describes the default settings of the monitor configuration file:
Event Qualification Entry Settings POLL_INTERVAL 15 minutes REPEAT_FREQUENCY 1440 minutes (1 day) SEVERITY_ACTION For information on specific events, see the .clcfg file. The name of the Client Configuration file is:
/var/stm/config/tools/monitor/default_msamon_sas.clcfgMultiple-View (Predictive-Enabled) monitors contain Client-Configuration files (.clcfg). Starting with the HP-UX 11i v2 and HP-UX 11i v3 March 2008 release, the msamon_sas monitor supports the Multiple-View (Predictive-Enabled) feature. You can modify the .clcfg files to control the text sent to different targets. The default_msamon_sas.clcfg file applies to messages sent to all targets. You can use the monitor-specific .clcfg files to control the text sent to specific targets. For example, in the predictive_dm_core_hw.clcfg file, you can control the text sent to Predictive Support.
You can enable the HOST_ID tag for all the monitors. For information on the HOST_ID tag, see the Generic Monitor Data Sheet at:
http://www.docs.hp.com/en/diag/ems/emd_generic.htmThe DEV_ID tags in the .clcfg files control monitor-specific information reported as Component Data in the event message. If you enable the DEV_ID tag in the .clcfg file, the corresponding information appears in the event message.
The following table provides information on DEV_ID for the msamon_sas monitor:
DEV_ID tag Default Text label dev_pdev On Physical Device Path PSM Configuration File (.psmcfg)
The name of the PSM Configuration File (.psmcfg) is:
/var/stm/config/tools/monitor/msamon_sas.psmcfgThe following table describes the default settings of the PSM Configuration File:
Setting Name Details MONITOR_RESOURCE_NAME /storage/events/enclosures/msamon_sas PSM_RESOURCE_NAME /storage/status/enclosures/msamon_sas MONITOR_STATE_HANDLING UP_STATE_CONTROL
When the defective hardware is repaired, its state is changed to UP automatically by the PSM. The set_fixed utility need not be used to change the state to UP.DOWN SEVERITY THRESHOLD CRITICAL maps to DOWN
Top of Page / Diagnostics HOME