System Fault Management Administrator s Guide

Transcription

1 System Fault Management Administrator s Guide HP-UX 11i v2 Edition 3 Manufacturing Part Number: E0609 Copyright 2006 Hewlett-Packard Development Company, L.P.

2 Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. U.S. Government License Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Trademark Notices Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a U.S. registered trademark of Linus Trovalds. Windows is a U.S. registered trademark of Microsoft Corporation. 2

3 Contents About This Document 1. Introduction Overview Features and Benefits Providers Instance Providers Indication Providers User Interfaces HP Systems Insight Manager HP System Management Homepage Architecture on PA-RISC-based Systems Architecture on Itanium-based Systems Installing the SFM Software Prerequisites Installing the SFM Software from the Media Installing Using the TUI Installing Using the CLI Installing the SFM Software from the Web Verifying the Installation Verifying the Installation Using the TUI Verifying the Installation Using the CLI Removing the SFM Software Removing the Software Using the TUI Removing the Software Using the CLI Verifying Removal of the SFM Software Verifying Removal Using the TUI Verifying Removal Using the CLI Configuring Indication Providers Configuring Indication Filters Configuring Error Logging in SFM Configuring the SFMIndicationProvider Creating SFMIndicationProvider Subscriptions

4 Contents 4. Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Creating Subscriptions Viewing Indications Viewing Instances Viewing Information About Processors Viewing Information About Memory Viewing Information About Cooling Devices and Power Supplies Viewing Information About Temperature and Voltage Status Administering Indications and Instances Using HP SMH Viewing Instances Viewing Information About Processors Viewing Information About Cooling Devices Viewing Information About Physical Memory Viewing Information About Power Supplies Viewing Information About Temperature and Voltage Administering Indications Using EVWEB Overview Launching EVWEB for Administration Creating EVWEB Event Subscriptions Modifying EVWEB Event Subscriptions Deleting EVWEB Event Subscriptions Configuring Consumer Viewing Event Subscriptions Overview Viewing EVWEB Event Subscriptions Viewing External Event Subscriptions Administering Throttling Configuration Policy Overview Creating Throttling Configuration Copying and Creating Throttling Configuration Modifying Throttling Configuration Deleting Throttling Configuration Viewing Throttling Configurations Overview

5 Contents Viewing List of Throttling Configurations Viewing Details of a Throttling Configuration Viewing Indications Overview Launching EVWEB for Viewing WBEM Indications Searching WBEM Events Viewing Summary Information About WBEM Events Viewing Detailed Information About WBEM Events Deleting WBEM Events from the Event Archive Viewing Low Level Logs Using Log Viewer Overview Searching Low Level Logs Using Simple Search Searching Low Level Logs Using Advanced Search Viewing List of Low Level Logs Viewing Details of Low Level Logs Tracing EVWEB Overview Enabling Tracing Using EVWEB GUI Enabling Tracing Using EVWEB CLI Modifying Tracing Using EVWEB GUI Modifying Tracing Using EVWEB CLI Disabling Tracing Using EVWEB GUI Disabling Tracing Using EVWEB CLI Troubleshooting SFM Troubleshooting Instance Providers Troubleshooting Indication Providers Troubleshooting EVWEB Glossary Index

6 Contents 6

7 About This Document This document describes how to install, administer, and troubleshoot the System Fault Management (SFM) software and its components. Document updates may be issued between editions to correct errors or to document product changes. To ensure that you receive the updated or new editions, subscribe to the appropriate product support service. Contact your local HP sales representative for more information. This document can also be found online at: Intended Audience This document is intended for system administrators responsible for installing, and managing remote systems using SFM. This document is also intended for users working on the client systems. Administrators and users are expected to have knowledge of operating system concepts, commands, and online diagnostics tools. This document is not a tutorial. Publishing History Table 1 lists the publishing history for this document. Table 1 Publishing History Document Manufacturing Part Number Operating Systems Supported Publication Date i Version 2 September 2006 Document Organization System Fault Management Administrator s Guide is divided into several chapters. Each chapter contains information on installing and administering SFM. Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Introduction Introduces the SFM software, SFM features and benefits, SFM providers, user interfaces, EVWEB, and the architecture of SFM. Installing the SFM Software Instructs how to install, verify, and remove the SFM software. Configuring Indication Providers Instructs how to configure the indication filters, error logging, and the SFMIndicationProvider. Administering Indications and Instances Using HP SIM Describes how to use the HP Systems Insight Manager (HP SIM) GUI to administer indications and view instances on remote systems. Administering Indications and Instances Using HP SMH Describes how to use the HP System Management Homepage (HP SMH) GUI to administer indications and view instances on the local system. 7

