EMS Hardware Monitors User's Guide Manufacturing Part Number: B6191-90029 May 2005 © Copyright 1979-2005 Hewlett-Packard Development Company, L.P.
Legal Notices The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Printed in the US. Confidential computer software. Valid license from HP required for possession, use or copying.
Printing History The printing date and part number indicate the current edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.) The part number changes when extensive technical changes are incorporated. New editions of this manual will incorporate all material updated since the previous edition.
Contents 1. Introduction Hardware Monitoring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is Hardware Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Does Hardware Monitoring Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benefits of Hardware Monitoring . . . . . . . . . . . . . . . . . . . . . . .
Contents Event Polling (in Detail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 4. Using the Peripheral Status Monitor Peripheral Status Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Does the PSM Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSM Components . . . . . . . .
Contents File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations for Modifying the PSM Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8
Tables Table 1-1. Hardware Monitoring Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 2-1. Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 2-2. Disk Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Table 2-3. Tape Products (monitored by SCSI Tape Devices Monitor) . . . . . .
Tables 10
Figures Figure 1-1. Components Involved in Hardware Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-1. The Steps for Installing and Configuring Hardware Monitoring. . . . . . . . . . . . . . . . . . Figure 2-2. Building a Monitoring Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-1. Hardware Monitoring Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-2.
Figures 12
About This Manual This guide is intended for use by system administrators and others involved in managing HP-UX system hardware resources. It describes the installation and use of (EMS) Hardware Monitors—an important tool in managing the operation and health of system hardware resources. The book is organized as follows: • Chapter 1, “Introduction,” provides a foundation for understanding what the hardware monitors are and how they work.
• Managing MC/ServiceGuard (B3936-90024) - provides information on creating package dependencies for hardware resources • Using EMS HA Monitors (B5735-90001) - provides detailed information on using EMS to create monitoring requests. Note: This manual pertains to High Availability (HA) Monitors rather than to the EMS Hardware Monitors. Related Web sites The following Web sites provide information on hardware monitoring. • http://docs.hp.com/en/diag.
Introduction 1 Introduction This chapter introduces the EMS Hardware Monitors.
Introduction Hardware Monitoring Overview Hardware Monitoring Overview What is Hardware Monitoring? Hardware monitoring is the process of watching a hardware resource (such as a disk) for the occurrence of any unusual activity, called an event. When an event occurs, it is reported using a variety of notification methods (such as email). Event detection and notification are all handled automatically with minimal involvement on your part.
Introduction Hardware Monitoring Overview How Does Hardware Monitoring Work? The following figure shows the basic components involved in hardware monitoring. Figure 1-1 Components Involved in Hardware Monitoring The typical hardware monitoring process works as follows: 1. While monitoring its hardware resources, the hardware event monitor detects some type of abnormal behavior on one of the resources. 2.
Introduction Hardware Monitoring Overview Benefits of Hardware Monitoring Hardware monitoring provides the following benefits: • Reduces system downtime by detecting hardware failures when they occur, allowing you to quickly identify and correct problems. • Integrates with MC/ServiceGuard and other applications responsible for maintaining system availability. These applications can now add many hardware resources to the components they monitor.
Introduction Hardware Monitoring Overview Products Supported by Hardware Monitors EMS Hardware Monitors are provided for a wide range of system hardware resources. The following list identifies the types of hardware supported by monitors at the time of publication. A detailed list of the specific hardware products supported by each hardware monitor is included in http://docs.hp.
Introduction Hardware Monitoring Overview Tips for Hardware Monitoring Here are some tips for using hardware monitoring. ✓ Keep hardware monitoring enabled to protect your system from undetected failures. Hardware monitoring is an important tool for maintaining high-availability on your system. In a high-availability environment, the failure of a hardware resource makes the system vulnerable to another failure.
Introduction Hardware Monitoring Overview Hardware Monitoring Terms The following terms are used throughout this guide. Understanding them is important when learning how the hardware event monitors work and how to use them effectively. Table 1-1 Hardware Monitoring Terms Term Definition Asynchronous event detection The ability to detect an event at the time it occurs. When an event occurs the monitor is immediately aware of it. This method provides quicker notification response than polling.
Introduction Hardware Monitoring Overview Table 1-1 Term Hardware event monitor Hardware Monitoring Terms (Continued) Definition A monitor daemon that gathers information on the operational status of hardware resources. Each monitor is responsible for watching a specific group or type of hardware resources. For example, the tape monitor handles all tape devices on the system. The monitor may use polling or asynchronous event detection for tracking events.
Introduction Hardware Monitoring Overview Table 1-1 Term Hardware Monitoring Terms (Continued) Definition Peripheral Status Monitor (PSM) Included with the hardware event monitors, the PSM is a monitor daemon that acts as a hardware status monitor by converting events to changes in hardware resource status. This provides compatibility with MC/ServiceGuard, which uses changes in status to manage cluster resources. Through the EMS GUI, the PSM is also used to create hardware status monitoring requests.
Introduction Hardware Monitoring Overview 24 Chapter 1
Installing and Using Monitors 2 Installing and Using Monitors This chapter instructs you how to use the EMS Hardware Monitors to manage your hardware resources.
Installing and Using Monitors The Steps Involved The Steps Involved The steps involved in installing and configuring hardware monitoring are shown in Figure 2-1 on page 27. Each step is described in detail in this chapter on the page indicated. Installation of Support Tools is necessary if you have Diagnostic/IPR Media release earlier than the June 1999 release only. With HP-UX 11i, the Support Tools are automatically installed when the OS is installed.
Installing and Using Monitors The Steps Involved Figure 2-1 Chapter 2 The Steps for Installing and Configuring Hardware Monitoring 27
Installing and Using Monitors Installing EMS Hardware Monitors Installing EMS Hardware Monitors The EMS Hardware Monitors software is distributed with the Support Tools (diagnostics). All the necessary files for hardware monitoring are installed automatically when the Support Tools are installed. There are several different ways that the Support Tools are installed: • The Support Plus Media: installing the OnlineDiag depot from the Support Plus Media using swinstall.
Installing and Using Monitors Installing EMS Hardware Monitors • HP 9000 Series 700 or 800 Computer • HP-UX 10.20 or 11.x (Hardware event monitoring is not currently available on the special high security systems, HP-UX 10.26 (TOS) and HP-UX 11.04 (VVOS). • Support Plus Media, the more current the better. The hardware event monitors were first distributed in the HP-UX 10.20/11.00 February 1999 release (IPR 9902).
Installing and Using Monitors Checking for Special Requirements Checking for Special Requirements Some devices have special requirements in order to be monitored. Examine the tables of supported products below to see if any of your devices have special requirements. Table 2-1 Disk Arrays Product HP AutoRAID Disk Array Model/Product Number 12H 12 Supported by: AutoRAID Disk Array Monitor Special Requirements Requires the following ARMServer versions: HP-UX 10.XX (PHCO_23261); HP-UX 11.
Installing and Using Monitors Checking for Special Requirements Table 2-2 Disk Products Product All disks bound to the sdisk and disc30 drivers and not under the control of another event monitor (such as a disk array monitor). Model/Product Number NA Special Requirements None Hitachi XP128, XP256, XP512 and XP1024 drives and EMC Symetrix drives are not supported, since these drives have their own monitoring.
Installing and Using Monitors Checking for Special Requirements Table 2-3 Tape Products (monitored by SCSI Tape Devices Monitor) (Continued) Product Model/Product Number Special Requirements DLT 4000 and 7000; 15 slot; Deskside/Rack; Differential A4851A None DLT 4000 and 7000; 588 slot; Drives Diff; Robotics SE A4845A None DLT 4000 and 7000; 100 slot; Drives Diff; Robotics SE A4846A None DLT 4000 and 7000; 30 slot; Differential A4853A None DLT7000 8-slot Library A5501A March 00 Release D
Installing and Using Monitors Checking for Special Requirements DLT 4000 & 7000; 100 slot; Drives Diff; Robotics SE DLT 4000 & 7000; 30 slot; Differential As of the March 2000 release (IPR0003), the monitor also supports the following devices: DDS-4 Autoloader DLT7000 HP Surestore Tape Autoloader Model 1/9 DLT8000 HP Surestore Tape Autoloader Model 1/9 DLT 8000 HP Surestore Tape Library Model 2/20 DLT8000 HP Surestore Tape Library Model 4/40 DLT8000 HP Surestore Tape Library Model 6/60 DLT8000 HP Surestore
Installing and Using Monitors Checking for Special Requirements Table 2-5 Fibre Channel SCSI Multiplexers Product HP Fibre Channel SCSI Multiplexer Model/Product Number A3308A Special Requirements Firmware version 3840 Supported by: Fibre Channel SCSI Multiplexer Monitor Table 2-6 Fibre Channel Adapters Product HP Fibre Mass Storage Channel Adapters Supported by: Fibre Channel Mass Storage Channel Adapter Fibre Channel Mass Storage Channel Adapter Supported by: A5158A Fibre Channel Mass Storage Ch
Installing and Using Monitors Checking for Special Requirements Table 2-7 Product HP Fibre Channel Arbitrated Loop Hubs Fibre Channel Arbitrated Loop (FC-AL) Hub Model/Product Number A3724A A4839A Supported by: Fibre Channel Arbitrated Loop Hub Monitor Special Requirements The FC-AL Hub monitor requires: Device Firmware revisions: • Device Agent Firmware revision 2.14 or greater • Hub Controller Firmware revision 3.06 or greater Firmware and installation instructions are available at http://www.
Installing and Using Monitors Checking for Special Requirements Table 2-9 Memory Product All system memory on PA-RISC systems. Model/Product Number Special Requirements NA None NA HP-UX 11.22 OS or later Supported by: PA Memory Monitor Itanium Memory Monitor: monitor for all system memory on Itanium systems. Supported by: Itanium Memory Monitor Table 2-10 System Product A monitor designed to monitor all system chassis logs. Model/Product Number Superdome S-Class For HP-UX 11.11 OS only.
Installing and Using Monitors Checking for Special Requirements Table 2-10 System (Continued) Product Low Priority Machine Checks (LPMCs) Model/Product Number Special Requirements NA HP-UX 11.x NA All HP-UX IPF systems running HP-UX 11.23 or later. Supported by: LPMC Monitor IPMI Forward Progress Log Monitor monitors IPMI FPL log entries on the system. Supported by: IPMI Forward Progress Log Monitor All HP-UX PA systems running HP-UX 11.23 or later. The ia64_corehw monitor must be running.
Installing and Using Monitors Checking for Special Requirements Table 2-12 Others Product iSCSI Subsystem Model/Product Number NA HP-UX software solution for iSCSI protocol. Supported by: Remote Monitor HP-UX 11.23, Patch PHSS_30457 for IA 11.23 (11.23) Codename: iHOP Supported by: iSCSI Subsystem Monitor All devices managed by HP device management software.
Installing and Using Monitors Using Hardware Monitoring Requests Using Hardware Monitoring Requests Monitoring requests are used to implement your strategy for monitoring hardware resources. The Hardware Monitoring Request Manager is the tool you use to create and manage hardware event monitoring requests. The following procedures describe how to use the Hardware Monitoring Request Manager to perform the tasks involved in managing monitoring requests for all hardware event monitors.
Installing and Using Monitors Using Hardware Monitoring Requests Figure 2-2 40 Building a Monitoring Request Chapter 2
Installing and Using Monitors Running the Monitoring Request Manager Running the Monitoring Request Manager NOTE You must be logged on as root to run the Monitoring Request Manager. To run the Monitoring Request Manager, type: /etc/opt/resmon/lbin/monconfig The opening screen indicates if monitoring is currently enabled or disabled. Since the June 1999 release, monitoring is enabled by default.
Installing and Using Monitors Enabling Hardware Event Monitoring Enabling Hardware Event Monitoring Hardware event monitoring must be enabled to protect your system from undetected hardware failures. All hardware monitoring requests are ignored while monitoring is disabled. Once monitoring has been enabled, all hardware event monitors and their associated monitoring requests will become operational.
Installing and Using Monitors Enabling Hardware Event Monitoring Default Monitoring Requests A set of default monitoring requests are created for each hardware event monitor. These default requests provide a complete level of monitoring and protection for the hardware resources under the control of the monitor. The default monitoring requests listed in Table 2-13 on page 43 are used for all hardware event monitors.
Installing and Using Monitors Listing Monitor Descriptions Listing Monitor Descriptions One of the first steps in managing monitoring requests is selecting the proper monitor for the hardware resource. You must know what hardware resources each monitor is responsible for to ensure that you select the proper monitor. Listing the descriptions of the available monitors will show you what hardware resources each monitor supports. To list the descriptions of available monitors: 1.
Installing and Using Monitors Viewing Current Monitoring Requests Viewing Current Monitoring Requests Before adding or modifying monitoring requests, you should examine the current monitoring requests. These include the default monitoring requests created during system startup. By examining the current requests, you can determine what additional requests may be needed to implement your monitoring and notification strategy.
Installing and Using Monitors Adding a Monitoring Request Adding a Monitoring Request Adding a monitoring request is a convenient way to add another notification method for a monitor. Each new notification method requires its own monitoring request. Monitoring requests can only be added at the monitor level, which creates an identical request for all instances of the hardware resources supported by the monitor. Monitoring requests cannot be added for a specific hardware instance.
Installing and Using Monitors Adding a Monitoring Request added to the monitoring configuration. When you restart the system or execute the IOSCAN utility (thus performing a real/hard IOSCAN), the new hardware will be included in event monitoring. If you add a new class of supported hardware resource to your system, any monitoring requests that apply to All monitors are used for the new hardware, ensuring that your hardware is protected immediately from undetected failure.
Installing and Using Monitors Adding a Monitoring Request Table 2-14 Monitoring Requests Configuration Settings (Continued) Setting Notification Method Description The following notification methods are available.
Installing and Using Monitors Adding a Monitoring Request Table 2-15 Event Severity Level Event Severity Levels (Continued) Description MC/ServiceGuard Response Minor Warning An event that will not likely escalate to a more severe condition if let uncorrected. System operation will not be interrupted and normal use of the hardware can continue. The problem can be repaired at a convenient time. If MC/ServiceGuard is installed and this is a critical component, a package fail-over WILL NOT occur.
Installing and Using Monitors Adding a Monitoring Request Example of Adding a Monitoring Request The following example illustrates the process of adding a monitoring request. In this example a request is added that will send all CRITICAL events detected by the AutoRAID disk array monitor to an email address of admin@hp.com.
Installing and Using Monitors Adding a Monitoring Request Enter Email Address: [root] admin@hp.com User Comment: (C)lear (A)dd Enter selection {or (Q)uit,(H)elp} [c] a Enter comment: [] This is a test message. Client Configuration File: (C)lear (A)dd Use Clear to use the default file. Enter selection {or (Q)uit,(H)elp} [c] c New entry: Send events generated by all monitors /storage/events/disk_arrays/AutoRAID with severity = CRITICAL to EMAIL admin@hp.
Installing and Using Monitors Modifying Monitoring Requests Modifying Monitoring Requests Modifying an existing monitoring request is a convenient way to alter one of the settings used in the request. Simply select a monitoring request and then change the desired setting. All other aspects of the request remain unchanged. To modify a monitoring request: 1. Run the Hardware Monitoring Request Manager by typing: /etc/opt/resmon/lbin/monconfig 2.
Installing and Using Monitors Verifying Hardware Event Monitoring Verifying Hardware Event Monitoring Once you have created the monitoring requests you need for your system, you may want to verify that they are working as you expect. The most effective way of verifying hardware event monitoring is to simulate a hardware failure or event. Depending on the hardware, you can do this by removing a disk from an array, unplugging a cable, turning off the hardware resource, using known defective media, etc.
Installing and Using Monitors Checking Detailed Monitoring Status Checking Detailed Monitoring Status This option lets you view the detailed information for all active monitoring requests. This information is organized by resource instance, and lists all the monitoring requests currently applied to each instance.
Installing and Using Monitors Retrieving and Interpreting Event Messages Retrieving and Interpreting Event Messages Event messages generated by hardware monitoring can be delivered using a variety of notification methods. To simplify receiving event messages you may want to use the email and/or textfile notification methods. Both of these methods, which are included in the default monitoring, receive the entire content of the message so you can read it immediately.
Installing and Using Monitors Deleting Monitoring Requests Deleting Monitoring Requests You may want to delete any monitor requests for a hardware resource that has been removed from your system. Only requests created exclusively for the missing resource should be deleted. CAUTION Use careful consideration before deleting monitoring requests or you may make your system vulnerable to undetected hardware failures.
Installing and Using Monitors Disabling Hardware Event Monitoring Disabling Hardware Event Monitoring You can disable hardware event monitoring if desired. However, all EMS Hardware Monitors will be disabled. You cannot disable a specific monitor. While monitoring is disabled, all monitoring requests are disabled. The monitoring requests are retained and become operational when monitoring is re-enabled. CAUTION Use careful consideration before disabling hardware event monitoring.
Installing and Using Monitors Disabling Hardware Event Monitoring 58 Chapter 2
Detailed Description 3 Detailed Description This chapter describes EMS Hardware Monitors in detail. The topics discussed in this chapter include: • Hardware monitoring architecture. • Hardware monitoring request manager. • EMS hardware event monitor. • Polling or asynchronous? • Startup client. • Peripheral status monitor. • Event monitoring service (EMS). • File locations. • Startup process (in detail). • Asynchronous event detection (in detail). • Event polling (in detail).
Detailed Description The Detailed Picture of Hardware Monitoring The Detailed Picture of Hardware Monitoring The following figure shows the major components involved in hardware monitoring and the communication paths between them.
Detailed Description The Detailed Picture of Hardware Monitoring Components from Three Different Applications Hardware event monitoring involves components from three different applications: • Event Monitoring System (EMS) provides the framework for event notification. EMS was originally developed to support system monitoring, but the existing framework is used to manage hardware event monitoring as well.
Detailed Description The Detailed Picture of Hardware Monitoring EMS Hardware Event Monitor The EMS hardware event monitor is the key component in the event monitoring architecture. An event monitor is a daemon process, running in the background continuously. The event monitor watches all instances of the hardware resources it supports, waiting for the occurrence of any failures or other unusual events. The monitor may use polling, asynchronous event detection, or both.
Detailed Description The Detailed Picture of Hardware Monitoring Each monitor has its own startup configuration file, which contains the default monitoring requests and any customized requests created using the Hardware Monitoring Request Manager.
Detailed Description The Detailed Picture of Hardware Monitoring File Locations The following table lists the locations of the files involved in hardware monitoring. Table 3-1 File Locations Directories and Files Description /usr/sbin/stm/uut/bin/tools/monitor/monitor_name Monitor executable files. /var/stm/config/tools/monitor/Global.cfg Default monitor configuration file. /var/stm/config/tools/monitor/monitor_name.cfg Monitor-specific configuration files.
Detailed Description The Detailed Picture of Hardware Monitoring Startup Process (in Detail) The following steps describe the process used to start the hardware monitoring. The startup process is illustrated in Figure 3-2 on page 65. The startup process is managed by the startup client (startcfg_client).
Detailed Description The Detailed Picture of Hardware Monitoring Disabling Monitoring Hardware monitoring can be disabled using the Hardware Monitoring Request Manager. Disabling monitoring disables all EMS Hardware Monitors. Individual monitors cannot be disabled using the Hardware Monitoring Request Manager. When monitoring is disabled all existing monitoring requests are unregistered, and then a kill -2 command is issued to stop all monitors.
Detailed Description The Detailed Picture of Hardware Monitoring Asynchronous Event Detection (in Detail) The following steps describe the process involved in asynchronous event detection. The asynchronous detection is illustrated in Figure 3-3 on page 68. 1. A device driver detects an error during an I/O with the device. 2.
Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-3 68 Asynchronous Event Detection Process Chapter 3
Detailed Description The Detailed Picture of Hardware Monitoring Event Polling (in Detail) The following is the process used for gathering event information using polling. The polling process is illustrated in Figure 3-4 on page 70. 1. At the interval defined by the polling value in the monitor configuration file, the monitor communicates with all the devices it is currently monitoring. The monitor sends pass-thru commands to all SCSI devices, and uses the appropriate protocol for other types of devices.
Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-4 70 Monitoring Polling Process Chapter 3
Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-5 Chapter 3 Memory Monitor Polling Process 71
Detailed Description The Detailed Picture of Hardware Monitoring 72 Chapter 3
Using the Peripheral Status Monitor 4 Using the Peripheral Status Monitor This chapter describes the Peripheral Status Monitor, which converts hardware events to status information for use by MC/ServiceGuard.
Using the Peripheral Status Monitor Peripheral Status Monitor Overview Peripheral Status Monitor Overview The primary function of the Peripheral Status Monitor, or PSM, is to convert hardware events into changes in device status. These changes in status can then be used by MC/ServiceGuard to control package failover. The information in Chapter 2, “Installing and Using Monitors,” described how to configure your system to detect hardware events using the Monitoring Request Manager.
Using the Peripheral Status Monitor How Does the PSM Work? How Does the PSM Work? The PSM converts hardware events detected by the EMS Hardware Monitors to “UP” or “DOWN” status, which is used by MC/ServiceGuard in controlling package failover. Figure 4-1 on page 76 illustrates how the PSM works with the other components of hardware monitoring.
Using the Peripheral Status Monitor How Does the PSM Work? Figure 4-1 76 Peripheral Status Monitor Chapter 4
Using the Peripheral Status Monitor How Does the PSM Work? PSM Components The PSM comprises the following components, which are installed along with the hardware event monitors. Each component has its own man page containing detailed information about its operation. • psmctd - the Peripheral Status Client/Target daemon used to monitor the state of hardware resources. • psmmon - the utility used to monitor the state of resources recognized by the psmctd daemon.
Using the Peripheral Status Monitor How Does the PSM Work? The status resource class path for each monitor is included in the monitor descriptions are available on the Web at http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_summ.htm. An HP-UX man page is available for each monitor.
Using the Peripheral Status Monitor Configuring MC/ServiceGuard Package Dependencies with the PSM Configuring MC/ServiceGuard Package Dependencies with the PSM The PSM allows you to create MC/ServiceGuard package dependencies for resources monitored by EMS Hardware Monitors. To use the PSM with MC/ServiceGuard, you configure one or more of the resource instances available in the PSM as MC/ServiceGuard package dependencies.
Using the Peripheral Status Monitor Configuring MC/ServiceGuard Package Dependencies with the PSM Configuring Package Dependencies using SAM The procedure assumes you have taken the necessary steps to create the package to which you will be adding resource dependencies. Complete instructions for configuring MC/ServiceGuard clusters and packages are provided in Managing MC/ServiceGuard. To create a package resource dependency: 1. From the command line, start the graphical version of SAM by typing: sam 2.
Using the Peripheral Status Monitor Configuring MC/ServiceGuard Package Dependencies with the PSM Configuring Package Dependencies by Editing the Configuration File You can also add PSM package dependencies by editing the package configuration file in /etc/cmcluster/pkg.ascii. See the Managing MC/ServiceGuard for details on modifying this file. When using the MC/ServiceGuard commands (e.g.
Using the Peripheral Status Monitor Creating EMS Monitoring Requests for PSM Creating EMS Monitoring Requests for PSM In addition to creating MC/ServiceGuard package dependencies, you can also use the PSM to create EMS monitoring requests. Because it is a state monitor rather than an event monitor, the process and options available for creating PSM requests with EMS are identical to those for the other system monitors available for EMS. To create a PSM monitoring request: 1.
Using the Peripheral Status Monitor Monitoring Request Parameters Monitoring Request Parameters The following information describes in detail the monitoring request parameters and offers tips on how to use them. Specifying When to Send Event - One of the first steps in creating a monitoring request involves specifying the conditions under which you want to be alerted. The following options are available for selecting when to send an alert.
Using the Peripheral Status Monitor Monitoring Request Parameters Setting the Polling Interval - The polling interval specifies how often EMS will check the PSM for changes in hardware status. The polling interval is the maximum amount of elapsed time before EMS will be aware of a change in status for the hardware resource being monitored. A short polling interval will ensure that you have recent data. However, a short polling interval may use more CPU and system resources.
Using the Peripheral Status Monitor Monitoring Request Parameters SNMP traps This option sends messages to applications using SNMP traps, such as Network Node Manager. See HP OpenView Using Network Node Manager (P/N J1169-90002) for more information on configuring SNMP traps. The following traps are used by EMS: EMS_ENTERPRISE_OID EMS_NORMAL_OID EMS_ABNORMAL_OID EMS_REBOOT_OID EMS_RESTART_OID EMS_NORMAL_SEV_OID EMS_WARNING_SEV_OID EMS_MINOR_SEV_OID EMS_MAJOR_SEV_OID EMS_CRITICAL_SEV_OID "1.3.6.1.4.1.11.2.
Using the Peripheral Status Monitor Monitoring Request Parameters To set for email notification: 1. Select the Email option from the list. 2. Specify the full email address in the Email Address field. syslog This option sends event notification to the system log. For an abnormal event, a system logging level of error will be associated with the logged message. An abnormal event message (error) is returned under the following conditions: • The When value is . . .
Using the Peripheral Status Monitor Copying Monitoring Requests Copying Monitoring Requests There are two ways to use the copy function: • To create requests for multiple resources using the same monitoring parameters. This is a quick way to set requests for multiple resources. • To create requests for the same resource using different monitoring parameters. This is a quick way to create requests that send events using multiple notification methods.
Using the Peripheral Status Monitor Modifying Monitoring Requests Modifying Monitoring Requests To change the monitoring parameters of a request: 1. From the Event Monitoring Service main screen, select the monitoring request whose parameters you wish to modify. 2. From the Actions menu select Modify Monitoring Request. The Monitoring Request Parameters screen is displayed. 3. In the Monitoring Request Parameters screen, modify the parameters as desired. 4. Click OK.
Using the Peripheral Status Monitor Removing Monitoring Requests Removing Monitoring Requests The Remove Monitoring Requests functions with multiple requests as well as single requests. To remove monitoring requests: 1. From the Event Monitoring Service main screen, select the monitoring request you wish to remove. To select contiguous multiple requests, hold the Shift key and click. To select individual multiple requests, hold the Ctrl key and click. 2.
Using the Peripheral Status Monitor Viewing Monitoring Requests Viewing Monitoring Requests To view the parameters for a monitoring request: 1. From the Event Monitoring Service main screen, select the monitoring request you wish to view and either: • Double-click, or • From the Actions menu select View Monitoring Request The View Monitoring Request Parameters screen is displayed. The parameters listed here match the parameters specified for the monitoring request. 2.
Using the Peripheral Status Monitor Using the set_fixed Utility to Restore Hardware UP State Using the set_fixed Utility to Restore Hardware UP State Most hardware event monitors cannot detect when a hardware failure has been repaired and the resource has been returned to normal operation. Consequently, these monitors cannot alert the PSM to change the status of its hardware resources from DOWN to UP.
Using the Peripheral Status Monitor Using the set_fixed Utility to Restore Hardware UP State 92 Chapter 4
Hardware Monitor Configuration Files 5 Hardware Monitor Configuration Files Several configuration files are used to control the operation of each hardware event monitor. The operation of the monitor can be altered by editing the contents of the various configuration files. Before altering the contents of a configuration file, you should have a thorough understanding of what effects the changes will have on monitor operation.
Hardware Monitor Configuration Files Overview Overview Understanding Multiple-View and Non-Multiple-View Monitor Classes EMS Hardware Monitors are divided into two classes: Multiple-View and Non-Multiple-View. Multiple-View monitors allow you to specify different event messages (for the same monitor) to one or more targets (“clients”). Targets may have different requirements for events, so event messages can be configured to be unique for each target.
Hardware Monitor Configuration Files Client Configuration File Client Configuration File As of the June 2000 release, several of the hardware monitors have been converted to be multiple-view. These monitors use an additional file for configuration, the Client Configuration File (for example, default_disk_em.clcfg.) The immediate purpose of this change is to enable HP Support Applications to work with hardware monitors. There will also be long-term benefits, as well.
Hardware Monitor Configuration Files Client Configuration File OR /etc/opt/resmon/lbin/send_test_event The program was created for HP Support Applications to ensure that the communication mechanism from the monitor to HP Support is working. However, it can be used by customers to ensure the same thing: that the communication mechanisms from the monitor to their notification method (email, event log, SNMP trap, etc.) are working.
Hardware Monitor Configuration Files Client Configuration File # EQ : event_number : severity : enable flag : suppression time : time window : # threshold : value threshold 1 : operator 1 : operator 2 : value threshold 2 # event_number : the number of the event # string of "OTHER" means use this entry when no other EQ entry matches # event number # # severity : the severity of the event.
Hardware Monitor Configuration Files Client Configuration File # msa1000 events EQ:110:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:111:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:120:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:121:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:130:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:131:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:140:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_
Hardware Monitor Configuration Files Client Configuration File EQ:510:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:520:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:600:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:900:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:901:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:902:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:903:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE # EQ:904:
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files Monitor-Specific and Global Configuration Files The common operating parameters defined by the monitor-specific and global configuration files for all non-multiple-view monitors include: • Polling Interval - identifies the frequency at which the monitor polls the hardware for status. This value is selected to provide current device status without seriously impacting system performance.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files Table 5-1 lists the common fields used to define monitor configuration settings. In addition to the common parameters, some monitors include other parameters in their configuration file. Any additional configuration parameters used by each monitor are listed in the monitor descriptions in the data sheets for the hardware event monitors available on the Web at http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_summ.htm.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files Table 5-1 Monitor Configuration File Entries (Continued) Setting REPEAT_FREQUENCY Values Description frequency must be a positive integer indicating the number of minutes to wait before a repeat event can be generated Defines how often repeat alerts should be generated for the same event. Events for a specific device should not be reported more often than the specified frequency.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files However, if you do want to suppress the reporting of less important events, you can change the severity action to IGNORE. This will affect all events in that category, and all instances of the monitor's hardware resources. Polling Interval If you need more frequent polling to isolate a potential problem with the hardware, the polling interval can be reduced.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # C = COMMUNICATION DEVICE # # DTLPWRSOMC = SCSI Device Class # #--> [ 28 00 06 -- ] DTLPWRSOMC Not-ready to ready transition. Medium changed.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # [ 30 01 06 -- ] DEFINE_EVENT 100308 INFORMATION # [ 3a 00 06 -- ] DEFAULT # msg num 8 #--------------------------------------------------------DEFINE_EVENT # [ 30 00 DEFINE_EVENT # [ 30 02 100109 INFORMATION DEFAULT # msg num 9 06 -- ] 100209 INFORMATION DEFAULT # msg num 9 06 -- ] DT--WR-O-- Cannot read medium - incompatible format.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files #--------------------------------------------------------DEFINE_EVENT 100020 INFORMATION DEFAULT # msg num 20 # [ 3f 03 06 -- ] DTLPWRSOMC Inquiry data has changed. #--------------------------------------------------------DEFINE_EVENT 100021 INFORMATION DEFAULT # msg num 21 # [ 2a 00 06 -- ] DTL-WRSOMC Parameters changed.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files DEFINE_EVENT # [ 18 05 DEFINE_EVENT # [ 18 06 DEFINE_EVENT # [ 1e 00 DEFINE_EVENT # [ -- -- 101726 MINOR_WARNING DEFAULT 01 -- ] 101826 MINOR_WARNING DEFAULT 01 -- ] 101926 MINOR_WARNING DEFAULT 01 -- ] D---W--O-- Recovered 102026 MINOR_WARNING DEFAULT 01 -- ] # msg num 40 # msg num 41 # msg num 42 id with ecc correction.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files #--------------------------------------------------------DEFINE_EVENT # [ 12 00 DEFINE_EVENT # [ 13 00 100136 CRITICAL DEFAULT # msg num 57 03 -- ] D---W--O-- Address mark not found for id field. 100236 CRITICAL DEFAULT # msg num 58 03 -- ] D---W--O-- Address mark not found for data field.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # [ 32 00 DEFINE_EVENT # [ 32 01 DEFINE_EVENT # [ 32 02 -- -- ] 100242 CRITICAL DEFAULT # msg num 76 03 -- ] D---W--O-- Defect list update failure. 100342 CRITICAL DEFAULT # msg num 76 03 -- ] #--------------------------------------------------------DEFINE_EVENT # [ 06 00 DEFINE_EVENT # [ 14 00 DEFINE_EVENT # [ 14 01 100143 CRITICAL DEFAULT # msg num 78 03 -- ] D---WR-OM- No reference position (like track 0)found.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # [ 4b 00 06 -- ] DTLPWRSOMC Data phase error. #--------------------------------------------------------DEFINE_EVENT 100053 CRITICAL DEFAULT # msg num 92 # [ 10 00 04 -- ] D---W--O-- Id crc or ecc error. #--------------------------------------------------------DEFINE_EVENT 100054 CRITICAL DEFAULT # msg num 93 # [ 2b 00 06 -- ] DTLPWRSO-C Copy cannot execute; host cannot disconnect.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files DEFINE_EVENT 100065 CRITICAL DEFAULT # msg num 104 # [ 09 01 06 -- ] ----WR-O-- Tracking servo failure. #--------------------------------------------------------DEFINE_EVENT # [ 09 02 DEFINE_EVENT # [ 09 03 100166 CRITICAL DEFAULT # msg num 105 06 -- ] ----WR-O-- Focus servo failure. 100266 CRITICAL DEFAULT # msg num 106 04 -- ] ----WR-O-- Spindle servo failure.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # [ 04 00 DEFINE_EVENT # [ 08 00 DEFINE_EVENT # [ 41 00 05 -- ] 100273 CRITICAL DEFAULT # msg num 118 04 -- ] DTL-WRSOMC Logical unit communication failure. 100373 CRITICAL DEFAULT # msg num 114 04 -- ] D--------- Data path failure -- should use 40 nn.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files DEFINE_EVENT # [ -- -DEFINE_EVENT # [ -- -DEFINE_EVENT # [ -- -- 102476 CRITICAL 05 -- ] 102576 CRITICAL 09 -- ] 102676 CRITICAL -- 02 ] DEFAULT # msg num 133 DEFAULT # msg num 169 DEFAULT # msg num 174 #--------------------------------------------------------DEFINE_EVENT 100077 INFORMATION DEFAULT # msg num 137 # [ 00 01 06 -- ] -T-------- Filemark detected.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files # [ 33 00 DEFINE_EVENT # [ 50 00 DEFINE_EVENT # [ 51 00 DEFINE_EVENT # [ 52 00 03 -- ] -T-------100985 CRITICAL 03 -- ] -T-------101085 CRITICAL 03 -- ] -T-----O-101185 CRITICAL 03 -- ] -T-------- Tape length error. DEFAULT # msg num 155 Write append error. DEFAULT # msg num 158 Erase failure. DEFAULT # msg num 159 Cartridge fault.
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files #--------------------------------------------------------DEFINE_EVENT 100095 INFORMATION # [ -- -- -- 10 ] DEFAULT # msg num 177 #--------------------------------------------------------DEFINE_EVENT 100096 INFORMATION # [ -- -- -- 14 ] DEFAULT # msg num 177 #--------------------------------------------------------DEFINE_EVENT 100097 MAJOR_WARNING DEFAULT # msg num 179 # [ -- -- -- 18 ] #--------------------------------
Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files SEVERITY_ACTION SEVERITY_ACTION SEVERITY_ACTION SEVERITY_ACTION SEVERITY_ACTION INFORMATION MINOR_WARNING MAJOR_WARNING SERIOUS CRITICAL NOTIFY NOTIFY NOTIFY NOTIFY NOTIFY #****************************************************************************# #* *# #* cfg-verb event# --severity--- action- ---------description------------- *# #* *# #****************************************************************************# DEF
Hardware Monitor Configuration Files Startup Configuration File Startup Configuration File Each hardware event monitor has its own startup configuration file which contains the monitoring requests currently defined for the monitor.
Hardware Monitor Configuration Files Startup Configuration File Considerations for Modifying the Startup Configuration File Settings While you can edit the contents of the startup configuration file directly, the better approach is to use the Hardware Monitoring Request Manager (monconfig) to create and manage your monitoring requests. Using the monitoring request manager you can create requests for multiple monitors simultaneously.
Hardware Monitor Configuration Files Startup Configuration File Table 5-3 Startup Configuration File Entries Keyword Target Type (required) Values Valid values include: UDP TCP OPC SNMP TEXTLOG SYSLOG EMAIL CONSOLE Description Identifies the method of notification used.
Hardware Monitor Configuration Files Startup Configuration File Default File Entries The following default monitoring requests illustrate the structure of the entries in the startup configuration file. Table 5-4 Default Monitoring Requests Description Entry Entry to send all events to textlog MONITOR: /storage/events/disk_arrays/FW_SCSI Criteria Threshold: INFORMATION Criteria Operator: >= Target Type: TEXTLOG Target TEXTLOG File: /var/opt/resmon/log/event.
Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Peripheral Status Monitor (PSM) Configuration File Interaction between the PSM and a hardware event monitor is controlled by a PSM configuration file. This file defines what severity levels will result in DOWN status being reported, and what action, if any, is required to return the hardware to UP status. Any hardware event monitor that does not include a PSM configuration file will not be monitored by the PSM.
Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Considerations for Modifying the PSM Configuration File • The only change you should consider making to the PSM configuration file is redefining the severity levels which cause a change to DOWN status. By default, SERIOUS and CRITICAL events will result in a DOWN status.
Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Table 5-5 PSM Configuration File Fields Keyword Values Description MONITOR_RESOURCE_NAME (required) A valid event monitor resource path name Identifies the hardware event monitor to which the entry applies Note: This must the first keyword in the file. PSM_RESOURCE_NAME (Optional) A valid PSM (status) resource path name This value should be related to MONITOR_RESOURCE_ NAME.
Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Table 5-5 PSM Configuration File Fields (Continued) Keyword Values DOWN_SEVERITY_THRESHOLD (Optional.
Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Example File Entries The following examples illustrate the various types of file entries that can be made for the PSM monitor. Example 1: Use all default values. SERIOUS and CRITICAL event will cause DOWN status. MONITOR_RESOURCE_NAME: /storage/events/disks/default Example 2: Change the entry so MAJOR_WARNING events will also cause DOWN status.
Hardware Monitor Configuration Files Pushing EMS Hardware Monitors configuration to multiple systems Pushing EMS Hardware Monitors configuration to multiple systems To push EMS Hardware Monitors configuration to multiple systems, do the following: • Do the configuration on one system via monconfig (creates appropriate /var/stm/config/tools/monitor/*.sapcfg) • Do additional manual edits, if any, in the other configuration files: /var/stm/config/tools/monitor/*.cfg, default_*.
Special Procedures 6 Special Procedures This chapter describes the special procedures required for the Fibre Channel Arbitrated Loop Monitor (dm_fc_hub), and for the Fibre Channel Switch Monitor (dm_fc_sw).
Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Fibre Channel Arbitrated Loop Hub Monitor History • IPR 9902: Initial release Supported Products • Fibre Channel Arbitrated Loop Hub Model A3724A • Fibre Channel Arbitrated Loop Hub Model A4839A Special Requirements The FC-AL Hub monitor requires: Device Firmware revisions: • Device Agent Firmware revision 2.14 or greater • Hub Controller Firmware revision 3.
Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Initial Monitor Configuration Unlike the other EMS Hardware Monitors, the FC-AL hub monitor requires some initial configuration before it will function. Because a FC-AL hub is not part of the host's configuration, the host cannot detect any hubs during startup. You must tell the hub monitor what hubs you want it to monitor. This is done by defining two settings in the hub monitor configuration file, HUB_COUNT and HUB_X_IP_ADDRESS.
Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Adding or Removing an FC-AL Hub Adding or removing a hub from the monitor configuration involves changing the same configuration file settings described in the preceding procedure, HUB_COUNT and HUB_X_IP_ADDRESS. Changing the FC-AL Hub Monitoring Configuration To change the FC Step 1. Determine the IP address for each hub your are adding or deleting. Step 2. Open file /var/stm/config/tools/monitor/dm_fc_hub.cfg in an ASCII text editor. Step 3.
Special Procedures Fibre Channel Arbitrated Loop Hub Monitor • Repeat Frequency: 1 day (1440 minutes) • Severity Action: Notify for all levels The hub monitor also uses the following settings to configure the SNMP environment used by the hub. Note that two of these settings (HUB_COUNT and HUB_X_IP_ADDRESS) are required to indicate to the monitor what hubs should monitored.
Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Table 6-1 PSM Configuration File Fields (Continued) Setting Default Value Description HUB_X_IS_MONITORED value 1 (Yes) This setting determines if the indicated hub will be monitored. Valid values are 0 (No) and 1 (Yes). HUB_X_SYSNAME text none Identifies the hub's sysname if the hub's system.sysName value is not set. PSM Configuration File File name: /var/stm/config/tools/monitor/dm_fc_hub.
Special Procedures Fibre Channel Switch Monitor Fibre Channel Switch Monitor History • IPR 9904: Initial release Supported Products • Gigabit Fibre Channel Switch Model A5223A Special Requirements The FC Switch monitor requires: C++ runtime support patches: • 10.20 PHSS_16585 (supersedes PHSS_14262) • 11.00 PHSS_16587 (supersedes PHSS_14577) Before using the switch monitor, edit the monitor configuration file, /var/stm/config/tools/monitor/dm_fc_sw.cfg, to indicate what switches will be monitored.
Special Procedures Fibre Channel Switch Monitor Configuring the FC Switch Monitor Configuration File To configure the FC switch monitor configuration file complete the following steps: Step 1. Determine which switches you want the monitor to be responsible for. Record the IP address for each of these switches. Step 2. Open file /var/stm/config/tools/monitor/dm_fc_sw.cfg in an ASCII text editor. Step 3.
Special Procedures Fibre Channel Switch Monitor Step 1. Determine the IP address for each switch you are adding or deleting. Step 2. Open file /var/stm/config/tools/monitor/dm_fc_sw.cfg in an ASCII text editor. Step 3. Locate the following line in the file and change value “n” to reflect the new number of switches to be monitored: SW_COUNT n Step 4. If you are adding a switch, add the following line to file: SW_X_IP_ADDRESS nn.nn.nnn.
Special Procedures Fibre Channel Switch Monitor The switch monitor also uses the following settings to configure the SNMP environment used by the switch. Note that two of these settings (SW_COUNT and SW_X_IP_ADDRESS) are required to indicate to the monitor what switches should monitored.
Special Procedures Fibre Channel Switch Monitor Table 6-2 PSM Configuration File Fields (Continued) Setting Default Value Description SW_X_IS_MONITORED value 1 (Yes) This setting determines if the indicated switch will be monitored. Valid values are 0 (No) and 1 (Yes). SW_X_SYSNAME text none Identifies the switch's sysname if the switch's system.sysName value is not set. PSM Configuration File File name: /var/stm/config/tools/monitor/dm_fc_sw.
Special Procedures Fibre Channel Switch Monitor 138 Chapter 6
Index A adding event monitoring requests, 46 adding PSM monitoring requests, 82 asynchronous event detection, 62, 67, 68 C changing device status, 91 checking detailed monitoring status, 54 client configuration files, 95, 96 configuration files client, 95, 96 global, 94, 103, 115 modifying, 102 modifying PSM, 122 modifying startup, 118 monitor, 62 monitor-specific, 94, 115, 116 PSM, 121 startup, 63, 117, 120 configuration files for hardware monitoring, 93 configuring MC/Service Guard package dependencies mo
Index L listing event monitoring requests, 44 M MC/Service Guard package dependencies, 79 memory supported by monitors, 33 memory monitor polling, 69, 71 modifying configuration files, 102 for PSM, 122 for startup, 118 modifying event monitoring requests, 52 modifying PSM monitoring requests, 88 monitor configuration files, 62 monitor descriptions Fibre Channel Arbitrated Loop Hub, 128 Fibre Channel Switch, 133 O overview of PSM, 74 P package dependencies, 80 polling event, 69, 70 FC-AL Hub, 69 memory monit
