Monitor Description | Configuration Files
Monitor Description
The remote monitor is designed to monitor the operation of all supported devices via a remote connection to the device's management software.
If a problem is detected with a device, 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 remote monitor employs asynchronous event detection. The monitor continuously watches for any errors or abnormal behavior reported by the device management software via a TCP/IP port (port 2818). If a device problem is detected by the device management program, an event describing the problem is passed directly to the monitor for immediate analysis and event generation if necessary.
The monitor is launched automatically when the system is started, ensuring that all supported devices are protected from undetected hardware failure.
Release HistorySeptember 2000 Release and HP-UX 11i: Initial release. Includes Multiple-view ("Predictive-enabled") support.
Supported Products
All devices managed by HP device management software, currently:
- HP StorageWorks Virtual Array 7100
- HP StorageWorks Virtual Array 7400
- HP StorageWorks Virtual Array 7410
- HP StorageWorks Virtual Array 7110
Special Requirements
HP-UX 11.xx, September 2000 Release or later
TCP/IP port 2818 must be availableResource Path
Event monitoring: /StorageAreaNetwork/events/SAN_Monitor
Status monitoring: N/AMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/RemoteMonitor
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/RemoteMonitor.sapcfg
Default Entries: The monitor uses the standard default monitor request entries. See the Generic Monitor Data Sheet.
Monitor Configuration File (.cfg) File name: /var/stm/config/tools/monitor/RemoteMonitor.cfgDefault settings:
Setting Name Before September 2000 September 2000 & 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.
Device Default DISK_ARRAY DISABLE DISK_DRIVE DISABLE JBOD DISABLE TAPE_LIBRARY DISABLE TAPE_DRIVE DISABLE FC_HUB DISABLE FC_SWITCH DISABLE FC_BRIDGE DISABLE Note: Multiple-view (Predictive-enabled) hardware monitors no longer use the the Monitor Configuration file (.cfg) to set the Repeat Frequency and Severity Action. These settings are made instead in the the Client Configuration files (.clcfg) described below.
Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_RemoteMonitor.clcfg
Note: the client-configuration files (.clcfg) apply only to Multiple-view (Predictive-enabled) hardware monitors.
Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_RemoteMonitor.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_RemoteMonitor.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_devclass ON Device Class dev_fw_version ON Firmware Revision dev_inq_prod ON Inquiry Product ID dev_inq_vendor ON Inquiry Vendor ID dev_pdev ON Physical Device Path dev_seri al_num ON Serial Number PSM Configuration File (.psmcfg)
N/A