8 Chapter 6 Troubleshooting SFM Describes how to troubleshoot SFM providers and EVWEB. Typographic Conventions This document uses the following conventions: audit (5) Book Title KeyCap Emphasis Bold An HP-UX manpage. In this example, audit is the name and 5 is the section in the HP-UX Reference. On the Web and on the Instant Information CD, it may be a link to the manpage itself. From the HP-UX command line, you can enter man audit or man 5 audit to view the manpage. See man (1). The title of a book. On the Web and on the Instant Information CD, it may be a link to the book itself. The name of a keyboard key. Note that Return and Enter both refer to the same key. Text that is emphasized. The defined use of an important word or phrase. ComputerOutput Text displayed or generated by the system. UserInput Command Variable Commands and other text that you type. A command name or qualified command phrase. The name of a variable that you can replace in a command or function or information in a display that represents several possible values. [ ] The contents are optional in formats and command descriptions. If the contents are a list separated by, you can choose one of the items. { } The contents are required in formats and command descriptions. If the contents are a list separated by, you must choose one of the items.... The preceding element can be repeated an arbitrary number of times. Separates items in a list of choices. HP-UX Release Name and Release Identifier Each HP-UX 11i release has an associated release name and release identifier. The uname (1) command with the -r option returns the release identifier. Table 2 shows the releases available for HP-UX 11i. Table 2 HP-UX Releases Release Identifier Release Name Supported Processor Architecture B HP-UX 11i v2.0 Intel Itanium, PA-RISC Related Information Additional information about SFM is available at: Following lists the other documents on SFM: System Fault Management Release Notes System Fault Management Frequently Asked Questions 8

9 System Fault Management Provider Data Sheets HP Welcomes Your Comments HP welcomes your comments concerning this document. We are truly committed to providing documentation that meets your needs. Send your comments or suggestions to: Include the document title, manufacturing part number, and any comment, error found, in this document. Also, please include what we did right, so we can incorporate it into other documents. 9

10 10

11 1 Introduction This chapter introduces you to the System Fault Management (SFM) software and the tools that SFM includes. The chapter discusses the following topics: Chapter 1 11

12 Introduction Overview on page 13 Features and Benefits on page 14 Providers on page 15 User Interfaces on page 21 Architecture on PA-RISC-based Systems on page 22 Architecture on Itanium-based Systems on page Chapter 1

13 Introduction Overview Overview The SFM software is a collection of tools used to monitor the health of HP servers running HP-UX. SFM retrieves information about a system s hardware devices such as CPU, memory, power supply, and cooling devices. SFM operates within the Web-Based Enterprise Management (WBEM) environment. WBEM is an industry-wide standards-based initiative to aid the management of large scale systems. WBEM has the following components: A WBEM infrastructure, such as HP WBEM services. SFM uses the Common Information Model Object Manager (CIMOM) WBEM service to route query requests and responses between WBEM providers and clients. Clients must be compliant with the Common Information Model (CIM) (2.7.2) schema of the Distributed Management Task Force (DMTF). A WBEM-based network management application, such as the HP Systems Insight Manager (HP SIM) and HP System Management Homepage (HP SMH), a user interface for controlling and monitoring resources within a large-scale system. SFM can use HP SIM to display query information for local and remote systems. WBEM providers that obtain information. SFM includes instance and indication providers, which are one set of WBEM providers among many. SFM providers query and provide system hardware property and event information. Chapter 1 13

14 Introduction Features and Benefits Features and Benefits SFM dynamically queries on request property information about a hardware device on a local or remote system. It offers the following features and benefits: Displays information on standards-compliant graphical and command-line system management applications, such as HP SIM and HP SMH. Operates within the WBEM environment. Supports the Central Management Server (CMS) running on HP-UX, Linux, or Windows. Enables you to view and administer WBEM indications. Converts WBEM indications, generated by the SFMIndicationProvider, into Event Monitoring Service (EMS) events to support EMS clients. Provides the same features and benefits as those found in the EMS Hardware Monitors. NOTE SFM is the future replacement of EMS Hardware Monitors. 14 Chapter 1

15 Introduction Providers Providers SFM providers can be classified as instance providers or as indication providers. This section describes these providers. Chapter 1 15

16 Introduction Providers Instance Providers Table 1-1 On request, an SFM instance provider dynamically queries the local or remote system for the property information described in Table 1-1 and reports the information to the CIMOM. Instance Providers Instance Provider CPU Description The CPU Instance Provider gathers the following types of information: Logical processor information, such as: Current clock speed Processor family Processor status information, including configuration and deconfiguration, failure status, and active and inactive status Load percentage Physical processor chip information, such as chip revisions and architecture revisions Location details, such as: Location attributes such as cabinet number, cell number, slot number, and so on. Only information for filled slots is available. Processor IDs The CPU Instance Provider depends on the EMS Wrapper Provider to update the processor inventory. 16 Chapter 1

