HP (Hewlett-Packard) B6191-90029 инструкция обслуживания

EMS Hardware Monitors User's Guide Manufacturing P art Number: B6191-90029 May 2005 © Copyright 1979-2005 Hewlett-P ackard Development Company , L.P .[...]

2 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 w arranty statements accompanying such products and services . Nothing herein should be construed as constituting an additional warranty . HP shall not be liable for technical or editori[...]

3 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 c hanges when extensive technical changes are incorporated. New editions of this manual will in[...]

4[...]

Contents 5 1. Introduction Hardware Monitoring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 What is Hardware Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 How Does Hardware Monitoring W ork? . .[...]

Contents 6 Event P olling (in Detail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 4. Using the P eripheral Status Monitor P eripheral Status Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 How [...]

Contents 7 File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 File F ormat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Considerations for Modifyin[...]

Contents 8[...]

T ables 9 T able 1-1. Hardw are Monitoring T erms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 T able 2-1. Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 T able 2-2. Disk Products . . . . . . . . . . . . . . [...]

T ables 10[...]

F igures 11 Figure 1-1. Components Involved in Hardw are Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Figure 2-1. The Steps for Installing and Configuring Hardw are Monitoring . . . . . . . . . . . . . . . . . . 27 Figure 2-2. Building a Monitoring Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]

F igures 12[...]

13 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, “In[...]

14 • 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 A vailability (HA) Monitors rather than to the EMS Hardware Monitors . Rel[...]

