HP StorageWorks Modular SAN array 1000 / 30 Monitor (msamon)

Monitor Description | Configuration Files

---

Monitor Description

The HP StorageWorks Modular SAN array 1000 / 30 Monitor (msamon) is designed to monitor the operation of storage devices on your system.

If msamon detects a problem with a disk array or Just A Bunch Of Disks (JBOD) (SCSI/SATA), it sends an event to the Event Monitoring Service (EMS). The EMS framework alerts you using one of the notification methods defined for the monitor. Events include a description of the problem, its causes, and the recommended solution.

The msamon monitor polls the device at regular intervals for the status of each disk array. Then, the monitor analyzes the data returned by the device to determine if a hardware problem has occurred. If an error that warrants notification has occurred, the monitor generates an event.

The monitor launches automatically along with the system. Therefore, it ensures that all supported disk arrays are protected from undetected hardware failure.

Release History

HP-UX 11i v2 March 2004 release: Initial release

HP-UX 11i June 2004 release: Support added for HP StorageWorks Modular Array 30

HP-UX 11i v2 May 2005 release: Support added for HP Storage Works Modular Array 1500 (Active-Passive)

HP-UX 11i September 2005 release: Support added for HP Storage Works Modular Array 1500 (Active-Active, Active-Passive)

Supported Products

• Starting with HP-UX 11i v2 March 2004 release of OnlineDiag, msamon monitors HP StorageWorks Modular Array 1000 supported on the following cards:
  • A6795A (2 Gbps, 64-bit 66 MHz PCI)
  • A6826A (2 Gbps, 64-bit PCI Dual Channel)
• Starting with HP-UX 11i June 2004 release and HP-UX 11i v2 September 2004 release of OnlineDiag, msamon also monitors HP StorageWorks Modular Array 1000 supported on the following cards:
  • A9782A (2 Gbps, 64-bit PCI Dual Channel combo)
  • A9784A (2 Gbps, 64-bit PCI Dual Channel combo)
• HP StorageWorks Modular SAN Array 30
• HP StorageWorks Modular SAN Array 1500 (Active-Active, Active-Passive)

Special Requirements

None

Resource Path

Event monitoring: /storage/events/disk_arrays/MSA1000
Status monitoring: /storage/status/disk_arrays/MSA1000

Monitor Name

/usr/sbin/stm/uut/bin/tools/monitor/msamon

Peripheral Status Monitor (PSM) State Control

If the state of the repaired hardware changes to "up", it is automatically detected and reported by UP_STATE_CONTROL to the PSM.

Configuration Files

Startup Configuration File (.sapcfg)

File name: /var/stm/config/tools/monitor/msamon.sapcfg

Default Entries: The monitor uses standard default monitor request entries.

Monitor Configuration File (.cfg)

File name: /var/stm/config/tools/monitor/msamon.cfg

Default settings:

Setting Name	Prior to June 2001	June Release and After
POLL_INTERVAL	15 minutes	15 minutes
REPEAT_FREQUENCY	1440 minutes (1 day)	Replaced by Suppression Time in the .clcfg file but is still 1440 minutes.
SEVERITY_ACTION	Notify events with any severity level	See the .clcfg file for information on specific events.

PSM Configuration File (.psmcfg)

File name: /var/stm/config/tools/monitor/msamon.psmcfg

Default settings:

Setting Name	Details
MONITOR_RESOURCE_NAME	/storage/events/disk_arrays/MSA1000
PSM_RESOURCE_NAME	/storage/status/disk_arrays/MSA1000
MONITOR_STATE_HANDLING	UP_STATE_CONTROL If the state of the repaired hardware changes to "up", it is automatically detected and reported to the PSM. The set_fixed utility need not be used to change the state to "up".
DOWN_SEVERITY_THRESHOLD	Critical maps to DOWN

Default Client Configuration File (.clcfg)

File name: /var/stm/config/tools/monitor/default_msamon.clcfg

Multiple-view (predictive-enabled) monitors contain client-configuration files (.clcfg). Starting with the HP-UX 11i March 2003 release, the msamon 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.clcfg 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.

The HOST_ID tags in the .clcfg files control the system information reported as "Additional System Data" in the event messages. If you enable the HOST_ID tag in the .clcfg file, the corresponding information appears in the event message.

You can enable the HOST_ID tag for all the monitors. For more information, see the Generic Monitor Data Sheet.

The 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 msamon:

DEV_ID tag	Default	Text Label
dev_pdev	Off	Physical Device Path