17 Introduction Providers Table 1-1 Instance Providers (Continued) Instance Provider Memory Description The Memory Instance Provider gathers the following types of information: Memory slot information Memory module information, such as: Serial number Part number Memory capacity Module form factor Module status (for example, configuration status, failure status) The Memory Instance Provider depends on the EMS Wrapper Provider to update the memory inventory. Environmental The Environmental Instance Provider gathers information about the following hardware components: Fans Power supply Bulk power supply AC input lines Filter Metadata (FMD) The FMD Instance Provider does the following: Provides the ability to predefine a filter in a repository Ensures that chosen indications are logged to the Event Archive Creates HP-advised subscriptions when SFM is installed Chapter 1 17

18 Introduction Providers Indication Providers Table 1-2 SFM includes two indication providers, the EMS Wrapper Provider and the SFMIndicationProvider. The SFMIndicationProvider is available on Itanium-based systems only. Table 1-2 describes the SFM indication providers. Indication Providers Indication Provider EMS Wrapper Provider Description The EMS Wrapper Provider does the following: 1. Converts hardware events generated by the EMS Hardware Monitors into WBEM indications. 2. Reports the WBEM indications to the CIMOM. Using a WBEM-based management application, such as HP SIM, you can subscribe to and receive Event Monitoring Service (EMS) events generated on a remote system. On the system on which SFM is installed, you can use an SFM tool, called EVWEB, to view and administer events through the HP SMH interface. 18 Chapter 1

19 Introduction Providers Table 1-2 Indication Providers (Continued) Indication Provider SFMIndicationProvider Description The SFMIndicationProvider generates indications that are compliant with the WBEM standards. It replaces the following EMS monitors: cmc_em cpe_em memory_ia64 You can choose either the SFMIndicationProvider or these three EMS monitors. The remaining EMS monitors continue to function as usual irrespective of whether you choose the SFMIndicationProvider or the EMS monitors that it replaces. If you choose the SFMIndicationProvider, it does the following: 1. Generates WBEM indications when it detects the following on a system: Corrected Machine Check (CMC) errors Corrected Platform Errors (CPE) Memory-related errors 2. Reports these WBEM indications to the CIMOM. Chapter 1 19

20 Introduction Providers The SFMIndicationProvider is a standards-based solution that works independent of the EMS framework. The WBEM indications generated by the SFMIndicationProvider may contain additional data that are not present in the EMS event details. The WBEM indications can be reported to the EMS clients through the EMS framework. NOTE The following apply to indication providers: The terms events and indications are used interchangeably. The SFMIndicationProvider is introduced in the June 2006 release on HP-UX 11i v2. Releases prior to the June 2006 release do not include this indication provider. 20 Chapter 1

21 Introduction User Interfaces User Interfaces You can use two types of interfaces to view SFM provider queries: HP SIM and HP SMH. This section describes these interfaces. HP Systems Insight Manager HP SIM is a WBEM-based user interface for controlling and monitoring resources within a large-scale system. You can use HP SIM to create subscriptions and to view indications and instances on a remote system. You must install HP SIM on the CMS. You can use HP SIM to launch HP SMH. HP System Management Homepage HP SMH is a secure, Web-based management application. You must install HP SMH on a local system to view hardware configuration, status data, performance metrics, system thresholds, and software version control information. You can also launch HP SMH from HP SIM remotely. Chapter 1 21

22 Introduction Architecture on PA-RISC-based Systems Architecture on PA-RISC-based Systems Figure 1-1 illustrates the architecture of SFM installed on a PA-RISC-based client system. The client system is managed by the CMS. Figure 1-1 Block Diagram of SFM on PA-RISC-Systems The following list describes the sequence of events when a request is made for information: 1. The CIMOM receives requests from the CMS for device information. 2. The CIMOM converts the requests to a format that is deciphered by the SFM providers and directs the requests to the appropriate SFM provider, for example, the CPU Instance Provider. 3. The SFM provider queries the associated hardware device for property information. 4. The SFM provider returns the query information to the CIMOM. 5. The CIMOM conveys the responses from the provider to the CMS. 22 Chapter 1

23 Introduction Architecture on PA-RISC-based Systems Information can be viewed using HP SIM on the remote system and HP SMH on the local system. The following list describes the sequence of events when an event is generated from an EMS monitor: 1. The EMS Wrapper Provider receives events generated by the EMS monitors through the EMS framework. 2. The provider converts these events into WBEM indications and reports these indications to the CIMOM. 3. The CIMOM directs these indications to EVWEB and to the CMS that has created subscriptions for indications. EVWEB then stores the indications either in the Event Archive or in your box, or both, depending on your configuration. Indications can be viewed using HP SIM on the remote system and HP SMH on the local system. Chapter 1 23