Chapter 1 Introduction 15 1 Introduction This chapter introduces the EMS Hardware Monitors . The topics discussed in this chapter include the following: • What is hardware monitoring? • How does hardware monitoring work? • Benefits of hardware monitoring • Products supported by hardware monitoring • Tips for hardware monitoring • Hardw[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 16 Hardware Monitoring Overview What is Hardware Monitoring? Hardware monitoring is the process of w atching 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 [...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 17 How Does Hardware Monitoring W ork? 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 hardw are eve[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 18 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 fo[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 19 Products Supported by Hardware Monitors EMS Hardware Monitors are provided for a wide range of system hardw are 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 ea[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 20 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,[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 21 Hardware Monitoring T erms 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 . T able 1-1 Hardware Monitoring T erms T erm Definition Asynchronous event detection The ability[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 22 Hardware event monitor A monitor daemon that gathers information on the operational status of hardware resources . Each monitor is responsible for watc hing a specific group or type of hardware resources. F or example, the tape monitor handles all tape devices on the system. The monitor may[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 23 P eripheral 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 mana[...]

Chapter 1 Introduction Hard ware Monitoring Over vie w 24[...]

Chapter 2 Installing and Using Monitors 25 2 Installing and Using Monitors This chapter instructs you how to use the EMS Hardw are Monitors to manage your hardware resources . The topics discussed in this chapter include: • An overview of the steps involved • Installing EMS Hardware Monitors • Adding and managing monitor requests • Disablin[...]

Chapter 2 Installing and Using Monitors The Steps In volved 26 The Steps Involved The steps involved in installing and configuring hardware monitoring are shown in F igure 2-1 on page 27. Each step is described in detail in this chapter on the page indicated. Installation of Support T ools is necessary if you have Diagnostic/IPR Media release earl[...]

Chapter 2 Installing and Using Monitors The Steps In volved 27 Figure 2-1 The Steps for Installing and Configuring Hardware Monitoring[...]

Chapter 2 Installing and Using Monitors Installing EMS Hard ware Monitors 28 Installing EMS Hardware Monitors The EMS Hardware Monitors softw are is distributed with the Support T ools (diagnostics). All the necessary files for hardware monitoring are installed automatically when the Support T ools are installed. There are several different wa ys [...]

Chapter 2 Installing and Using Monitors Installing EMS Hard ware Monitors 29 • HP 9000 Series 700 or 800 Computer • HP-UX 10.20 or 11.x (Hardware event monitoring is not currently a vailable 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 m[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 30 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 . T able 2-1 Disk Arrays Product Model/Product Number Special Requirem[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 31 Important: HP Storage W orks SDL T 160/320 GB T ape Drive and the HP Ultrium 460 External T ape Drive are not supported by the Online Diagnostics product. Some STM tools may function but these tools are not supported. The diagnostics tools and utilities that support these[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 32 In addition to the above products, the SCSI T ape Devices Monitor supports all SCSI tape resources bound to the PCI tape driver . SCSI tape resources bound to tape2 - NIO (HP-PB) tape driver and stape - GSC (HSC) tape driver are not supported on HP-UX 11i v2 May 2005 rele[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 33 DL T 4000 & 7000; 100 slot; Drives Diff; Robotics SE DL T 4000 & 7000; 30 slot; Differential As of the March 2000 release (IPR0003), the monitor also supports the following devices: DDS-4 Autoloader DL T7000 HP Surestore T ape Autoloader Model 1/9 DL T8000 HP Sure[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 34 T able 2-5 Fibre Channel SCSI Multiplexers Product Model/Product Number Special Requirements HP Fibre Channel SCSI Multiplexer Supported by: Fibre Channel SCSI Multiplexer Monitor A3308A Firmw are version 3840 T able 2-6 Fibre Channel Adapters Product Model/Product Number[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 35 T able 2-7 Fibre Channel Arbitrated Loop (FC-AL) Hub Product Model/Product Number Special Requirements HP Fibre Channel Arbitrated Loop Hubs Supported by: Fibre Channel Arbitrated Loop Hub Monitor A3724A A4839A The FC-AL Hub monitor requires: Device Firmw are revisions: ?[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 36 T able 2-9 Memory Product Model/Product Number Special Requirements All system memory on P A-RISC systems. Supported by: P A Memory Monitor NA None Itanium Memory Monitor: monitor for all system memory on Itanium systems. Supported by: Itanium Memory Monitor NA HP-UX 11.2[...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 37 Low Priority Machine Checks (LPMCs) Supported by: LPMC Monitor NA HP-UX 11.x IPMI F orward Progress Log Monitor monitors IPMI FPL log entries on the system. Supported by: IPMI F orward Progress Log Monitor NA All HP-UX IPF systems running HP-UX 11.23 or later . All HP-UX [...]

Chapter 2 Installing and Using Monitors Checking f or Special Requirements 38 T able 2-12 Others Product Model/Product Number Special Requirements iSCSI Subsystem HP-UX software solution for iSCSI protocol. Supported by: iSCSI Subsystem Monitor NA HP-UX 11.23, P atch PHSS_30457 for IA 11.23 (11.23) Codename: iHOP F or product support information: h[...]

Chapter 2 Installing and Using Monitors Using Hard ware Monitoring Requests 39 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 d[...]

Chapter 2 Installing and Using Monitors Using Hard ware Monitoring Requests 40 Figure 2-2 Building a Monitoring Request[...]

Chapter 2 Installing and Using Monitors Running the Monitoring Request Manager 41 Running the Monitoring Request Manager NO TE Y ou must be logged on as root to run the Monitoring Request Manager . T o run the Monitoring Request Manager , type: /etc/opt/resmon/lbin/monconfig The opening screen indicates if monitoring is currently enabled or disable[...]

Chapter 2 Installing and Using Monitors Enabling Har dware Event Monitoring 42 Enabling Hardware Event Monitoring Hardware event monitoring must be enabled to protect your system from undetected hardw are failures. All hardware monitoring requests are ignored while monitoring is disabled. Once monitoring has been enabled, all hardware event monitor[...]

Chapter 2 Installing and Using Monitors Enabling Har dware Event Monitoring 43 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 monitorin[...]

Chapter 2 Installing and Using Monitors Listing Monitor Descriptions 44 Listing Monitor Descriptions One of the first steps in managing monitoring requests is selecting the proper monitor for the hardware resource. Y ou must know what hardware resources each monitor is responsible for to ensure that you select the proper monitor . Listing the desc[...]

Chapter 2 Installing and Using Monitors Viewing Current Monitoring Requests 45 V iewing 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 wh[...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 46 Adding a Monitoring Request Adding a monitoring request is a convenient wa y 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 identi[...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 47 added to the monitoring configuration. When you restart the system or execute the IOSCAN utility (thus performing a real/hard IOSCAN), the new hardw are will be included in event monitoring . If you add a new class of supported hardware resource to your system, any monitoring r[...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 48 Notification Method The following notification methods are available . EMAIL* - sends notification to the specified email address TEXTLOG* - sends notification to specified file SNMP - sends notification using SNMP traps CONSOLE - sends notification to the system consol[...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 49 Minor W arning 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 [...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 50 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 arra y monitor to an email address of admin@hp.com . =========[...]

Chapter 2 Installing and Using Monitors Adding a Monitoring Request 51 Enter Email Address: [root] admin@hp.com admin@hp.com User Comment: (C)lear (A)dd Enter selection {or (Q)uit,(H)elp} [c] a <== ADD COMMENT Enter comment: [] This is a test message. IF DESIRED Client Configuration File: (C)lear (A)dd Use Clear to use the default file. Enter se[...]

Chapter 2 Installing and Using Monitors Modifying Monitoring Requests 52 Modifying Monitoring Requests Modifying an existing monitoring request is a convenient wa y 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. T o modify [...]

Chapter 2 Installing and Using Monitors V erifying Hard ware Event Monitoring 53 V erifying Hardware Event Monitoring Once you have created the monitoring requests you need for your system, you may w ant to verify that they are working as you expect. The most effective wa y of verifying hardware event monitoring is to simulate a hardware failure or[...]

Chapter 2 Installing and Using Monitors Checking Detailed Monitoring Status 54 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 . Unlike the option to [...]

Chapter 2 Installing and Using Monitors Retrieving and Interpreting Event Messages 55 Retrieving and Interpreting Event Messages Event messages generated by hardware monitoring can be delivered using a variety of notification methods . T o simplify receiving event messages you may w ant to use the email and/or textfile notification methods. Both[...]

Chapter 2 Installing and Using Monitors Deleting Monitoring Requests 56 Deleting Monitoring Requests Y ou may want to delete any monitor requests for a hardw are resource that has been removed from your system. Only requests created exclusively for the missing resource should be deleted. CA UTION Use careful consideration before deleting monitoring[...]

Chapter 2 Installing and Using Monitors Disabling Har dware Event Monitoring 57 Disabling Hardware Event Monitoring Y ou can disable hardware event monitoring if desired. However , all EMS Hardware Monitors will be disabled. Y ou cannot disable a specific monitor . While monitoring is disabled, all monitoring requests are disabled. The monitoring [...]

Chapter 2 Installing and Using Monitors Disabling Har dware Event Monitoring 58[...]

Chapter 3 Detailed Description 59 3 Detailed Description This chapter describes EMS Hardware Monitors in detail. The topics discussed in this c hapter include: • Hardware monitoring architecture . • Hardware monitoring request manager . • EMS hardware event monitor . • P olling or asynchronous? • Startup client. • P eripheral status mon[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 60 The Detailed Picture of Hardware Monitoring The following figure shows the major components involved in hardware monitoring and the communication paths between them. Figure 3-1 Hardware Monitoring Architecture[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 61 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 [...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 62 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 bac kground continuously . The event monitor watches all instances of the hardware resources it suppo[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 63 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 . During system startup, following the execution of the IOSCAN utility (thus performin[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 64 File Locations The following table lists the locations of the files involved in hardware monitoring . In the above table, monitor_name is the name of a particular monitor such as armmon . T able 3-1 File Locations Directories and Files Description /usr/sbin/stm/uut/bin/[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 65 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 ). The startup client is run w[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 66 Disabling Monitoring Hardware monitoring can be disabled using the Hardw are Monitoring Request Manager . Disabling monitoring disables all EMS Hardware Monitors . Individual monitors cannot be disabled using the Hardware Monitoring Request Manager . When monitoring is d[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 67 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. The devic[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 68 Figure 3-3 Asynchronous Event Detection Process[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 69 Event P olling (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 comm[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 70 Figure 3-4 Monitoring P olling Process[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 71 Figure 3-5 Memory Monitor P olling Process[...]

Chapter 3 Detailed Description The Detailed Picture of Hard ware Monitoring 72[...]

Chapter 4 Using the P eripheral Status Monitor 73 4 Using the P eripheral Status Monitor This chapter describes the P eripheral Status Monitor , which converts hardw are events to status information for use by MC/ServiceGuard. The topics in this chapter include: • An overview of the PSM • How to configure MC/ServiceGuard package dependencies w[...]

Chapter 4 Using the P eripheral Status Monitor P eripheral Status Monitor Overview 74 P eripheral Status Monitor Overview The primary function of the P eripheral 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 informa[...]

Chapter 4 Using the P eripheral Status Monitor How Does the PSM W ork? 75 How Does the PSM W ork? The PSM converts hardware events detected by the EMS Hardw are 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 o[...]

Chapter 4 Using the P eripheral Status Monitor How Does the PSM W ork? 76 Figure 4-1 P eripheral Status Monitor[...]

Chapter 4 Using the P eripheral Status Monitor How Does the PSM W ork? 77 PSM Components The PSM comprises the following components, whic h are installed along with the hardware event monitors. Each component has its own man page containing detailed information about its operation. • psmctd - the P eripheral Status Client/T arget daemon used to m[...]

Chapter 4 Using the P eripheral Status Monitor How Does the PSM W ork? 78 The status resource class path for each monitor is included in the monitor descriptions are a vailable on the W eb at http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_summ.htm . An HP-UX man page is available for each monitor . T o access the man page, type (where monitorname [...]

Chapter 4 Using the P eripheral Status Monitor Configuring MC/ServiceGuard P ackage Dependencies with the PSM 79 Configuring MC/ServiceGuard P ackage Dependencies with the PSM The PSM allows you to create MC/ServiceGuard package dependencies for resources monitored by EMS Hardware Monitors . T o use the PSM with MC/ServiceGuard, you configure on[...]

Chapter 4 Using the P eripheral Status Monitor Configuring MC/ServiceGuard P ackage Dependencies with the PSM 80 Configuring P ackage 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 cluste[...]

Chapter 4 Using the P eripheral Status Monitor Configuring MC/ServiceGuard P ackage Dependencies with the PSM 81 Configuring P ackage Dependencies by Editing the Configuration File Y ou 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 m[...]

Chapter 4 Using the P eripheral Status Monitor Creating EMS Monitoring Requests for PSM 82 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 [...]

Chapter 4 Using the P eripheral Status Monitor Monitoring Request P arameters 83 Monitoring Request P arameters The following information describes in detail the monitoring request parameters and offers tips on how to use them. Specifying When to Send Event - <Notify> One of the first steps in creating a monitoring request involves specifyin[...]

Chapter 4 Using the P eripheral Status Monitor Monitoring Request P arameters 84 Setting the P olling Interval - <P olling Interval> The polling interval specifies how often EMS will check the PSM for changes in hardw are status. The polling interval is the maximum amount of elapsed time before EMS will be aw are of a change in status for th[...]

Chapter 4 Using the P eripheral Status Monitor Monitoring Request P arameters 85 SNMP traps This option sends messages to applications using SNMP traps, suc h as Network Node Manager . See HP OpenV iew Using Network Node Manager (P/N J1169-90002) for more information on configuring SNMP traps . The following traps are used by EMS: EMS_ENTERPRISE_O[...]

Chapter 4 Using the P eripheral Status Monitor Monitoring Request P arameters 86 T o set for email notification: 1. Select the Email option from the <Notify via> list. 2. Specify the full email address in the Email Address field. syslog This option sends event notification to the system log. F or an abnormal event, a system logging level o[...]

Chapter 4 Using the P eripheral Status Monitor Copying Monitoring Requests 87 Copying Monitoring Requests There are two wa ys to use the copy function: • T o create requests for multiple resources using the same monitoring parameters. This is a quic k way to set requests for multiple resources. • T o create requests for the same resource using [...]

Chapter 4 Using the P eripheral Status Monitor Modifying Monitoring Requests 88 Modifying Monitoring Requests T o 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 Monitor[...]

Chapter 4 Using the P eripheral Status Monitor Removing Monitoring Requests 89 Removing Monitoring Requests The Remove Monitoring Requests functions with multiple requests as well as single requests. T o remove monitoring requests: 1. From the Event Monitoring Service main screen, select the monitoring request you wish to remove. T o select contigu[...]

Chapter 4 Using the P eripheral Status Monitor Viewing Monitoring Requests 90 V iewing Monitoring Requests T o 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 V iew Monitoring Request The V[...]

Chapter 4 Using the P eripheral Status Monitor Using the set_fixed Utility to Restore Hard ware UP State 91 Using the set_fixed Utility to Restore Hardware UP State Most hardware event monitors cannot detect when a hardw are failure has been repaired and the resource has been returned to normal operation. Consequently , these monitors cannot alert[...]

Chapter 4 Using the P eripheral Status Monitor Using the set_fixed Utility to Restore Hard ware UP State 92[...]

Chapter 5 Hardware Monitor Configuration Files 93 5 Hardware Monitor Configuration F iles 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,[...]

Chapter 5 Hardware Monitor Configuration Files Overview 94 Overview Understanding Multiple-View and Non-Multiple-V iew Monitor Classes EMS Hardware Monitors are divided into two classes: Multiple-V iew and Non-Multiple-View . Multiple-View monitors allow you to specify different event messages (for the same monitor) to one or more targets (“clie[...]

Chapter 5 Hardware Monitor Configuration Files Client Configuration File 95 Client Configuration F ile 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 immed[...]

Chapter 5 Hardware Monitor Configuration Files Client Configuration File 96 OR /etc/opt/resmon/lbin/send_test_event The program was created for HP Support Applications to ensure that the communication mec hanism from the monitor to HP Support is working. However , it can be used by customers to ensure the same thing: that the communication mechan[...]

Chapter 5 Hardware Monitor Configuration Files Client Configuration File 97 # 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[...]

Chapter 5 Hardware Monitor Configuration Files Client Configuration File 98 # 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:[...]

Chapter 5 Hardware Monitor Configuration Files Client Configuration File 99 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:TR[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 100 Monitor-Specific and Global Configuration F iles The common operating parameters defined by the monitor -specific and global configuration files for all non-multiple-view monitors include: • P olling Interval - identifies the frequency at [...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 101 T able 5-1 lists the common fields used to define monitor configuration settings. In addition to the common parameters, some monitors inc lude other parameters in their configuration file. Any additional configuration parameters used by each [...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 102 Considerations for Modifying the Monitor Configuration File Settings The default configuration settings for each monitor have been carefully selected to provide efficient monitoring for most systems. However , it may be necessary to modify these[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 103 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 . P olling Interva[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 104 # C = COMMUNICATION DEVICE # # DTLPWRSOMC = SCSI Device Class # #--> [ 28 00 06 -- ] DTLPWRSOMC Not-ready to ready transition. Medium changed. # # cc qq kk ss Data elements equating to event # # cc = SCSI Additional Sense Code # qq = SCSI Additi[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 105 # [ 30 01 06 -- ] DEFINE_EVENT 100308 INFORMATION DEFAULT # msg num 8 # [ 3a 00 06 -- ] #--------------------------------------------------------- DEFINE_EVENT 100109 INFORMATION DEFAULT # msg num 9 # [ 30 00 06 -- ] DEFINE_EVENT 100209 INFORMATION[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 106 #--------------------------------------------------------- DEFINE_EVENT 100020 INFORMATION DEFAULT # msg num 20 # [ 3f 03 06 -- ] DTLPWRSOMC Inquiry data has changed. #--------------------------------------------------------- DEFINE_EVENT 100021 IN[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 107 DEFINE_EVENT 101726 MINOR_WARNING DEFAULT # msg num 40 # [ 18 05 01 -- ] DEFINE_EVENT 101826 MINOR_WARNING DEFAULT # msg num 41 # [ 18 06 01 -- ] DEFINE_EVENT 101926 MINOR_WARNING DEFAULT # msg num 42 # [ 1e 00 01 -- ] D---W--O-- Recovered id with [...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 108 #--------------------------------------------------------- DEFINE_EVENT 100136 CRITICAL DEFAULT # msg num 57 # [ 12 00 03 -- ] D---W--O-- Address mark not found for id field. DEFINE_EVENT 100236 CRITICAL DEFAULT # msg num 58 # [ 13 00 03 -- ] D---W[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 109 # [ 32 00 -- -- ] DEFINE_EVENT 100242 CRITICAL DEFAULT # msg num 76 # [ 32 01 03 -- ] D---W--O-- Defect list update failure. DEFINE_EVENT 100342 CRITICAL DEFAULT # msg num 76 # [ 32 02 03 -- ] #------------------------------------------------------[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 110 # [ 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. #-----------------------------------------[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 111 DEFINE_EVENT 100065 CRITICAL DEFAULT # msg num 104 # [ 09 01 06 -- ] ----WR-O-- Tracking servo failure. #--------------------------------------------------------- DEFINE_EVENT 100166 CRITICAL DEFAULT # msg num 105 # [ 09 02 06 -- ] ----WR-O-- Focus[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 112 # [ 04 00 05 -- ] DEFINE_EVENT 100273 CRITICAL DEFAULT # msg num 118 # [ 08 00 04 -- ] DTL-WRSOMC Logical unit communication failure. DEFINE_EVENT 100373 CRITICAL DEFAULT # msg num 114 # [ 41 00 04 -- ] D--------- Data path failure -- should use 40[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 113 DEFINE_EVENT 102476 CRITICAL DEFAULT # msg num 133 # [ -- -- 05 -- ] DEFINE_EVENT 102576 CRITICAL DEFAULT # msg num 169 # [ -- -- 09 -- ] DEFINE_EVENT 102676 CRITICAL DEFAULT # msg num 174 # [ -- -- -- 02 ] #----------------------------------------[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 114 # [ 33 00 03 -- ] -T-------- Tape length error. DEFINE_EVENT 100985 CRITICAL DEFAULT # msg num 155 # [ 50 00 03 -- ] -T-------- Write append error. DEFINE_EVENT 101085 CRITICAL DEFAULT # msg num 158 # [ 51 00 03 -- ] -T-----O-- Erase failure. DEFIN[...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 115 #--------------------------------------------------------- DEFINE_EVENT 100095 INFORMATION DEFAULT # msg num 177 # [ -- -- -- 10 ] #--------------------------------------------------------- DEFINE_EVENT 100096 INFORMATION DEFAULT # msg num 177 # [ [...]

Chapter 5 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files 116 SEVERITY_ACTION INFORMATION NOTIFY SEVERITY_ACTION MINOR_WARNING NOTIFY SEVERITY_ACTION MAJOR_WARNING NOTIFY SEVERITY_ACTION SERIOUS NOTIFY SEVERITY_ACTION CRITICAL NOTIFY #***************************************************************************[...]

Chapter 5 Hardware Monitor Configuration Files Startup Configuration File 117 Startup Configuration F ile Each hardw are event monitor has its own startup configuration file which contains the monitoring requests currently defined for the monitor . At startup, following the execution of the IOSCAN utility (performing a real/hard ioscan), or w[...]

Chapter 5 Hardware Monitor Configuration Files Startup Configuration File 118 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 [...]

Chapter 5 Hardware Monitor Configuration Files Startup Configuration File 119 T able 5-3 Startup Configuration File Entries Keyword V alues Description T arget Type (required) V alid values include: UDP TCP OPC SNMP TEXTLOG SYSLOG EMAIL CONSOLE Identifies the method of notification used. T arget Type Modifier (required for the following targe[...]

Chapter 5 Hardware Monitor Configuration Files Startup Configuration File 120 Default File Entries The following default monitoring requests illustrate the structure of the entries in the startup configuration file. T able 5-4 Default Monitoring Requests Description Entry Entry to send all events to textlog MONITOR: /storage/events/disk_arrays/[...]

Chapter 5 Hardware Monitor Configuration Files P eripheral Status Monitor (PSM) Configuration File 121 P eripheral 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 w[...]

Chapter 5 Hardware Monitor Configuration Files P eripheral Status Monitor (PSM) Configuration File 122 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 eve[...]

Chapter 5 Hardware Monitor Configuration Files P eripheral Status Monitor (PSM) Configuration File 123 T able 5-5 PSM Configuration File F ields Keyword V alues 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[...]

Chapter 5 Hardware Monitor Configuration Files P eripheral Status Monitor (PSM) Configuration File 124 DOWN_SEVERITY_THRESHOLD (Optional. This value is required if DOWN_SEVERITY_OPERATOR is specified) V alid values include: CRITICAL SERIOUS (De fault) MAJOR_W AR NING MINOR_W AR NING INFORMATIO NAL Defines the event severity level used with DOWN[...]

Chapter 5 Hardware Monitor Configuration Files P eripheral Status Monitor (PSM) Configuration File 125 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: /storag[...]

Chapter 5 Hardware Monitor Configuration Files Pushing EMS Hard ware Monitors configuration to m ultiple systems 126 Pushing EMS Hardware Monitors configuration to multiple systems T o push EMS Hardware Monitors configuration to multiple systems , do the following: • Do the configuration on one system via monconfig (creates appropriate /var[...]

Chapter 6 Special Procedures 127 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) .[...]

Chapter 6 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor 128 F ibre 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 Firmw are rev[...]

Chapter 6 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor 129 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. Y ou[...]

Chapter 6 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor 130 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 T o chang[...]

Chapter 6 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor 131 • Repeat Frequency: 1 da y (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 indi[...]

Chapter 6 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor 132 PSM Configuration File File name: /var/stm/config/tools/monitor/dm_fc_hub.psmcfg Default settings: • PSM Resource Name: /connectivity/status/hubs/FC_hub • State Handling: Requires the use of set_fixed to set UP state. • DOWN state mapping: Serious and Critical map to[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 133 F ibre 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 (supers[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 134 Configuring the FC Switch Monitor Configuration File T o configure the FC switch monitor configuration file complete the following steps: Step 1. Determine which switches you w ant the monitor to be responsible for . Record the IP address for each of these switches . Step 2. Open ?[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 135 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 mon[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 136 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. Changes that involve adding or deleting swit[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 137 PSM Configuration File File name: /var/stm/config/tools/monitor/dm_fc_sw.psmcfg Default settings: • PSM Resource Name: /connectivity/status/switches/FC_sw • State Handling: Requires the use of set_fixed to set UP state. • DOWN state mapping: Serious and Critical map to DOWN . SW_[...]

Chapter 6 Special Procedures Fibre Channel Switch Monitor 138[...]

139 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 s[...]

Index 140 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 mo[...]