Monitor Description | Configuration Files
Monitor Description
The Fibre Channel Adapter monitor is designed to monitor the operation of all supported fibre channel adapter cards on your system. If a problem is detected with any of the adapters, 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 FC adapter monitor employs asynchronous event 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. If the error warrants notification, an event is generated immediately.
The monitor is launched automatically when the system is started, ensuring that all supported fibre channel adapters are protected from undetected hardware failure.
Release History
September 2000 Release (Support Plus Media) and HP-UX 11i: Multiple-view ("Predictive-enabled") support
February 1999 Release: Initial releaseSupported Products
Fibre Channel Adapter Models A3404A, A3591A, A3636A, A3740A
Special Requirements
The following driver revisions are required:
- B.10.20 TFC plus Dart40
- B.11.00 release IPR9808 (Rocklin version)
Resource Path
Event monitoring: /adapters/events/FC_adapter
Status monitoring: /adapters/status/FC_adapterMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/dm_FCMS_adapter
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/dm_FCMS_adapter.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/dm_FCMS_adapter.cfg
Default settings:
Polling Interval N/A - Employs Asynchronous Event Detection Repeat Frequency N/A Severity Action Notify for all levels 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.
Default Client Configuration File (.clcfg) CLCFG_VERSION:A.01.00
File name: /var/stm/config/tools/monitor/default_dm_FCMS_adapter.clcfg
Monitors containing the client-configuration files (.clcfg) are Multiple-View enabled 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_dm_fcms_adapter.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_dm_fcms_adapter.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 PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/dm_FCMS_adapter.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /adapters/events/FC_adapter PSM_RESOURCE_NAME /adapters/state/events/FC_adapter MONITOR_STATE_HANDLING NO_UP_CONTROL. Requires the use of set_fixed to set UP state. DOWN_SEVERITY_THRESHOLD SERIOUS and CRITICAL will map to DOWN state