24 Introduction Architecture on Itanium-based Systems Architecture on Itanium-based Systems Figure 1-2 illustrates the architecture of SFM installed on a Itanium-based client system. Figure 1-2 Block Diagram of SFM on Itanium-based Systems The sequence of events when a request is made for information of a managed resource is as follows: 1. The CIMOM receives requests from the CMS for device information. 24 Chapter 1

25 Introduction Architecture on Itanium-based Systems 2. The CIMOM converts the requests to a format that is deciphered by the SFM providers and directs the requests to the appropriate SFM provider, for example, the CPU Instance Provider. 3. The SFM provider queries the associated hardware device for property information. 4. The SFM provider returns the query information to the CIMOM. 5. The CIMOM conveys the responses from the provider to the CMS. Information can be viewed using HP SIM on the remote system and HP SMH on the local system. The sequence of events when an event is generated from an EMS monitor is as follows: 1. The EMS Wrapper Provider receives events generated by the EMS monitors through the EMS framework. 2. The provider converts these events into WBEM indications and reports these indications to the CIMOM. 3. The CIMOM directs these indications to EVWEB and to the CMS that has created subscriptions for indications. EVWEB then stores the indications either in the Event Archive or in your box, or both, depending on your configuration. Indications can be viewed using HP SIM on the remote system and HP SMH on the local system. The sequence of events if you choose to use the SFMIndicationProvider instead of the EMS monitors it substitutes, is as follows: 1. The SFMIndicationProvider generates WBEM indications that are triggered by CMC errors, CPE, and memory-related errors on the system. 2. The provider reports these WBEM indications to the CIMOM. 3. The CIMOM directs these indications to EVWEB and to the CMS that has created subscriptions for indications. EVWEB then stores the indications either in the Event Archive or in your box, or both, depending on your configuration. Indications can be viewed using HP SIM on the remote system and HP SMH on the local system. Chapter 1 25

26 Introduction Architecture on Itanium-based Systems 4. The indications generated by the SFMIndicationProvider, and reported to the CIMOM, can also be directed to the EMS framework through the WBEM Wrapper Monitor. The WBEM Wrapper Monitor converts the WBEM indications into EMS events and directs them to the EMS framework. EMS clients can receive these events, along with the other events generated by the EMS monitors, through the EMS framework. NOTE Only those indications that are generated by the SFMIndicationProvider can be directed to the EMS framework through the WBEM Wrapper Monitor. Indications generated by the EMS Wrapper Provider cannot be directed to the EMS framework. 26 Chapter 1

27 2 Installing the SFM Software The System Fault Management (SFM) software is installed by default with the HP-UX 11i v2 Operating Environment (OE) media. However, at some point you may need to install the SFM software separately. This chapter describes how to install the SFM software as a standalone Chapter 2 27

28 Installing the SFM Software component on the HP-UX 11i v2 operating system. This chapter discusses the following topics: Prerequisites on page 29 Installing the SFM Software from the Media on page 30 Installing the SFM Software from the Web on page 35 Verifying the Installation on page 36 Removing the SFM Software on page 39 Verifying Removal of the SFM Software on page Chapter 2

29 Installing the SFM Software Prerequisites Prerequisites Following are the prerequisites for installing the June 2006 version of SFM software: March 2006 HP-UX 11i v2 Operating Environment Update Release (OEUR) or later OpenSSL Version A e.012 or later WBEM Services Version A or later SysMgmtWeb Version A (HP-UX Web-Based System Management User Interface) PHKL_32653 (diag 2) kernel patch Online Diagnostics (OnlineDiag bundle) Table 1-1 lists the versions of Online Diagnostics that support the SFM software. All later versions of Online Diagnostics will support the SFM software in the future. Table 2-1 Online Diagnostics Versions Platform EMS Version STM Version PA-RISC A C Itanium A C NOTE All the prerequisites are available on the OE media. You can select the SFM dependencies from the OE media while installing the SFM software as a standalone component. The OnlineDiag bundle is always installed with the OE media. Installing a kernel patch may require a system reboot. HP recommends that you install HP Systems Insight Manager (HP SIM) version to remotely administer indications and instances. Chapter 2 29

30 Installing the SFM Software Installing the SFM Software from the Media Installing the SFM Software from the Media This section describes the two ways in which you can install the SFM software from the HP-UX 11i V2 OE media: Using the terminal user interface (TUI) Using the command-line interface (CLI) Installing Using the TUI To install the SFM software using the TUI, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Mount the CD to a location of your choice as in the following example: # mount /dev/dsk/c1t2d0 /tmp/cdrom Step 3. Enter the following command at the HP-UX prompt: # swinstall The SD Install - Software Selection window appears as shown in the following figure: Step 4. In the Specify Source window, select the appropriate location and click OK. The SD Install - Software Selection window is displayed. Step 5. In the SD Install - Software Selection window, select Options-> Autoselect dependencies when marking software. 30 Chapter 2

