HP B6191-90029 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Monitor
  5. B6191-90029
  6. User manual
HP B6191-90029 User Manual

HP B6191-90029 User Manual

Ems hardware monitors
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
EMS Hardware Monitors User's Guide
Manufacturing Part Number: B6191-90029
May 2005
© Copyright 1979-2005 Hewlett-Packard Development Company, L.P.

Advertisement

Table of Contents
loading

Related Manuals for HP B6191-90029

Summary of Contents for HP B6191-90029

  • Page 1 EMS Hardware Monitors User's Guide Manufacturing Part Number: B6191-90029 May 2005 © Copyright 1979-2005 Hewlett-Packard Development Company, L.P.

  • Page 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 warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.

  • Page 3: April 2003 Edition

    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.

  • Page 5: Table Of Contents

    1. Introduction Hardware Monitoring Overview ............16 What is Hardware Monitoring? .
  • Page 6 Contents Event Polling (in Detail) ............. 69 4.
  • Page 7 File Names ..............121 File Format .
  • Page 8 Contents...
  • Page 9 Tables Table 1-1. Hardware Monitoring Terms ..........21 Table 2-1.
  • Page 10 Tables...
  • Page 11 Figures Figure 1-1. Components Involved in Hardware Monitoring ....... 17 Figure 2-1.
  • Page 12 Figures...

  • Page 13: About This Manual

    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.
  • Page 14 Edition number or publication date (from the title page). • Your name. • Your company’s name. Serious errors, such as technical inaccuracies that may render a program or a hardware device inoperative, should be reported to the HP Response Center or directly to a Support Engineer.

  • Page 15: Introduction

    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 •...

  • Page 16: Hardware Monitoring Overview

    Hardware monitoring is easily integrated with MC/ServiceGuard, and the necessary notification methods are provided for communication with other applications such as HP OpenView. Hardware monitoring is designed to provide a high level of protection against system hardware failure with minimal impact on system performance.

  • Page 17: How Does Hardware Monitoring Work

    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.

  • Page 18: Benefits Of Hardware Monitoring

    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.

  • Page 19: Products Supported By Hardware Monitors

    A detailed list of the specific hardware products supported by each hardware monitor is included in http://docs.hp.com/en/diag/ - the online library for information about EMS Hardware Monitors (look for “Supported Products” under EMS Hardware Monitors).

  • Page 20: Tips For Hardware Monitoring

    If you are using MC/ServiceGuard, you should consider using the PSM to include your system hardware resources in the MC/ServiceGuard strategy. In addition, the necessary notification methods are provided for communicating with network management application such as HP OpenView.  Utilize the many notification methods available. The notification methods provided by hardware monitoring provide a great deal of flexibility in designing a strategy to keep you informed of how well your...

  • Page 21: Hardware Monitoring Terms

    Event Monitoring The application framework used for monitoring system Service (EMS) resources on HP-UX 10.20 and 11.x. EMS Hardware Monitors use the EMS framework for reporting events and creating PSM monitoring requests. The EMS framework is also used by EMS High Availability Monitors.
  • Page 22 EMS GUI. Multiple-view As of the HP-UX 11.00/10.20 June 2000 release (IPR 0006), certain monitors will allow event reporting to be tailored for different targets (clients). This “multiple-view” (“Predictive-enabled”) feature will be added to all hardware monitors in future releases.
  • Page 23 Predictive-enabled See “multiple-view.” This feature enables hardware monitors to work with HP Support Applications. Resource instance A specific hardware device. The resource instance is the last element of the resource path and is typically the hardware path to the resource (e.g., 10_12_5.0.0), but it may also be a...
  • Page 24 Introduction Hardware Monitoring Overview Chapter 1...

  • Page 25: Installing And Using Monitors

    Installing and Using Monitors This chapter instructs you how to use the EMS Hardware 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 •...

  • Page 26: The Steps Involved

    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.

  • Page 27: Figure 2-1 The Steps For Installing And Configuring Hardware Monitoring

    Installing and Using Monitors The Steps Involved Figure 2-1 The Steps for Installing and Configuring Hardware Monitoring Chapter 2...

  • Page 28: Installing Ems Hardware Monitors

    The Support Plus Media: installing the OnlineDiag depot from the Support Plus Media using swinstall. • HP Software Depot website: downloading the “Support Tools for the HP 9000” in the “Enhancement Releases” product category, then using swinstall to install the OnlineDiag depot.

  • Page 29: Removing 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).

  • Page 30: Checking For Special Requirements

    Supported by: Fast/Wide SCSI Disk Array Monitor HP Fibre Channel High Availability Disk Array (Model 60/FC) Supported by Disk Array FC60 Monitor HP Storage Works Modular SAN array 1000 Supported by: HP Storage Works Modular SAN array 1000 Monitor Model/Product...

  • Page 31: Table 2-2 Disk Products

    This monitor should be disabled while taking a backup since EMS polling can interfere with the backup process. Tape products are monitored on releases prior to HP-UX 11i v2 May 2005 only. However, they are not monitored in the current release.
  • Page 32 In addition to the above products, the SCSI Tape 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 release.

  • Page 33: Table 2-4 High Availability Storage Systems

    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 Tape Library Model 20/700...

  • Page 34: Table 2-5 Fibre Channel Scsi Multiplexers

    Installing and Using Monitors Checking for Special Requirements Table 2-5 Fibre Channel SCSI Multiplexers Product HP Fibre Channel SCSI Multiplexer 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...

  • Page 35: Table 2-7. Fibre Channel Arbitrated Loop (Fc-Al) Hub

    Table 2-7 Fibre Channel Arbitrated Loop (FC-AL) Hub Model/Product Product Number HP Fibre A3724A Channel A4839A Arbitrated Loop Hubs Supported by: Fibre Channel Arbitrated Loop Hub Monitor Table 2-8 Fibre Channel Switch Model/Product Product Number HP Fibre A5223A Channel Switch...

  • Page 36: Table 2-9 Memory

    For example, resources associated with temperature or power supply. Supported by: Itanium Core Hardware Monitor Model/Product Special Number Requirements None HP-UX 11.22 OS or later Model/Product Special Number Requirements Superdome For HP-UX 11.11 OS S-Class only. The chassis code...

  • Page 37: Table 2-11 Interface Cards

    Supported by: SCSI123 Monitor Chapter 2 Model/Product Special Number Requirements HP-UX 11.x All HP-UX IPF systems running HP-UX 11.23 or later. All HP-UX PA systems running HP-UX 11.23 or later. The ia64_corehw monitor must be running. Hardware: HP-UX 11.x. HP9000 (/V) S700...
  • Page 38 Subsystem HP-UX software solution for iSCSI protocol. Supported by: iSCSI Subsystem Monitor All devices managed by HP device management software. Current plans are for many different types of devices to be supported, including disk drives, disk arrays, disk jbods, tape drives, tape libraries, FC hubs, switches and bridges.

  • Page 39: Using Hardware Monitoring Requests

    Some Monitoring Request Examples The following monitoring request applies to all monitors. It sends all events with a severity greater than or equal to MAJOR WARNING to an email address of sysad@hp.com: Send events generated by all monitors with severity >= MAJOR WARNING to EMAIL sysad@hp.com...

  • Page 40: Figure 2-2 Building A Monitoring Request

    Installing and Using Monitors Using Hardware Monitoring Requests Figure 2-2 Building a Monitoring Request Chapter 2...

  • Page 41: 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.

  • Page 42: Enabling Hardware Event Monitoring

    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.

  • Page 43: Default Monitoring Requests

    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.

  • Page 44: Listing Monitor Descriptions

    For a detailed list of the specific products each monitor supports, refer to the Diagnostics website at: http://docs.hp.com/en/diag/ Under “EMS Hardware Monitors,” click on “Supported Products” and “Data Sheets.” You can also refer to the man page for the particular monitor; for example, “man_disk_em”.

  • Page 45: 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.

  • Page 46: Adding A Monitoring Request

    (for example, for HP Support Applications). Adding a client configuration file at this prompt does not create or edit the file; it merely sets up the monitoring request to use the file. Unless you have a specific client that requires a client configuration file, choose (C)lear (the default).

  • Page 47: Table 2-14 Monitoring Requests Configuration Settings

    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.

  • Page 48: Table 2-15 Event Severity Levels

    Installing and Using Monitors Adding a Monitoring Request Table 2-14 Monitoring Requests Configuration Settings (Continued) Setting Notification The following notification methods are available. Method 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 console TCP - sends notification to the specified target host and port...
  • Page 49 Table 2-15 Event Severity Levels (Continued) Event Severity Level Description Minor An event that will not likely escalate Warning 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.

  • Page 50: Example Of 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. =================================================================== ===========...
  • Page 51 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.com with comment: This is a test message Are you sure you want to keep these changes? {(Y)es,(N)o,(H)elp} [n] y...

  • Page 52: Modifying Monitoring Requests

    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.

  • Page 53: Verifying Hardware Event Monitoring

    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.

  • Page 54: Checking Detailed Monitoring Status

    (Possibly there is no hardware to monitor.) >/system/events/memory ... OK. For /system/events/memory/49: Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log Events >= 4 (MAJOR WARNING) Goto SYSLOG Events >= 4 (MAJOR WARNING) Goto EMAIL; addr=root Events >= 4 (MAJOR WARNING) Goto TCP; host=hpbs1266.boi.hp.com port=53327 Chapter 2...

  • Page 55: Retrieving And Interpreting Event Messages

    /storage/events/disks/default/10_4_4.0.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time : Wed Sep 9 10:48:30 1998 Hostname : hpbs8684.boi.hp.com Event Id : 0x0035f6b15e00000000 Event # : 100037 Severity : CRITICAL Disk at hardware path 10/4/4.0.0 : Media failure...

  • Page 56: Deleting Monitoring Requests

    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.

  • Page 57: 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.
  • Page 58 Installing and Using Monitors Disabling Hardware Event Monitoring Chapter 2...

  • Page 59: Detailed Description

    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. •...

  • Page 60: The Detailed Picture Of Hardware Monitoring

    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. Figure 3-1 Hardware Monitoring Architecture Chapter 3...

  • Page 61: Components From Three Different Applications

    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.

  • Page 62: Ems Hardware Event Monitor

    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.

  • Page 63: Peripheral Status Monitor (Psm)

    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. During system startup, following the execution of the IOSCAN utility (thus performing a real/hard ioscan), or when managing requests using the Hardware Monitoring Request Manager, the startup client reads each configuration file and creates the monitoring requests defined by the entries in the file.

  • Page 64: File Locations

    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 /usr/sbin/stm/uut/bin/tools/monitor/monitor_name /var/stm/config/tools/monitor/Global.cfg /var/stm/config/tools/monitor/monitor_name.cfg /var/stm/config/tools/monitor/default_monitor_name.clcfg /var/stm/config/tools/monitor/monitor_name.sapcfg /var/stm/config/tools/monitor/monitor_name.psmcfg /etc/opt/resmon/lbin/monconfig /etc/opt/resmon/lbin/startcfg_client /etc/opt/resmon/lbin/set_fixed /etc/opt/resmon/dictionary/monitor_name.dict In the above table, monitor_name is the name of a particular monitor such as armmon.

  • Page 65: Startup Process (In Detail)

    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 when the system is restarted, following the execution of the IOSCAN utility (performing a real/hard ioscan), when the enable monitoring command is executed from the Hardware Monitoring Request Manager, or when monconfig changes the monitor requests.
  • Page 66 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.

  • Page 67: Asynchronous Event Detection (In Detail)

    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.

  • Page 68: Figure 3-3 Asynchronous Event Detection Process

    Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-3 Asynchronous Event Detection Process Chapter 3...

  • Page 69: Event Polling (In Detail)

    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.

  • Page 70: Figure 3-4 Monitoring Polling Process

    Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-4 Monitoring Polling Process Chapter 3...

  • Page 71: Figure 3-5 Memory Monitor Polling Process

    Detailed Description The Detailed Picture of Hardware Monitoring Figure 3-5 Memory Monitor Polling Process Chapter 3...
  • Page 72 Detailed Description The Detailed Picture of Hardware Monitoring Chapter 3...

  • Page 73: Using The Peripheral Status Monitor

    Using the Peripheral Status Monitor This chapter describes the Peripheral Status Monitor, which converts hardware 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 with the PSM •...

  • Page 74: Peripheral Status Monitor Overview

    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,”...

  • Page 75: How Does The Psm Work

    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.

  • Page 76: Figure 4-1 Peripheral Status Monitor

    Using the Peripheral Status Monitor How Does the PSM Work? Figure 4-1 Peripheral Status Monitor Chapter 4...

  • Page 77: Psm Components

    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. •...
  • Page 78 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. To access the man page, type (where monitorname is the executable file listed in the data sheet): man monitorname...

  • Page 79: 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.

  • Page 80: Configuring Package Dependencies Using Sam

    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.

  • Page 81: Configuring Package Dependencies By Editing The Configuration File

    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., cmapplyconf) to specify the use of the PSM Resource Monitor, the section of the package configuration file that has the keyword “RESOURCE_NAME”...

  • Page 82: Creating Ems Monitoring Requests For Psm

    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.

  • Page 83: 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 - <Notify> One of the first steps in creating a monitoring request involves specifying the conditions under which you want to be alerted.

  • Page 84: Setting The Polling Interval -

    • The When value changes condition evaluates to TRUE See the HP OpenView IT/Operations Administrators Task Guide (Part Number B4249-90003) for more information on configuring notification severity. Templates for configuring IT/Operations and Network Node events can be found on the Hewlett-Packard High Availability public web page at http://www.hp.com/go/ha.
  • Page 85 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 "1.3.6.1.4.1.11.2.3.1.7"...

  • Page 86: Adding A Notification Comment -

    Using the Peripheral Status Monitor Monitoring Request Parameters To 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. For an abnormal event, a system logging level of error will be associated with the logged message.

  • Page 87: 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.

  • Page 88: Modifying Monitoring Requests

    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.

  • Page 89: 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 To select individual multiple requests, hold the 2.

  • Page 90: Viewing Monitoring Requests

    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 •...

  • Page 91: 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.
  • Page 92 Using the Peripheral Status Monitor Using the set_fixed Utility to Restore Hardware UP State Chapter 4...

  • Page 93: Hardware Monitor Configuration Files

    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.

  • Page 94: Overview

    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”).

  • Page 95: Client Configuration File

    80, but HP Support may want to see the event when the value is greater than or equal to 70.

  • Page 96: Sample Client Configuration File

    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.
  • Page 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"...
  • Page 98 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_OP:NONE EQ:141:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:150:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:151:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:220:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:221:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:222:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:230:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:231:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:232:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:233:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:300:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:301:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:302:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:310:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:312:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:320:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:322:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:330:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:331:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:400:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:500:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:501:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:502:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:503:CRITICAL:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE Chapter 5...
  • Page 99 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:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:905:MAJOR_WARNING:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE EQ:906:INFORMATION:TRUE:NOT_USED:ANY:1:NONE:NO_OP:NO_OP:NONE Chapter 5...

  • Page 100: Monitor-Specific And Global Configuration Files

    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.

  • Page 101: Table 5-1. Monitor Configuration File Entries

    Web at http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_summ.htm. NOTE An HP-UX man page is available for each monitor. To access the man page, type (where monitorname is the executable file listed in the data sheet): man monitorname Table 5-1 Monitor Configuration File Entries...

  • Page 102: Considerations For Modifying The Monitor Configuration File Settings

    Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files Table 5-1 Monitor Configuration File Entries (Continued) Setting REPEAT_FREQUENCY <frequency> 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.

  • Page 103: Sample Global Configuration File

    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.
  • Page 104 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. cc qq kk ss Data elements equating to event = SCSI Additional Sense Code = SCSI Additional Sense Code Qualifier = SCSI Sense Key...
  • Page 105 [ 30 01 06 -- ] DEFINE_EVENT 100308 INFORMATION [ 3a 00 06 -- ] #--------------------------------------------------------- DEFINE_EVENT 100109 INFORMATION [ 30 00 06 -- ] DEFINE_EVENT 100209 INFORMATION [ 30 02 06 -- ] DT--WR-O-- Cannot read medium - incompatible format. #--------------------------------------------------------- DEFINE_EVENT 100010 INFORMATION [ 30 03 06 -- ] DT-------- Cleaning cartridge installed.
  • Page 106 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files #--------------------------------------------------------- DEFINE_EVENT 100020 INFORMATION [ 3f 03 06 -- ] DTLPWRSOMC Inquiry data has changed. #--------------------------------------------------------- DEFINE_EVENT 100021 INFORMATION [ 2a 00 06 -- ] DTL-WRSOMC Parameters changed. #--------------------------------------------------------- DEFINE_EVENT 100022 INFORMATION [ 2a 01 06 -- ] DTL-WRSOMC Mode parameters changed.
  • Page 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 ecc correction. DEFINE_EVENT 102026 MINOR_WARNING DEFAULT # msg num 33 [ -- -- 01 -- ] #---------------------------------------------------------...
  • Page 108 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files #--------------------------------------------------------- DEFINE_EVENT 100136 CRITICAL [ 12 00 03 -- ] D---W--O-- Address mark not found for id field. DEFINE_EVENT 100236 CRITICAL [ 13 00 03 -- ] D---W--O-- Address mark not found for data field. #--------------------------------------------------------- DEFINE_EVENT 100137 CRITICAL [ 0c 02 03 -- ] D---W--O-- Write error - auto reallocation failed.
  • Page 109 [ 32 00 -- -- ] DEFINE_EVENT 100242 CRITICAL [ 32 01 03 -- ] D---W--O-- Defect list update failure. DEFINE_EVENT 100342 CRITICAL [ 32 02 03 -- ] #--------------------------------------------------------- DEFINE_EVENT 100143 CRITICAL [ 06 00 03 -- ] D---WR-OM- No reference position (like track 0)found. DEFINE_EVENT 100243 CRITICAL [ 14 00 03 -- ] DTL-WRSO-- Recorded entity not found.
  • Page 110 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files [ 4b 00 06 -- ] DTLPWRSOMC Data phase error. #--------------------------------------------------------- DEFINE_EVENT 100053 CRITICAL [ 10 00 04 -- ] D---W--O-- Id crc or ecc error. #--------------------------------------------------------- DEFINE_EVENT 100054 CRITICAL [ 2b 00 06 -- ] DTLPWRSO-C Copy cannot execute; host cannot disconnect. #--------------------------------------------------------- DEFINE_EVENT 100055 CRITICAL [ 11 0a 04 -- ] DT-----O-- Miscorrected error.
  • Page 111 DEFINE_EVENT 100065 CRITICAL [ 09 01 06 -- ] ----WR-O-- Tracking servo failure. #--------------------------------------------------------- DEFINE_EVENT 100166 CRITICAL [ 09 02 06 -- ] ----WR-O-- Focus servo failure. DEFINE_EVENT 100266 CRITICAL [ 09 03 04 -- ] ----WR-O-- Spindle servo failure. #--------------------------------------------------------- DEFINE_EVENT 100067 CRITICAL [ 42 00 06 -- ] D--------- Power-on or self-test failure.
  • Page 112 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files [ 04 00 05 -- ] DEFINE_EVENT 100273 CRITICAL [ 08 00 04 -- ] DTL-WRSOMC Logical unit communication failure. DEFINE_EVENT 100373 CRITICAL [ 41 00 04 -- ] D--------- Data path failure -- should use 40 nn. #--------------------------------------------------------- DEFINE_EVENT 100074 CRITICAL [ 05 00 04 -- ] DTL-WRSOMC Logical unit does not respond to selection.
  • Page 113 DEFINE_EVENT 102476 CRITICAL [ -- -- 05 -- ] DEFINE_EVENT 102576 CRITICAL [ -- -- 09 -- ] DEFINE_EVENT 102676 CRITICAL [ -- -- -- 02 ] #--------------------------------------------------------- DEFINE_EVENT 100077 INFORMATION [ 00 01 06 -- ] -T-------- Filemark detected. #--------------------------------------------------------- DEFINE_EVENT 100078 INFORMATION [ 00 02 06 -- ] -T----S--- End-of-partition/medium detected.
  • Page 114 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files [ 33 00 03 -- ] -T-------- Tape length error. DEFINE_EVENT 100985 CRITICAL [ 50 00 03 -- ] -T-------- Write append error. DEFINE_EVENT 101085 CRITICAL [ 51 00 03 -- ] -T-----O-- Erase failure. DEFINE_EVENT 101185 CRITICAL [ 52 00 03 -- ] -T-------- Cartridge fault.

  • Page 115: Sample Monitor-Specific Configuration File

    #--------------------------------------------------------- DEFINE_EVENT 100095 INFORMATION [ -- -- -- 10 ] #--------------------------------------------------------- DEFINE_EVENT 100096 INFORMATION [ -- -- -- 14 ] #--------------------------------------------------------- DEFINE_EVENT 100097 MAJOR_WARNING DEFAULT # msg num 179 [ -- -- -- 18 ] #--------------------------------------------------------- DEFINE_EVENT 100098 INFORMATION [ -- -- -- 22 ] #--------------------------------------------------------- DEFINE_EVENT 100099 MAJOR_WARNING DEFAULT # msg num 181 [ -- -- -- 28 ]...
  • Page 116 Hardware Monitor Configuration Files Monitor-Specific and Global Configuration Files SEVERITY_ACTION INFORMATION SEVERITY_ACTION MINOR_WARNING SEVERITY_ACTION MAJOR_WARNING SEVERITY_ACTION SERIOUS SEVERITY_ACTION CRITICAL #****************************************************************************# #* cfg-verb event# --severity--- action- ---------description------------- *# #****************************************************************************# DEFINE_EVENT INFORMATION DEFINE_EVENT INFORMATION DEFINE_EVENT INFORMATION DEFINE_EVENT CRITICAL DEFINE_EVENT CRITICAL DEFINE_EVENT CRITICAL DEFINE_EVENT SERIOUS DEFINE_EVENT...

  • Page 117: 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. At startup, following the execution of the IOSCAN utility (performing a real/hard ioscan), or when using the Hardware Monitoring Request Manager (monconfig) to manage monitoring requests, the entries in the startup configuration file are used to create monitoring requests for the monitor.

  • Page 118: Considerations For Modifying The Startup Configuration File Settings

    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.

  • Page 119: Table 5-3. Startup Configuration File Entries

    Table 5-3 Startup Configuration File Entries Keyword Target Type (required) Target Type Modifier (required for the following target types) Target UDP Host - hostname of the machine to which UDP event messages will be sent Target UDP Port - port number on the host that will be used for the network connection Target TCP Host - hostname of the machine to which TCP event messages will be sent Target TCP Port - port number on the host that will be used for the network connection USERLOG...

  • Page 120: Default File Entries

    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 to send all MONITOR: /storage/events/disk_arrays/FW_SCSI Criteria Threshold: INFORMATION events to textlog Criteria Operator: >= Target Type: TEXTLOG...

  • Page 121: 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.

  • Page 122: Considerations For Modifying The Psm Configuration File

    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.

  • Page 123: Table 5-5. Psm Configuration File Fields

    Table 5-5 PSM Configuration File Fields Keyword MONITOR_RESOURCE_NAME (required) PSM_RESOURCE_NAME (Optional) MONITOR_STATE_HANDLING (Optional) Chapter 5 Peripheral Status Monitor (PSM) Configuration File Values Description A valid event Identifies the hardware monitor event monitor to which resource path the entry applies Note: name This must the first keyword in the file.
  • Page 124 Hardware Monitor Configuration Files Peripheral Status Monitor (PSM) Configuration File Table 5-5 PSM Configuration File Fields (Continued) Keyword DOWN_SEVERITY_THRESHOLD (Optional. This value is required if DOWN_SEVERITY_OPERATOR is specified) DOWN_SEVERITY_OPERATOR (Optional) Values Description Valid values Defines the event severity include: level used with DOWN_SEVERITY_OPE CRITICAL RATOR...

  • Page 125: Example File Entries

    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. MONITOR_RESOURCE_NAME: /storage/events/disks/default DOWN_SEVERITY_THRESHOLD:...

  • Page 126: Pushing Ems Hardware Monitors Configuration To Multiple Systems

    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) •...

  • Page 127: Special Procedures

    Special Procedures 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...

  • Page 128: Fibre Channel Arbitrated Loop Hub Monitor

    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.software.hp.com C++ runtime support patches: • 10.20 PHSS_16585 (supersedes PHSS_14262) • 11.00 PHSS_16587 (supersedes PHSS_14577) Before using the hub monitor, edit the monitor configuration file,...

  • Page 129: Initial Monitor Configuration

    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.

  • Page 130: Adding Or Removing An Fc-Al Hub

    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.

  • Page 131: Table 6-1. Psm Configuration File Fields

    • 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.
  • Page 132 Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Table 6-1 PSM Configuration File Fields (Continued) Setting HUB_X_IS_MONITORED value HUB_X_SYSNAME text 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. •...

  • Page 133: 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.

  • Page 134: Adding Or Removing An Fc Switch

    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.

  • Page 135: Configuration Files

    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.

  • Page 136: Table 6-2 Psm Configuration File Fields

    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. Changes that involve adding or deleting switches to the configuration file while the monitor is running will be invoked at the next polling interval, or following the selection of the (E)nable Monitoring option from the Hardware Monitoring Request Manager (monconfig).
  • Page 137 Table 6-2 PSM Configuration File Fields (Continued) Setting SW_X_IS_MONITORED value SW_X_SYSNAME text 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. Chapter 6 Default Value...
  • Page 138 Special Procedures Fibre Channel Switch Monitor Chapter 6...

  • Page 139: Index

    adding event monitoring requests adding PSM monitoring requests asynchronous event detection changing device status checking detailed monitoring status client configuration files configuration files client global modifying modifying PSM modifying startup monitor monitor-specific startup configuration files for hardware monitoring configuring MC/Service Guard package dependencies modifying the configuration file using SAM console notification in EMS...
  • Page 140 Index listing event monitoring requests MC/Service Guard package dependencies memory supported by monitors memory monitor polling modifying configuration files for PSM for startup modifying event monitoring requests modifying PSM monitoring requests monitor configuration files monitor descriptions Fibre Channel Arbitrated Loop Hub Fibre Channel Switch overview of PSM package dependencies...

Table of Contents