31 Installing the SFM Software Installing the SFM Software from the Media Step 6. Select Enforce dependency analysis errors in agent, and click OK, as shown in the following figure. The Note window is displayed. Selecting these options automatically installs all the dependencies. NOTE The system selects some options by default. However, you must select the two options mentioned in step 5 to automatically install the prerequisites. Step 7. Click OK in the Note window to confirm the selection of dependencies. Step 8. In the SD Install - Software Selection window, select Actions->Install to begin installation, as shown in the following figure: Chapter 2 31

32 Installing the SFM Software Installing the SFM Software from the Media NOTE SFM is automatically configured after it is installed. The following figure displays the beginning of the configuration phase: 32 Chapter 2

33 Installing the SFM Software Installing the SFM Software from the Media When the SFM software installs, the Install window appears indicating that the SFM software is installed successfully, as shown in the following figure: Step 9. Unmount the CD. To unmount, enter the following command at the HP-UX prompt: # unmount /tmp/cdrom Step 10. To verify whether the SFM software is installed properly, enter the following command at the HP-UX prompt: # swlist grep SysFaultMgmt If the SFM software is installed properly, SysFaultMgmt and the version number of the SFM software are displayed in the output. If the SFM software is not installed properly, you must repeat the installation procedure. For more information, see Verifying the Installation on page 36. Installing Using the CLI To install the SFM software using CLI, complete the following steps: Step 1. Log in to the system as a superuser. Chapter 2 33

34 Installing the SFM Software Installing the SFM Software from the Media Step 2. Mount the CD to a location of your choice, as in the following example: # mount /dev/dsk/c1t2d0 /tmp/cdrom Step 3. To install the SFM software and all the dependencies, enter the following command at the HP-UX prompt: # swinstall -x autoselect_dependencies=true -x enforce_dependencies=true -s /tmp/cdrom SysFaultMgmt Step 4. Unmount the CD. To unmount, enter the following command at the HP-UX prompt: # unmount /tmp/cdrom Step 5. To verify whether the SFM software is installed properly, enter the following command at the HP-UX prompt: # swlist grep SysFaultMgmt If the SFM software is installed properly, SysFaultMgmt and the version number of the SFM software appear in the output. If the SFM software is not installed properly, you must repeat the installation procedure. For more information, see Verifying the Installation on page Chapter 2

35 Installing the SFM Software Installing the SFM Software from the Web Installing the SFM Software from the Web To install the SFM software from the Software Depot, complete the following steps: Step 1. Go to HP Software Depot at: Step 2. Search for SysFaultMgmt. The Overview page is displayed. Step 3. Go to the Installation page and review Prerequisites to ensure that your system meets the requirements. Step 4. Select the Receive for Free >> option at the bottom right of the page. Step 5. Select the appropriate release of the HP-UX operating system. Step 6. Enter your registration information. Read and accept the terms and conditions. Step 7. Click Next >> at the bottom right of the page. Step 8. Click the appropriate link under Download Software to download the software. Save the software in a local directory on your system, for example, /tmp/sysfaultmgmt.depot. Step 9. To install the product, login as superuser and enter the following command: # swinstall -s <full path of depot> SysFaultMgmt For example, # swinstall -s /tmp/sysfaultmgmt.depot SysFaultMgmt Step 10. To verify whether the SFM software is installed properly, enter the following command at the HP-UX prompt: # swlist grep SysFaultMgmt If the SFM software is installed properly, SysFaultMgmt and the version number appear in the output. If the SFM software is not installed properly, you must repeat the installation procedure. For more information, see Verifying the Installation on page 36. Chapter 2 35

36 Installing the SFM Software Verifying the Installation Verifying the Installation This section describes how to verify the SFM software installation using the TUI and the CLI. Verifying the Installation Using the TUI To verify the SFM software installation, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Click Logfile in the Install window, as shown in the following figure: The Logfile, which includes details about the installation, is displayed. If there are no errors in the Logfile, the SFM software is installed properly. If the SFM software is not installed properly, you must repeat the installation procedure. Step 3. For information about errors related to installation, enter the following command at the HP-UX prompt: # swjob -a log <system name>:/ 36 Chapter 2

37 Installing the SFM Software Verifying the Installation The jobid is available in the Logfile, as underlined in the Logfile window, in the following figure: For example, enter the following command at the HP-UX prompt: # swjob -a log iemlhamia.india.hp.com:/ Verifying the Installation Using the CLI To verify your installation using the CLI, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Enter the following command at the HP-UX prompt: # swjob If the output contains no errors, the SFM software is installed properly. Otherwise, you must install the SFM software again. Chapter 2 37

38 Installing the SFM Software Verifying the Installation A sample output is shown in the following figure: Step 3. For information about installation-related errors, enter the following command at the HP-UX prompt: # swjob -a log <system name>:/ For example, enter the following command at the HP-UX prompt: # swjob -a log iemlhamia.india.hp.com:/ 38 Chapter 2

39 Installing the SFM Software Removing the SFM Software Removing the SFM Software This section describes how to remove of the SFM software using the TUI and the CLI. CAUTION Removing the SFM software makes your system vulnerable to failure. Also, all the software products that depend on the SFM software may not work properly. Removing the Software Using the TUI To remove the SFM software from your system, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Enter the following command at the HP-UX prompt: # swremove Chapter 2 39

40 Installing the SFM Software Removing the SFM Software Step 3. Select SysFaultMgmt in the SD Remove window, as shown in the following figure: 40 Chapter 2

41 Installing the SFM Software Removing the SFM Software Step 4. Select Actions->Mark for Remove in the SD Remove window, as shown in the following figure: Chapter 2 41

42 Installing the SFM Software Removing the SFM Software Step 5. Select Actions->Remove, as shown in the following figure: 42 Chapter 2

43 Installing the SFM Software Removing the SFM Software Step 6. Click OK in the Remove Analysis window to confirm the removal of the SFM software, as shown in the following figure: Chapter 2 43

44 Installing the SFM Software Removing the SFM Software The following figure is a sample of the removal process in progress: 44 Chapter 2

45 Installing the SFM Software Removing the SFM Software Step 7. When the SFM software is removed, the Remove Window is displayed, as shown in the following figure: Step 8. To verify whether the SFM software is removed properly, enter the following command at the HP-UX prompt: # swlist grep SysFaultMgmt If the SFM software is removed properly, SysFaultMgmt and the version number of the SFM software does not appear in the output. If the SFM software is not removed properly, you must repeat the removal procedure. For more information, see Verifying Removal of the SFM Software on page 47. Removing the Software Using the CLI To remove the SFM software from your system, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Enter the following command at the HP-UX command prompt: Chapter 2 45

46 Installing the SFM Software Removing the SFM Software # swremove SysFaultMgmt Step 3. To verify whether the SFM software is removed properly, enter the following command at the HP-UX prompt: # swlist grep SysFaultMgmt If the SFM software is removed properly, SysFaultMgmt and the version number of the SFM software do not appear in the output. If the SFM software is not removed properly, you must repeat the removal procedure. For more information, see Verifying Removal of the SFM Software on page Chapter 2

47 Installing the SFM Software Verifying Removal of the SFM Software Verifying Removal of the SFM Software This section describes how to use the TUI and the CLI to verify whether the SFM software is removed successfully. Verifying Removal Using the TUI To verify whether the SFM software is removed successfully, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Click Logfile in the Remove Window. If there are no errors in the Logfile, the SFM software is removed successfully. If the SFM software is not removed properly, you must repeat the removal procedure. See Removing the SFM Software on page 39 for instructions on how to remove the SFM software. Step 3. For information about errors related to the removal of SFM, enter the following command at the HP-UX prompt: # swjob -a log <system name>:/ The jobid is available in the Logfile. Verifying Removal Using the CLI To verify if the SFM software is removed successfully, complete the following steps: Step 1. Log in to the system as a superuser. Step 2. Enter the following command at the HP-UX prompt: # swjob If the output contains no errors, the SFM software is removed successfully. If the SFM software is not removed properly, you must repeat the removal procedure. See Removing the SFM Software on page 39 for instructions on how to remove the SFM software. Step 3. For information about errors related to the removal of the SFM software, enter the following command at the HP-UX prompt: Chapter 2 47

48 Installing the SFM Software Verifying Removal of the SFM Software # swjob -a log <system name>:/ The jobid is available in the output of the swjob command. 48 Chapter 2

49 3 Configuring Indication Providers This chapter describes how to configure indication filters, error logging, and the SFMIndicationProvider. Chapter 3 49

50 Configuring Indication Providers Configuring Indication Filters Configuring Indication Filters You must configure the indication filters to view desired indications. You use the Filter Metadata Provider (FMD) to configure indication filters that deliver important or desired indications, for example, indications with a certain severity. The provider also ensures that all the indications that HP recommends for system management are logged in the Event Archive, available at /var/opt/sfmdb/pgsql. Logging indications in the archive helps track all the events that are generated. Filters are classified as follows: HP-Defined Filters HP-Defined filters are defined by HP, and are present in the FMD repository at the time of installation. You can enable or disable HP-Defined filters. To enable HP-Defined filters, enter the following command at the HP-UX prompt: # sfmconfig -m enable To disable HP-Defined filters, enter the following command at the HP-UX prompt: # sfmconfig -m disable Indications fulfilling the conditions in the HP-Known HP-Defined filters are logged in the Event Archive. These subscriptions ensure that all the indications recommended by HP for system management are logged in the Event Archive. Admin-Defined Filters Admin-Defined filters are defined by the administrator. HP does not provide any Admin-Defined filter. To create, delete, modify, enable, and disable Admin-Defined filters, you must use the sfmconfig command. By default, the FMD Provider does not log indications fulfilling the conditions in the Admin-Defined filters, in the Event Archive. You must modify the Admin-Defined filters to log indications in the Event Archive. For more information about the sfmconfig command and its options, enter the following command at the HP-UX prompt: 50 Chapter 3

51 Configuring Indication Providers Configuring Indication Filters # man sfmconfig Chapter 3 51

52 Configuring Indication Providers Configuring Error Logging in SFM Configuring Error Logging in SFM You can configure error logging parameters, such as severity, location of logs, and the number of backup files by using the sfmconfig command. To configure these parameters, complete the following steps: Step 1. Modify the /opt/sfm/conf/fmloggerconfig.xml configuration file using a text editor. Step 2. For the changes made in the /opt/sfm/conf/fmloggerconfig.xml configuration file to take effect, enter the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -c /opt/sfm/conf/fmloggerconfig.xml For more information about the sfmconfig command, enter the following command at the HP-UX prompt: # man sfmconfig NOTE You can configure the parameters by using the command-line interface (CLI) only. 52 Chapter 3

53 Configuring Indication Providers Configuring the SFMIndicationProvider Configuring the SFMIndicationProvider This section describes how to configure the SFMIndicationProvider. It also describes how to switch between the SFMIndicationProvider and the EMS Hardware Monitors. The SFMIndicationProvider operates independent of the EMS framework, and generates WBEM indications if it detects any abnormal activity on the resources it manages. To switch from the cpe_em, cmc_em, and memory_ia64 monitors to the SFMIndicationProvider, enter the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -w -s The following output on the terminal that was used to start the CIMOM indicates that the SFMIndicationProvider has successfully replaced the three EMS Hardware Monitors: Disabling EMS hardware monitors and enabling SysFaultMgmt. This may take a few minutes. SysFaultMgmt will now monitor the devices & EMS hardware monitors will be shutdown. To check whether the SFMIndicationProvider is working properly, send a test event by entering the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -t -m The following output indicates that the SFMIndicationProvider is working properly: Sending test event for memory monitor. NOTE You can also send test events for other devices that the SFMIndicationProvider monitors. For information on the devices monitored by the SFMIndicationProvider, see Table 1-2 on page 18. To view the list of events, enter the following command at the HP-UX prompt: # /opt/sfm/bin/evweb eventviewer -L Chapter 3 53

54 Configuring Indication Providers Configuring the SFMIndicationProvider A list of events along with the details such as event number, severity, and event category are displayed. To view the details of an event, enter the following command at the HP-UX prompt: # /opt/sfm/bin/evweb eventviewer -E -n <event number> The details of the specified event such as the summary, description, probable cause, and recommended actions for the error are displayed. To switch back from the SFMIndicationProvider to the three EMS Hardware Monitors, enter the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -w -e The following output on the terminal that was used to start the CIMOM indicates that the three EMS Hardware Monitors have successfully replaced the SFMIndicationProvider: Enabling EMS hardware monitors and disabling SysFaultMgmt. This may take a few minutes. SysFaultMgmt will no longer monitor the devices & EMS hardware monitors will be enabled. Creating SFMIndicationProvider Subscriptions Table 3-1 The SFMIndicationProvider uses the default Event Qualification (EQ) entries for generating events. To view the default EQ entries, enter the following command at the HP-UX prompt: # /opt/sfm/bin/evweb subscribe -T -g default -l You cannot modify or delete the default EQ entries. However, you can create custom subscriptions to receive required indications. Table 3-1 describes the EQ entries and their values. Event Qualification for the SFMIndicationProvider Entry Description Available Values event_number A unique number assigned to each event of a monitor. You can use any number. If no entry matches the event number, use OTHER. 54 Chapter 3

55 Configuring Indication Providers Configuring the SFMIndicationProvider Table 3-1 Event Qualification for the SFMIndicationProvider (Continued) Entry Description Available Values device_catego ry severity enable flag suppression time time window The monitored resource. The severity of the event. Switch to enable or disable an event. Time to suppress the generation of an event, in minutes. Threshold value of events, in minutes. If an error is detected for a duration longer than that specified in this field, an event is generated. processor memory backbone SEVERITY_FATAL_NONREC OVERABLE SEVERITY_CRITICAL SEVERITY_MINOR SEVERITY_DEGRADED_WAR NING SEVERITY_INFORMATION TRUE - enables an event. FALSE - disables an event. NOT_USED - never suppress an event. 1 - maxint - duration of suppression in minutes Generates an event only once. NOT_USED - threshold value not used. ANY - time window threshold used, but no time window is specified. 1 - maxint - Chapter 3 55

56 Configuring Indication Providers Configuring the SFMIndicationProvider Table 3-1 Event Qualification for the SFMIndicationProvider (Continued) Entry Description Available Values threshold value threshold X, operator X Number of times an error must be detected in the time window to qualify as an event. Value threshold is a case-sensitive condition. It can denote percentage in some cases. For example, percentage of the Page Dellocation Table (PDT) full. Operator denotes conditions to qualify value threshold. Value threshold and operator collectively represent an equation. 1 - maxint NOTE: To generate an event every time an error is detected, you must set the threshold value to 1, and the time window to ANY. Value threshold categories: NONE - value threshold is not used. Any positive value. Operator values: NO_OP - operator is not used. >, <, >=, <=, ==,!= For example, if the percentage of PDT required to qualify an event is between 60 and 70, enter the following: 60:<=:<=70 To create a new subscription with custom EQ criteria, make a copy of the default event configuration file and edit the contents of the file using a text editor. To enter a comment, begin the line with the # character. Following are the conditions for creating custom subscriptions: 1. Every custom setting must begin with EQ. 2. Any two EQ entries must be separated by a colon. 3. Only the available values for EQ entries must be used. 4. All EQ entries for a custom setting must be in the same line. Carriage returns are not allowed. 56 Chapter 3

57 Configuring Indication Providers Configuring the SFMIndicationProvider 5. EQ entries must be case sensitive. Example: In the following default configuration file for memory, event 3000 is suppressed: # EV_SBE_DETECTED (Single bit error detected) EQ:memory:3000:SEVERITY_INFORMATION:FALSE:NOT_USED:ANY:1:NON E:NO_OP:NO_OP_NONE To receive all indications related to single bit errors occurring on the DIMMs, make a copy of the default event configuration file and edit the appropriate line using a text editor, as follows: # EV_SBE_DETECTED (Single bit error detected) EQ:memory:3000:SEVERITY_INFORMATION:TRUE:NOT_USED:ANY:1:NONE :NO_OP:NO_OP:NONE To subscribe to indications based on the custom subscription, enter the following command at the HP-UX prompt: # /opt/sfm/bin/evweb subscribe -T -c -g <subscription_name> -p /opt/sfm/data/<modified_file> To modify a custom subscription, enter the following command at the HP-UX prompt: # /opt/sfm/bin/evweb subscribe -T -m -g <subscription_name> -p /opt/sfm/data/<modified_file2> To create, modify, and delete custom subscriptions using the GUI, see Administering Throttling Configuration Policy on page 110. For information on the SFMIndicationProvider, see Indication Providers on page 18. NOTE The SFMIndicationProvider is available on Itanium-based systems only. Chapter 3 57

58 Configuring Indication Providers Configuring the SFMIndicationProvider 58 Chapter 3

59 4 Administering Indications and Instances Using HP SIM This chapter describes System Fault Management (SFM) administration on a remote system using HP Systems Insight Manager (HP SIM). Chapter 4 59

60 Administering Indications and Instances Using HP SIM NOTE You can perform similar tasks using other management applications that are compliant with the Common Information Model (CIM) (2.7.2) schema of the Distributed Management Task Force (DMTF). The terms events and indications are used interchangeably in this document. This chapter addresses the following topics: Creating Subscriptions and Viewing Indications Using HP SIM on page 61 Viewing Instances on page Chapter 4

61 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM To view instances and events generated on a managed system, you must create subscriptions. When you create subscriptions on the Central Management Server (CMS) using HP SIM, indications are delivered to the CMS whenever an event occurs on the managed system. This section discusses the following topics: Creating Subscriptions on page 61 Viewing Indications on page 72 Creating Subscriptions To create subscriptions using HP SIM, complete the following steps: Step 1. Enter the following URL to launch HP SIM on your browser: name>:<port number>/ The system name is the name of the CMS. For example: The HP SIM home page is launched. Step 2. To create subscriptions, select Options-->Protocol Settings-->Global Protocol Settings in the HP SIM Home page, as shown in Figure 4-1. Chapter 4 61