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

62 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-1 HP SIM Home Page The Global Protocol Settings window is displayed, as shown in Figure Chapter 4

63 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-2 Global Protocol Settings Step 3. In Figure 4-2, under Default WBEM settings, select Enable WBEM. Click OK to save your settings. Step 4. Select Configure->Configure or Repair Agents, as shown in Figure 4-3. Chapter 4 63

64 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-3 Configuration The Configure or Repair Agents window is displayed, as shown in Figure Chapter 4

65 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-4 Configure or Repair Agents Step 5. From the Add targets by selecting from: list in Figure 3-4, select All Systems to view and select the systems. Selecting the name of the system enables you to view indications occurring on the selected system. The list of systems is displayed in the Select Target Systems window, as shown in Figure 4-5. Chapter 4 65

66 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-5 Select Target Systems Step 6. To select all the systems in the network, select the Select All Systems itself check box, as shown in Figure 4-5. Click Apply. The Verify Target Systems window is displayed, as shown in Figure Chapter 4

67 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-6 Verify Target Systems Step 7. Select the appropriate check box to verify the target systems and click Next, as shown in Figure 4-6. The Enter Credentials window is displayed, as shown in Figure 4-7. Chapter 4 67

68 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-7 Enter Credentials Step 8. Enter your credentials in the given fields, as shown in Figure 4-7. Click Next. The Configure or Repair Settings window is displayed, as shown in Figure Chapter 4

69 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-8 Configure or Repair Settings Step 9. On the Configure or Repair Settings window, click Run Now. The Task Results window is displayed, as shown in Figure 4-9. The Task Results window states that the Indication Subscription is successfully created. The next time an event is generated on the selected system, you can view the event in the events list. Chapter 4 69

70 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-9 Task Results Step 10. To obtain a printable report of the indication subscription details, click View Printable Report. The report is displayed, as shown in Figure Chapter 4

71 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-10 Printable Report of the Indication Subscription NOTE For more information, see the HP Systems Insight Manager Installation and User s Guide at: Chapter 4 71

72 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Viewing Indications To view the list of events generated on the selected systems, complete the following steps: Step 1. Select All Events in the left pane of the HP SIM window. The list of events is displayed, as shown in Figure Chapter 4

73 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-11 Events list Step 2. To view the details of an event, select the event. The details are displayed at the bottom of the same window, as shown in Figure Chapter 4 73

74 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-12 Event Details Step 3. To obtain the printable version of the event details, click View Printable Details at the bottom of the window. The printable report is displayed in a new window, as shown in Figure Chapter 4

75 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Figure 4-13 Printable Event Details Table 4-1 To create subscriptions and view indications using the CLI, see Creating Event Subscription Using CLI on page 93. The ProviderName in the Event Details window indicates the monitor that generated the event. Table 4-1 maps the monitors and providers. Representation of Monitors Monitor Provider cmc_em CMC_IndicationProviderIA Chapter 4 75

76 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Table 4-1 Representation of Monitors (Continued) Monitor Provider cpe_em dm_core_hw dm_chassis dm_memory disk_em fpl_em ia64_corehw lpmc_em memory_ia64 CPE_IndicationProviderIA CoreHardwareIndicationProvid erpa ChassisIndicationProviderPA MemoryIndicationProviderPA DiskIndicationProvider FPL_IndicationProvider CoreHardwareIndicationProvid eria LPMC_IndicationProviderPA MemoryIndicationProviderIA Table 4-2 compares the EMS Hardware Monitors properties with the equivalent EMS Wrapper Provider properties. Table 4-2 Property Representation EMS Hardware Monitors Event Time Severity Event System Summary Description of Error Probable Cause/ Recommended Action System Serial Number EMS Wrapper Provider EventTime PerceivedSeverity EventID SystemName Summary Description ProbableCauseDescription and RecommendedAction (these two are separate fields) SystemSerialNumber 76 Chapter 4

77 Administering Indications and Instances Using HP SIM Creating Subscriptions and Viewing Indications Using HP SIM Table 4-2 Property Representation (Continued) EMS Hardware Monitors InquiryVendorID Physical Device Path InquiryProductID PhysicalDevicePath EMS Wrapper Provider HWManufacturer HWLogicalLocation DeviceModel DeviceControllerLogicalLocat ion NOTE For more information, see the HP Systems Insight Manager Installation and User s Guide at: Chapter 4 77

78 Administering Indications and Instances Using HP SIM Viewing Instances Viewing Instances This section describes the tasks you must perform to view instances. This section discusses the following topics: Viewing Information About Processors on page 78 Viewing Information About Memory on page 80 Viewing Information About Cooling Devices and Power Supplies on page 80 Viewing Information About Temperature and Voltage Status on page 83 Viewing Information About Processors To obtain information about processors using the CPU Instance Provider, complete the following steps: Step 1. On the System Page of HP SIM, click Properties, as shown in Figure 4-14 on page Chapter 4

79 Administering Indications and Instances Using HP SIM Viewing Instances Figure 4-14 System Page The Properties window is displayed. This window provides details about the system. Step 2. To view information about the processor status, click the Status tab. Step 3. To view information about the status of the processors on the system, select Processor(s). Step 4. To view information about the processor configuration, click the Configuration tab. The Configuration window is displayed. Step 5. To view information about the configuration of the processors, select Processor(s). Chapter 4 79

80 Administering Indications and Instances Using HP SIM Viewing Instances NOTE There is no CLI to view information about processors. For more information, see the HP Systems Insight Manager Installation and User s Guide at: Viewing Information About Memory To obtain information about memory using the Memory Instance Provider, complete the following steps: Step 1. On the System Page of HP SIM, select Properties, as shown in Figure 4-14 on page 79. The Properties window is displayed. This window provides details about the system. Step 2. To view information about the memory status, click the Status tab. The Status window is displayed. Step 3. To view information about the status of the physical memory, select Physical Memory. Step 4. To view information about the memory configuration, click the Configuration tab. The Configuration window is displayed. Step 5. To view information about the configuration of the physical memory, select Physical Memory. NOTE There is no CLI to view information about memory. For more information, see the HP Systems Insight Manager Installation and User s Guide at: Viewing Information About Cooling Devices and Power Supplies This section discusses the following topics: 80 Chapter 4

81 Administering Indications and Instances Using HP SIM Viewing Instances Viewing Cooling Device Instances on page 81 Viewing Power Supply Instances on page 82 Viewing Cooling Device Instances To view information about the cooling devices on the system, complete the following steps: Step 1. On the System Page, select System Management Homepage, as shown in Figure 4-15 on page 81. Figure 4-15 System Page Chapter 4 81

82 Administering Indications and Instances Using HP SIM Viewing Instances Step 2. Select Home->System->Cooling under System Status Summary. Information about cooling devices on the system such as the status, location, and the type of fans is displayed in the Cooling Status window. Step 3. To return to the System Management Homepage home, select Home at the top of the window. NOTE There is no CLI to view information about cooling devices. For more information, see the HP Systems Insight Manager Installation and User s Guide at: Viewing Power Supply Instances To view information about the power supplies, complete the following steps: Step 1. On the System Page, select System Management Homepage, as shown in Figure 4-15 on page 81. Step 2. Select Home->System->Power under System Status Summary on the System Management Homepage. Information about the power status is displayed in the Power Status window. Step 3. To return to the System Management Homepage home, select Home at the top of the window. NOTE There is no CLI to view information about power supplies. For more information, see the HP Systems Insight Manager Installation and User s Guide posted at: 82 Chapter 4

83 Administering Indications and Instances Using HP SIM Viewing Instances Viewing Information About Temperature and Voltage Status This section discusses the following topics: Viewing the Temperature Status on page 83 Viewing Voltage Status on page 83 Viewing the Temperature Status To view the temperature status of the system, complete the following steps: Step 1. Select 2 items not shown under System on the System Management Homepage. The system page is displayed. Step 2. To view the temperature status of the system, select Temperature on the system page. The temperature status of the system is displayed in the Temperature Status window. Step 3. To return to the System Management Homepage home, select Home at the top of the window. NOTE There is no CLI to view information about the temperature status. For more information, see the HP Systems Insight Manager Installation and User s Guide at: Viewing Voltage Status To view the voltage status of the system, complete the following steps: Step 1. Select 2 items not shown under System on the System Management Homepage. Step 2. Select Voltage on the system page. Chapter 4 83

84 Administering Indications and Instances Using HP SIM Viewing Instances The voltage status of the system is displayed in the Voltage Status window. Step 3. To return to the System Management Homepage home, select Home at the top of the window. NOTE There is no CLI to view information about the voltage status. For more information, see the HP Systems Insight Manager Installation and User s Guide at: 84 Chapter 4

85 5 Administering Indications and Instances Using HP SMH This chapter describes the SFM administration tasks that you can perform using HP SMH on a local system. Chapter 5 85

86 Administering Indications and Instances Using HP SMH This chapter discusses the following topics: Viewing Instances on page 87 Administering Indications Using EVWEB on page 90 Viewing Event Subscriptions on page 103 Administering Throttling Configuration Policy on page 110 Viewing Indications on page 121 Viewing Low Level Logs Using Log Viewer on page 129 Tracing EVWEB on page Chapter 5

87 Administering Indications and Instances Using HP SMH Viewing Instances Viewing Instances This section describes the tasks you must perform to view instances. This section discusses the following topics: Viewing Information About Processors on page 87 Viewing Information About Cooling Devices on page 88 Viewing Information About Physical Memory on page 88 Viewing Information About Power Supplies on page 88 Viewing Information About Temperature and Voltage on page 89 Viewing Information About Processors To obtain information about processors using the CPU Instance Provider, complete the following steps: Step 1. On the HP System Management Homepage (SMH), under System, select Processors, as shown in Figure 5-1. Figure 5-1 System Management Homepage Chapter 5 87

88 Administering Indications and Instances Using HP SMH Viewing Instances Information about processors is displayed. Step 2. Select Home to return to HP SMH. Viewing Information About Cooling Devices To obtain information about cooling devices using the Environmental Provider, complete the following steps: Step 1. On HP SMH (Figure 5-1), under System, select Cooling. Information about cooling devices is displayed. Step 2. Select Home to return to HP SMH. Viewing Information About Physical Memory To obtain information about the physical memory using the Memory Provider, complete the following steps: Step 1. On HP SMH (Figure 5-1), under System, select Physical Memory. Information about physical memory is displayed. Step 2. Select Home to return to HP SMH. Viewing Information About Power Supplies To obtain information about the power supplies using the Environmental Provider, complete the following steps: Step 1. On HP SMH (Figure 5-1), under System, select Power. Information about power supplies is displayed. Step 2. Select Home to return to HP SMH. 88 Chapter 5

89 Administering Indications and Instances Using HP SMH Viewing Instances Viewing Information About Temperature and Voltage To obtain information about the temperature and voltage using the Environmental Provider, complete the following steps: Step 1. On HP SMH(Figure 5-1), under System, select...2 items not shown. You will see the System page displayed. Step 2. To view voltage status, Under System, select Voltage. Information about voltage is displayed. Step 3. To view temperature status, Under System, select Temperature. Information about temperature is displayed. Step 4. Select Home to return to HP SMH. Chapter 5 89

90 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB Administering Indications Using EVWEB This section describes how to use EVWEB for administrative tasks, such as creating and managing subscriptions for indications. This section discusses the following topics: Overview on page 90 Launching EVWEB for Administration on page 91 Creating EVWEB Event Subscriptions on page 92 Modifying EVWEB Event Subscriptions on page 95 Deleting EVWEB Event Subscriptions on page 99 Configuring Consumer on page 101 NOTE You must be an administrator to create, modify, and delete event subscriptions. Overview SFM includes a user component called EVWEB, which enables you to administer and view WBEM indications generated on the local system on which SFM is installed. EVWEB includes the following components: Event Subscription Administration to subscribe to indications Event Viewer to view indications present in the Event Archive Indication Consumer for Event Archive to store indications in the Event Archive Indication Consumer for to send indications to your address Event Archive database to include indications you have subscribed to 90 Chapter 5

91 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB EVWEB provides the following user interfaces to create and manage event subscriptions and view indications: Browser-based Graphical User Interface (GUI) Command-Line Interface (CLI) EVWEB supports the following user groups: Administrator Non-administrator In the CLI, any user with root privileges is an administrator. However, in the HP SMH GUI, the user groups in EVWEB are mapped to the user groups defined in HP SMH. The Administrator user group in HP SMH maps to administrators in EVWEB. The Operator and the User user group in HP SMH map to non-administrators in EVWEB. NOTE For information on how to configure user groups in HP SMH, see the HP System Management Homepage User s Guide at: Launching EVWEB for Administration You can launch EVWEB either through the CLI or through the HP SMH GUI. To launch EVWEB using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe To use HP SMH GUI to launch EVWEB for administering event subscription, complete the following steps: Step 1. Log in to HP SMH. To log in to HP SMH, enter in the address bar of the Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Chapter 5 91

92 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Select Tools in the main menu. The Tools page is displayed. This page displays the applications that are plugged into HP SMH. Step 5. Select Subscription Administration in Evweb box. The Event Subscription Administration page is displayed. You can perform various administrative tasks such as creating, modifying, and deleting event subscriptions on this page. Creating EVWEB Event Subscriptions You can create event subscriptions for the WBEM indications you are interested in monitoring. You can create the following types of event subscriptions using EVWEB: Admin Defined event subscriptions Event Subscriptions created using the sfmconfig command are called Admin Defined event subscriptions. You can modify and delete Admin Defined event subscriptions using the sfmconfig command. You cannot use the evweb list, evweb subscribe, or the evweb eventviewer command to create and delete Admin Defined event subscriptions. Event subscriptions created using the HP SMH GUI (Event Subscription Administration) You can create these event subscriptions using the GUI or the CLI. You can modify and delete the event subscriptions that are created using Event Subscription Administration. To create an event subscription using Event Subscription Administration, you must specify the following: A unique name for the event subscription Criteria such as device, event ID, and the severity of the event The location where the event must be stored You can create an event subscription using the following methods: Create a completely new event subscription. 92 Chapter 5

93 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB Copy an existing event subscription and modify it. Creating an Event Subscription Using GUI To create a new event subscription, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Create subscription in the action pane on the top right corner of the page. The Create Subscription page is displayed. Step 3. Provide appropriate information in the fields present in the Create Subscription page. NOTE It is mandatory to specify a unique name for creating an event subscription. Step 4. To view the command line equivalent of creating event subscriptions using GUI, click Preview on the Create Subscription page. This step is optional. Step 5. Select Create on the Create Subscription page. EVWEB creates the event subscription and displays a confirmation message. Step 6. Click OK on the confirmation message window. For more information on creating subscription using the HP SMH GUI, select Help on the action pane of the Create Subscription page. Creating Event Subscription Using CLI To create an event subscription using CLI, enter the following command at the HP-UX prompt: # evweb subscribe -C -n <subscription name> -v <comma\ separated event category names> Where: -C is an option used to create event subscriptions. Chapter 5 93

94 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB -n is a switch used to specify a name for an event. -v is a switch used to specify the category of an event. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. NOTE The -n and the -v switches are mandatory. You can also use the following switches with the -C option: (-e [eq\ne\le\ge\bw] [:] <severity level1>[,<severity level2>]) (-v <comma separated event category names>) (-i <comma separated EventID>) (-t (archive\ ) [<handler properties>]) -r -g <throttling configuration name> For more information on creating event subscriptions using CLI, see evweb_subscribe (1). Copying and Creating a New Event Subscription Using GUI You can reuse the existing subscriptions for creating a new subscription. To create a new event subscription by copying an existing event subscription, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select the event subscription you want to copy, from the event subscription table. Step 3. Select Copy and create subscription in the action pane on the top right corner of the page. The Copy and create subscription page is displayed. Step 4. Modify the required fields. 94 Chapter 5

95 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB IMPORTANT The subscription criteria is not copied when you copy an HP Advised event subscription. Therefore, ensure that you specify the subscription criteria in the Copy and Create Subscription page. Step 5. Select Create. EVWEB creates the event subscription and displays a confirmation message. Step 6. Click OK on the confirmation message window. NOTE There is no CLI equivalent of this action. The Copy and create subscription feature is available only on GUI. For more information on creating an event subscription by copying an existing event subscription using the GUI, select Help on the action pane of the Copy and Create Subscription page. Modifying EVWEB Event Subscriptions You can modify an event subscription by modifying the criteria and location. However, the fields that you are allowed to modify depend on the type of event subscription you select. You can modify more than one subscription at a time. NOTE The HP Known event subscriptions are classified as HP Advised and Admin Defined. In HP Advised event subscriptions, the events are stored in the event archive by default. The default location of the events cannot be modified. However, you can direct the events to your address. You cannot change any other subscription criteria. Chapter 5 95

96 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB In Admin Defined event subscriptions, the events are stored in the event archive by default. The default location of the events can be modified. You can store events in the event archive, direct them to your address, or do both. You cannot change any other subscription criteria. In event subscriptions created through EVWEB, you can change all criteria except the subscription name. You can modify an event subscription in the following ways: Modify a single event subscription. You can modify a single event subscription using the modify feature by selecting the event subscription from the event subscription table. Modify similar criteria in multiple event subscriptions. You can modify similar criteria in multiple event subscriptions by using the Copy and Modify subscription feature. Modifying an Event Subscription Using GUI To modify an event subscription, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Modify subscription in the action pane on the top right corner of the page. The Modify subscription page is displayed. Step 3. Select the event subscription, which you want to modify, from the event subscription table. Step 4. Modify the required fields. Step 5. To view the command line equivalent of modifying event subscriptions using GUI, click Preview on the Modify subscription page. This step is optional. Step 6. Select Modify in the Modify subscription page. EVWEB modifies the event subscription and displays a confirmation message. Step 7. Click OK on the confirmation message window. 96 Chapter 5

97 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB For more information on modifying an event subscription using the HP SMH GUI, select Help on the action pane of the Modify Event Subscription page. Modifying an Event Subscription Using CLI To modify an event subscription using CLI, enter the following command at the HP-UX prompt: # evweb subscribe -M -n <subscription name> -v <event category names> -t < address> Where: -M is an option used to modify event subscriptions. -n is a switch used to specify a name for an event. -v is a switch used to specify the category of an event. -t is a switch used to specify the location ( address or Event Archive) of an event. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. NOTE The -n switch is mandatory. You can also use the following switches with the -M option: (-e [eq\ne\le\ge\bw] [:] <severity level1>[,<severity level2>]) (-v <event category names>) (-i <EventID>) (-t (archive\ ) [<handler properties>]) -r -g <throttling configuration name> To modify an event subscription, you must specify the criteria and the location. Following are the ways in which you can modify an event subscription: Chapter 5 97

98 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB If you do not specify the -r option and the location, the current location is retained and the subscription criteria are updated. If you specify the -r option but not the location, the current location is removed and only the subscription criteria is updated. If you specify both subscription criteria and location, both of them are updated. If you specify the location but not the criteria, the location is updated but the original criteria is retained. For more information on creating event subscriptions using the CLI, see evweb_subscribe (1). Copying and Modifying an Event Subscription Using GUI To modify an event subscription by copying an existing event subscription, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select the event subscriptions you want to copy, from the event subscription table. The copy and modify subscription page is displayed. Step 3. Select the event subscriptions you want to modify by selecting the respective check boxes. Step 4. Select Copy and modify subscription in the action pane on the top right corner of the page. The Copy and modify subscription page is displayed. Step 5. Modify the required fields. Step 6. Select Modify in the Copy and modify subscription page. EVWEB modifies the event subscriptions and displays a confirmation message. Step 7. Click OK on the confirmation message window. 98 Chapter 5

99 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB NOTE There is no CLI equivalent of this action. The Copy and modify subscription feature is available only on GUI. IMPORTANT The subscription criteria is not copied when you copy an HP Advised event subscription. Therefore, make sure that you specify the subscription criteria in the Copy and modify subscription page. For more information on copying and modifying an event subscription using the HP SMH GUI, select Help on the action pane of the Copy and Modify Event Subscription page. Deleting EVWEB Event Subscriptions You must periodically delete event subscriptions that are not required. You can delete a single event subscription or multiple event subscriptions at a time. Deleting an Event Subscription Using GUI To delete an event subscription, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Delete subscription in the action pane on the top right corner of the page. The Delete subscriptions page is displayed. Step 3. Select the event subscriptions you want to delete, by selecting the appropriate check boxes. Step 4. Select Delete in the Delete subscription page. The event subscriptions are deleted and a confirmation message is displayed. Step 5. Click OK on the confirmation message window. Chapter 5 99

100 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB NOTE You cannot delete HP Advised event subscriptions and Admin Defined event subscriptions. For more information on deleting an event subscription using the HP SMH GUI, select Help on the action pane of the Delete Event Subscription page. NOTE HP recommends deleting all unwanted event subscriptions. Retaining a large number of event subscriptions may increase the size of the archive, and may affect the tasks you perform using Event Subscriptions Administration. Deleting an Event Subscription Using CLI To delete an event subscription using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe -D -f -n <subscription name> NOTE The -n switch is mandatory. Where: -D is an option used to delete event subscriptions. -n is a switch used to specify a name for an event. -f is a switch used to force the command. This switch can be used only with the -D option. If the -f switch is not used, EVWEB prompts for a confirmation before deleting an event subscription. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. NOTE Using CLI, you can delete only one event subscription at a time. 100 Chapter 5

101 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB For more information on deleting event subscriptions using the CLI, see evweb_subscribe (1). Configuring Consumer The Consumer is a component of EVWEB that receives indications from the WBEM Services, and redirects them to an SMTP server. Normally, the local system itself is the server. In such cases, you need not configure the Consumer. If the server is not on the local system, you must configure the Consumer. To configure the Consumer, complete the following steps: Step 1. Open the /opt/sfm/conf/evweb.conf file on the system. Step 2. Change the IP address, FULLNAME, and the FROMADDR (From Address) of the host and save the file. The IP address is the address of the server. The FULLNAME refers to the complete name of the server. The FROMADDR refers to address that sends the event notifications. Following is a sample evweb.conf file with IP address, FULLNAME, and the FROMADDR configured: <EVWEB> <CONSUMER> < CONSUMER> < SERVER> <IP> </IP> <FULLNAME> localhost </FULLNAME> </ SERVER> <FROMADDR> [email protected] </FROMADDR> Chapter 5 101

102 Administering Indications and Instances Using HP SMH Administering Indications Using EVWEB </ CONSUMER> </CONSUMER> </EVWEB> Step 3. Enter the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -c /opt/sfm/conf/evweb.conf The following message is displayed at the HP-UX prompt: loaded the control provider The Consumer is successfully configured. 102 Chapter 5

103 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions Viewing Event Subscriptions This section describes how to perform non-administration tasks, such as viewing event subscriptions. This section discusses the following topics: Overview on page 103 Viewing EVWEB Event Subscriptions on page 103 Viewing External Event Subscriptions on page 107 Overview You can view HP Known event subscriptions and event subscriptions that are created using EVWEB. You can also view event subscriptions that are created using tools other than EVWEB (referred to as external subscriptions). HP Known event subscriptions are created by default during the installation of the SysFaultMgmt bundle. HP Known event subscriptions are also created by administrators using the /opt/sfm/bin/sfmconfig command. HP provides some event subscriptions with EVWEB. These event subscriptions are known as HP Advised event subscriptions. By default, the HP Advised event subscriptions store the events in the Event Archive. Viewing EVWEB Event Subscriptions You can view summary and detailed information about event subscriptions using EVWEB. Viewing Summary of an EVWEB Event Subscription Using GUI To view summary of the event subscriptions, repeat steps 1-5 from Launching EVWEB for Administration on page 91. The Event Subscription Administration page is displayed. Chapter 5 103

104 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions The Event Subscription Administration page displays summary of the the event subscriptions. The summary information is tabulated. In this chapter, the tale is referred to as Event Subscription Summary table. For more information on viewing the summary of an EVWEB event subscription using the HP SMH GUI, select Help on the action pane of the Event Subscription page. Viewing Summary of an EVWEB Event Subscription Using CLI To view the summary of an EVWEB event subscription using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe -L -b internal Where: -L is an option used to list all the event subscriptions. -b is a switch used to display information about event subscriptions in brief. internal is an argument used to display information about HP Known event subscriptions and event subscriptions created using EVWEB. A summary of event subscriptions is displayed in a tabular format, as shown in Figure 5-2. Figure 5-2 Summary of EVWEB Event Subscriptions Table 5-1 describes the various fields in the Event Subscription Summary table. Table 5-1 EVWEB Event Subscriptions Field Subscription Name Description Displays the name of an event subscription. 104 Chapter 5

105 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions Table 5-1 Field HP Known Is Depricated Event Archive EVWEB Event Subscriptions Description Displays TRUE if the subscription is HP Known. Displays FALSE if the subscription is not HP Known. Displays TRUE if the subscription is depreciated. Displays FALSE if the subscription is not depreciated. This field is applicable to HP Advised subscriptions only. Displays TRUE if the subscription criterion is configured to store the WBEM indications in the Event Archive. Displays FALSE if the subscription criterion is not configured to store the WBEM indications in the Event Archive. Displays TRUE if the subscription criterion is configured to send an to the specified address, when a WBEM indication is generated. Displays FALSE if the subscription is not configured to send an . For information on viewing the summary of EVWEB event subscriptions using the CLI, see evweb_subscribe (1). Viewing Details of an Event Subscription Using GUI To view details of an event subscription, complete the following steps: Chapter 5 105

106 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. The Event Subscription Administration page displays the event subscription table. Step 2. Select the event subscription from the event subscription table. The details of the event subscription is displayed at the end of the event subscription table. For more information on viewing the details of an EVWEB event subscription using the HP SMH GUI, select Help on the action pane of the Event Subscription page. Viewing Details of an Event Subscription Using CLI To view the details of an EVWEB event subscription using CLI, enter the following command at the HP-UX prompt: # evweb subscribe -E -n <subscription name> Where: -E is an option used to display details of an event subscription. -n is a switch used to specify the name of an event subscription. A table with detailed information about event subscriptions is displayed, as shown in Figure 5-3. Figure 5-3 Details of an Event Subscription 106 Chapter 5

107 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions Table 5-2 describes the various fields in the Details of an Event Subscription page. Table 5-2 Details of an Event Subscriptions Field Subscription Name Throttling Config Name Subscription Criteria Subscription Destination Description Displays the name of an event subscription. Displays the name of the throttling configuration that is associated with the subscription. Displays the criteria that are specified for the subscription. For example, Severity, Event Id, Event Category, Device, and so on. Displays the destination location where the WBEM indications are stored. For example, Event Archive, address. Viewing External Event Subscriptions Event subscriptions created by tools and interfaces other than EVWEB are called external event subscriptions. This section describes how to view external event subscriptions using EVWEB. Viewing External Event Subscriptions Using GUI To view external event subscriptions, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. The Event Subscription Administration page displays the event subscription table. Step 2. Select View external subscription in the action pane on the top right corner of the page. Chapter 5 107

108 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions The View external subscriptions page is displayed. For more information on viewing external event subscription using the HP SMH GUI, select Help on the action pane of the View External Event Subscription page. Viewing External Event Subscriptions Using CLI To view the summary of an EVWEB event subscription using CLI, enter the following command at the HP-UX prompt: # evweb subscribe -L -b external Where: -L is an option used to list all the event subscriptions. -b is a switch used to display information about event subscriptions in brief. external is an argument used to display information about external event subscriptions. A list of event subscriptions is displayed in a tabular format, as shown in Figure 5-4. Figure 5-4 External Event Subscriptions The field names of the external event subscriptions are different from the ones created using EVWEB. However, field names of both external event subscriptions and subscriptions created using EVWEB, can be matched. Table 5-3 describes the various fields in the View external subscriptions page. Table 5-3 External Event Subscriptions Field Filter Name Handler Name Description Displays the name of an event subscription. 108 Chapter 5

109 Administering Indications and Instances Using HP SMH Viewing Event Subscriptions Table 5-3 Destination URL Query Field External Event Subscriptions Description Displays the destination location where the indications are stored. Displays the subscription criteria. For information on viewing external subscriptions using the CLI, see evweb_subscribe (1). Chapter 5 109

110 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Administering Throttling Configuration Policy This section describes how to use EVWEB for administrative tasks, such as creating and managing throttling configuration policies. This section discusses the following topics: Overview on page 110 Creating Throttling Configuration on page 110 Copying and Creating Throttling Configuration on page 112 Modifying Throttling Configuration on page 114 Deleting Throttling Configuration on page 115 Overview Throttling configuration is a feature that enables you to administer a throttling policy. The throttling policy contains various parameters that can be configured. Based on the throttling configuration and event subscriptions, you receive alerts for events generated on a single managed system. A throttling policy can be associated with more than one subscription. However, one subscription cannot be associated with more than one throttling policy. The throttling policy and a subscription can be created independent of each other. For more information on throttling policy, see Table 3-1 on page 54. NOTE The Throttling configuration administration feature is available only on Integrity servers. This feature is not available on HP 9000 servers. Creating Throttling Configuration You can create a throttling configuration policy and associate it with an event subscription. The HP Advised subscriptions are associated with the default throttling configuration policy defined by HP. 110 Chapter 5

111 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Creating a Throttling Configuration Using GUI To create a throttling configuration, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. Step 3. Select Create throttling config in the action pane on the top right corner of the page. The Create throttling config page is displayed. Step 4. Provide appropriate information in the fields present in the Create throttling config page. NOTE The throttling configuration name must be unique. The throttling policy file name must contain the absolute path of the file and the throttling configuration policy strings. Step 5. To view the command line equivalent of creating throttling configuration using GUI, click Preview on the Create throttling config page. This step is optional. Step 6. Select Create on the Create throttling page. EVWEB creates the throttling configuration and displays a confirmation message. Step 7. Click OK on the confirmation message window. For more information on creating a throttling configuration using the HP SMH GUI, select Help on the action pane of the Create throttling config page. Creating a Throttling Configuration Using CLI To create an throttling configuration using CLI, enter the following command at the HP-UX prompt: Chapter 5 111

112 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy # evweb subscribe -T -c -g <throttling configuration name>\ -p<throttling configuration policy file name> Where: -T is an option used to administer a throttling configuration. -c is a switch used to create a throttling configuration. -g is a switch used to specify a name for the throttling configuration. -p is a switch used to specify the path to the throttling configuration policy file. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. You can also use the following switches with the -T option: (-l) (-s <throttling configuration description>) NOTE The -g switch is mandatory with the -c, -m, -d, and the -l switches. The -p switch is mandatory if you use the -c switch. For more information on creating throttling configuration using CLI, see evweb_subscribe (1). Copying and Creating Throttling Configuration You can copy an existing throttling configuration and create a throttling configuration. By default, the description and the throttling policy of the existing throttling configuration is copied to the new throttling configuration. You can specify a new throttling policy while copying and creating a throttling configuration. Copying and Creating a Throttling Configuration Using GUI To copy an existing throttling configuration to create a throttling configuration, complete the following steps: 112 Chapter 5

113 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. Step 3. Select Copy and create throttling config in the action pane on the top right corner of the page. The Copy and create throttling config page is displayed. Step 4. Select the throttling configuration you want to copy, from the Throttling Configuration Summary Table. Step 5. Provide appropriate information in the fields present in the Copy and create throttling config page. NOTE The throttling configuration name must be unique. The throttling policy file name must contain the absolute path of the file and the throttling configuration policy strings. Step 6. Select Create on the Copy and create throttling config page. EVWEB creates the throttling configuration and displays a confirmation message. Step 7. Click OK on the confirmation message window. NOTE There is no CLI equivalent of this action. The Copy and create throttling configuration feature is available only on GUI. For more information on copying and creating a throttling configuration using the HP SMH GUI, select Help on the action pane of the Copy and create throttling config page. Chapter 5 113

114 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Modifying Throttling Configuration You can modify a throttling configuration by modifying the criteria in the Modify Throttling Config page. However, the fields that you are allowed to modify depend on the type of throttling configuration you select. You cannot modify HP Known throttling configurations. In all other throttling configurations, you cannot modify the name of the throttling configuration. Modifying a Throttling Configuration Using GUI To modify a throttling configuration, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. Step 3. Select Modify throttling config in the action pane on the top right corner of the page. The Modify Throttling Config page is displayed. Step 4. Modify the required fields. NOTE You cannot modify the name of the throttling configuration. Step 5. Select Modify on the Modify Throttling Config page. EVWEB modifies the throttling configuration and displays a confirmation message. Step 6. Click OK on the confirmation message window. For more information on modifying a throttling configuration using the HP SMH GUI, select Help on the action pane of the Modify Throttling Config page. 114 Chapter 5

115 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Modifying a Throttling Configuration Using CLI To modify a throttling configuration using CLI, enter the following command at the HP-UX prompt: # evweb subscribe -T -m -g <throttling configuration name>\ -p <throttling configuration policy file name> -s\ <throttling configuration description> Where: -T is an option used to administer a throttling configuration. -m is a switch used to modify the throttling configuration. -g is a switch used to specify the name of a throttling configuration that you want to modify. -p is a switch used to specify the path to the throttling configuration policy file. -s is a switch used to provide description for a throttling configuration. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. NOTE The -g switch is mandatory with the -m switch. You can also use the following switches with the -T option: (-l) -h For more information on modifying a throttling configuration using the CLI, see evweb_subscribe (1). Deleting Throttling Configuration You must periodically delete throttling configurations that are not required. You can delete a single throttling configuration or multiple throttling configurations at a time. Chapter 5 115

116 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy Deleting a Throttling Configuration Using GUI To delete a throttling configuration, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. Step 3. Select Delete throttling config in the action pane on the top right corner of the page. The Delete Throttling Config page is displayed. Step 4. Select the throttling configurations you want to delete, by selecting the appropriate check boxes. Step 5. Select Delete on the Delete Throttling Config page. The throttling configurations are deleted and a confirmation message is displayed. NOTE You cannot delete HP Known throttling configurations. As a result, the HP Known throttling configurations are not displayed in the Delete Throttling Config page. Step 6. Click OK on the confirmation message window. For more information on deleting a throttling configuration using the HP SMH GUI, select Help on the action pane of the Delete Throttling Config page. Deleting a Throttling Configuration Using CLI To delete a throttling configuration using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe -T -d -g <throttling configuration name> Where: 116 Chapter 5

117 Administering Indications and Instances Using HP SMH Administering Throttling Configuration Policy -T is an option used to administer a throttling configuration. -d is a switch used to delete a throttling configuration. -g is a switch used to specify the name of a throttling configuration that you want to modify. NOTE The -g switch is mandatory with the -d switch. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. For more information on deleting a throttling configuration using the CLI, see evweb_subscribe (1). Chapter 5 117

118 Administering Indications and Instances Using HP SMH Viewing Throttling Configurations Viewing Throttling Configurations This section describes how to perform administration tasks related to viewing throttling configurations using EVWEB. This section discusses the following topics: Overview on page 118 Viewing List of Throttling Configurations on page 118 Viewing Details of a Throttling Configuration on page 119 NOTE The Throttling configuration administration feature is available only on Integrity servers. This feature is not available on HP 9000 servers. Overview The Event Subscription Administration enables you to manage throttling configurations on a local HP-UX system. The Manage throttling configuration page displays a list of throttling configuration in a tabular format. In this document, this table is referred to as Throttling Configuration Summary Table. The Throttling Configuration Summary Table includes the name of the throttling configuration, the description, and the type of throttling configuration. HP Known throttling configuration cannot be modified or deleted. The information in the Throttling Configuration Summary Table is listed in alphabetical order of the Throttling Config Name. Click on the column heading to toggle sort order. You can sort one column at one time. To view the detailed information about the throttling configuration, click on the desired throttling configuration and scroll down. Viewing List of Throttling Configurations You can view summary information of a list of throttling configuration using EVWEB. 118 Chapter 5

119 Administering Indications and Instances Using HP SMH Viewing Throttling Configurations Viewing List of Throttling Configuration Using GUI To view list of throttling configuration, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. This page displays list of throttling configuration. Viewing a List of Throttling Configuration Using CLI To view a list of throttling configuration using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe -T Where: -T is an option used to administer a throttling configuration. For more information on viewing a list of throttling configuration using the CLI, see evweb_subscribe (1). Viewing Details of a Throttling Configuration The Manage throttling configuration page displays detailed information about a throttling configuration. Viewing Details of a Throttling Configuration Using GUI To view details of a throttling configuration, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Administration on page 91. Step 2. Select Manage Throttling Configurations in the action pane on the top right corner of the page. The Manage throttling configuration page is displayed. Step 3. Select the throttling configuration from Throttling Configuration Summary Table. Chapter 5 119

120 Administering Indications and Instances Using HP SMH Viewing Throttling Configurations The details of the throttling configuration appear at the end of Throttling Configuration Summary Table. For more information on viewing the details of a throttling configuration using the HP SMH GUI, select Help on the action pane of the Manage throttling config page. Viewing Details of a Throttling Configuration Using CLI To view details of a throttling configuration using the CLI, enter the following command at the HP-UX prompt: # evweb subscribe -T -l -g <throttling configuration name> Where: -T is an option used to administer a throttling configuration. -l is a switch used to view details of a throttling configuration. -g is a switch used to specify the name of a throttling configuration that you want to modify. NOTE The -g switch is mandatory with the -l switch. A message stating that the execution of the evweb subscribe command was successful is displayed on the screen. For more information on viewing details of a throttling configuration using the CLI, see evweb_subscribe (1). 120 Chapter 5

121 Administering Indications and Instances Using HP SMH Viewing Indications Viewing Indications This section describes how to perform non-administration tasks related to viewing WBEM indications using EVWEB. This section discusses the following topics: Overview on page 121 Launching EVWEB for Viewing WBEM Indications on page 123 Searching WBEM Events on page 123 Viewing Summary Information About WBEM Events on page 125 Viewing Detailed Information About WBEM Events on page 126 Deleting WBEM Events from the Event Archive on page 127 NOTE EVWEB enables both administrators and non-administrators to search and view WBEM events. However, only administrators can delete WBEM events. Overview The Event Viewer enables you to view, search, and delete WBEM events that are present in the Event Archive. It also enables you to view detailed and summary information of WBEM events. You can also search for WBEM events stored in the Event Archive using the quick search and advanced search features. To enhance search results, the Event Archive is divided into Current and History Event Archive. By default, the Current Event Archive contains the latest events that are generated on an HP-UX 11i v2 system. The events stored in the Current Event Archive are automatically moved to the History Event Archive based on the following parameters, which ever occurs first: The events are older than 10 days. The page size of the Current Event Archive is greater than 100. Chapter 5 121

122 Administering Indications and Instances Using HP SMH Viewing Indications Events older than 365 days are purged from the History Event Archive. This results in a phased elimination of old events. However, these parameters are configurable. To change the settings, the administrator must configure the /opt/sfm/conf/dbconfig.xml and the /opt/sfm/data/dbinternalconfig.xml policy files. The new settings are effective when a cron job is executed subsequent to these changes. Following is a part of the /opt/sfm/conf/dbconfig.xml policy file: The maximum page size is 400, and each page can have 70 records of 4 Kb each. The DBRecordLifeTime indicates the threshold time in days. The maximum threshold time is 10 days. The error logs are in the Current Event Archive for 10 days. The ArchedRecordLifetime is also measured in days and is set to 365 days (one year). It specifies that the WBEM events are stored in the History Event Archive for one year. The modifications in the DBConfig.xml file is effective when the cron job runs subsequent to the changes. Following is a part of the /opt/sfm/data/dbinternalconfig.xml policy file: <SFMConfig> <EvwebDBConfig> <PageSize>100</PageSize> <DBRecordLifeTime>10</DBRecordLifeTime> <ArchedRecordLifetime>365</ArchedRecordLifetime> </EvwebDBConfig> </SFMConfig> <SFMConfig> <EvwebDBInternalConfig> <InternalTimePeriodForJob>0.25</InternalTimePeriodForJob> <IntervalForArchivingJobExecution>2</Interval- ForArchivingJobExecution> </EvwebDBInternalConfig> </SFMConfig> 122 Chapter 5

123 Administering Indications and Instances Using HP SMH Viewing Indications The IntervalForArchivingJobExecution is measured in days. This parameter indicates the time interval within which a cron job for archiving the events is executed. The InternalTimePeriodForJob is also measured in days. HP recommends that you do not modify InternalTimePeriodForJob. The modifications made to the IntervalForArchivingJobExecution tag is effective when the cron job runs subsequent to the changes. Launching EVWEB for Viewing WBEM Indications You can launch EVWEB either through the CLI or the GUI. To Launch EVWEB using the CLI, enter the following command at the HP-UX prompt: # evweb <eventviewer list> To Launch EVWEB for viewing WBEM indications using the HP SMH GUI, complete the following steps: Step 1. Log in to the System Management Homepage. To log in to HP SMH, enter in the address bar of the Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Select Logs in the main menu. The Logs page is displayed. This page displays various applications that are plugged into HP SMH. Step 5. Select Event Viewer in Evweb box. The Event Viewer page is displayed. You can view and delete WBEM indications using the Event Viewer. Searching WBEM Events You can search for WBEM events that are stored in the Event Archive using either the GUI or the CLI. Chapter 5 123

124 Administering Indications and Instances Using HP SMH Viewing Indications Searching WBEM Events Using GUI The Event Viewer GUI provides quick search and advanced search options to search for WBEM events. To do a quick search of WBEM events, based on the severity of the event, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Viewing WBEM Indications on page 123. Step 2. Select Critical to search for critical events. Similarly, select Major, Minor, Warning, Information, Other, Normal, or Unknown to search for the respective WBEM events. Step 3. To view all events, select All Events. For more information on performing a quick search of WBEM events using the HP SMH GUI, select Help on the action pane of the List Events page. To perform an advanced search of WBEM events, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Viewing WBEM Indications on page 123. Step 2. Select Advanced Search on the right pane of the Event Viewer page. The Advanced Search page is displayed. Step 3. Provide appropriate information in the text boxes and fields present in the Advanced Search page. Step 4. Click Search on the Advanced Search page. Based on the search criteria, the WBEM events are displayed in a tabular format in the Event Viewer page. For more information on searching for WBEM events using GUI, select Help on the action pane of the Advanced Search page. Searching WBEM Events Using CLI To search WBEM events using the CLI, enter the following command at the HP-UX prompt: # evweb eventviewer -L 124 Chapter 5

125 Administering Indications and Instances Using HP SMH Viewing Indications Where: -L is an option used to list all the WBEM event. A list of WBEM events is displayed on the screen. You can also use the following switches with the -L option: -e [eq\ne\le\ge\bw] [:] <severity level1>[,<severity level2>] -v <event category names> -i <EventID> -r[is\be\en\co][:](<string to be searched>) -a(<number for age>(:)(yy\mm\dd\hh) -t[eq\le\ge\bw] (<mm:dd:yyyy:hh:mi:ss>)[,<mm:dd:yyyy:hh:mi:ss>] -s[asc\desc] (<summary list column name>) -o(<offset number>) -c(<count of events>) For information on searching WBEM events, using the CLI, see evweb_eventviewer (1). Viewing Summary Information About WBEM Events You can view summary information about events stored in the Event Archive database. Viewing Summary Information Using GUI To view summary information about WBEM events, repeat steps 1-5 from Launching EVWEB for Viewing WBEM Indications on page 123. The List Events page is displayed. The List Event tables displays summary information about WBEM events that are stored in the event archive. For more information on viewing summary information of WBEM events using GUI, select Help on the action pane of the List Events page. Viewing Summary Information Using CLI To search WBEM events using the CLI, enter the following command at the HP-UX prompt: Chapter 5 125

126 Administering Indications and Instances Using HP SMH Viewing Indications # evweb eventviewer -L Where: -L is an option used to list all the WBEM events. A list of WBEM events is displayed on the screen. Viewing Detailed Information About WBEM Events You can view the details of an WBEM event using EVWEB. The details of an event appear at the end of the List Events table only when you select an event from the List Events table. Viewing Detailed Information Using GUI To view detailed information about WBEM events, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Viewing WBEM Indications on page 123. Step 2. Select the desired WBEM event in the List Events table. The Details of the Event page is displayed. This includes a table that details the WBEM events. For information on viewing detailed information of WBEM events using GUI, select Help on the action pane of the List Events page. Viewing Detailed Information Using CLI To view detailed information on WBEM events using the CLI, enter the following command at the HP-UX prompt: # evweb eventviewer -E -n <event ID> Where: -L is an option used to list all the WBEM events. -n is a switch used specify the event ID of the WBEM event. The screen displays detailed information about the WBEM events. For information on viewing detailed information of WBEM events using the CLI, see evweb_eventviewer (1). 126 Chapter 5

127 Administering Indications and Instances Using HP SMH Viewing Indications Deleting WBEM Events from the Event Archive You can delete a single event or multiple events at a time. Deleting an Event Using GUI To delete an event, complete the following steps: Step 1. Repeat steps 1-5 from Launching EVWEB for Viewing WBEM Indications on page 123. Step 2. Select Delete Events in the action pane on the top right corner of the page. The Delete Events page is displayed. Step 3. Select the event you want to delete by selecting the appropriate check box. You can delete more than one WEBM event at a time. Step 4. Select Delete in the List Events page. EVWEB deletes the event from the event archive database and displays a confirmation message. Step 5. Click OK on the confirmation message window. For information on deleting WBEM events using the HP SMH GUI, select Help on the action pane of the Delete Events page. Deleting an Event Using CLI To delete WBEM events using CLI, enter the following command at the HP-UX prompt: # evweb eventviewer -D Where: -D is an option used to delete all the WBEM events. You can also use the following switches with the -D option: -e [eq\ne\le\ge\bw] [:] <severity level1>[,<severity level2>] -v <cevent category names> -i <EventID> Chapter 5 127

128 Administering Indications and Instances Using HP SMH Viewing Indications -r[is\be\en\co][:](<string to be searched>) -a(<number for age>(:)(yy\mm\dd\hh) -t[eq\le\ge\bw] (<mm:dd:yyyy:hh:mi:ss>)[,<mm:dd:yyyy:hh:mi:ss>] -s[asc\desc] (<summary list column name>) -f -n <comma separated Event Numbers> For information on deleting WBEM events using the CLI, see evweb_eventviewer (1). 128 Chapter 5

129 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer Viewing Low Level Logs Using Log Viewer This section describes how to perform administration tasks such as searching and viewing low level log information. This section discusses the following topics: Overview on page 129 Searching Low Level Logs Using Simple Search on page 130 Searching Low Level Logs Using Advanced Search on page 131 Viewing List of Low Level Logs on page 132 Viewing Details of Low Level Logs on page 134 Overview The Log Viewer enables you to view low level log information from the log database on a local HP-UX system. The low level log information include Log Id, Log Index, Log Version, Device Id, Device Type, Physical Location, and Time of occurrence. You can find the low level log information in both Current Log Database and Archive Log Database. By default, the most recent low level log information is stored in the current log database. The low level log information is automatically transferred from the Current Log Database to the Archive Log Database based on either of the following criterion, or whichever occurs first: The age of the log is greater than 10 days. Logs older than 10 days are automatically stored in the Archive Log Database. The page size of the database exceeds 100. You can modify the /opt/sfmconf/dbconfig.xml file to change the default criteria. Following is a sample /opt/sfmconf/dbconfig.xml file: <SFMConfig> <DBConfig> <PageSize>100</PageSize> Chapter 5 129

130 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer <DBRecordLifeTime>7</DBRecordLifeTime> <ArchedRecordLifetime>365</ArchedRecordLifetime> <ArchDBSize>250</ArchDBSize> </DBConfig> </SFMConfig> The maximum page size is 400, and each page can have 70 records of 4 Kb each. The DBRecordLifeTime indicates the threshold time in days. The maximum threshold time is 7 days. The ArchedRecordLifetime is also measured in days and is set to 365 days (1 year). The ArchDBSize indicates the number of pages in the database. The maximum number of pages is set to 250. If the ArchDBSize exceeds 250, the logs are removed from the database. NOTE The Log Viewer is available only on Integrity servers and not on HP 9000 servers. Searching Low Level Logs Using Simple Search To search the log database for low level logs using Log Viewer, complete the following steps: Step 1. Log in to the System Management Homepage. To log in to HP SMH, enter in the address bar of a Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Select Logs on the main menu. The Logs page is displayed. Step 5. Select Log Viewer in the Evweb box. The Log Viewer page is displayed. 130 Chapter 5

131 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer Step 6. Provide appropriate information in the fields present in the Log Viewer page. Step 7. Click Search on the Log Viewer page. Based on the search criteria, the log records are displayed in a tabular format. For information on searching the log database using GUI, select Help on the action pane of the Log Viewer page. Searching Low Level Logs Using Advanced Search To search the log database for low level logs using Log Viewer, complete the following steps: Step 1. Repeat steps 1-5 from Searching Low Level Logs Using Simple Search on page 130. Step 2. Select Advanced Search on the right pane of the Log Viewer page. The Advanced Search page is displayed. Step 3. Provide appropriate information in the fields present in the Advanced Search page. Step 4. Click Search on the Advanced Search page. Based on the search criteria, the log records are displayed in a tabular format in the Log Viewer page. For information on searching the log database using GUI, select Help on the action pane of the Advanced Search page present on the Log Viewer page. Searching Low Level Logs Using CLI To search for low level log information using the CLI, enter the following command at the HP-UX prompt: # evweb logviewer -L -b <current archive> Where: -L is an option used to obtain a list of low level log summary. Chapter 5 131

132 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer -b is a switch used to specify the location from where the low level logs have to be fetched. You can also use the following switches with the -L option: -i <Log ID> -n <Log Index> -j <Log Type> -x <Device ID> -y <Device Type> -p <Physical Location> -g <Log Source> -a <number for age> (:) (mm dd) -t [eq le ge bw](<mm:dd:yyyy>)[,<mm:dd:yyyy>] NOTE The -a and the -t switches are mutually exclusive and can be used with the -L option only. -s[asc desc] <column name> -o <Offset Number> -c <Number of Logs> NOTE The -s, -o, and the -c switches can be used with the -L option only. For information on searching for low level log information using the CLI, see evweb_logviewer (1). Viewing List of Low Level Logs You can view a list of low level logs summary using the Log Viewer. The list of low level logs are tabulated and include information, such as Log ID, Log Index, Device ID, Device Type, Log Version, and Time of 132 Chapter 5

133 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer occurrence. In this document, this table is referred to as the Logs Summary Table. The Logs Summary Table is a result of the search operation. Viewing List Of Low Level Logs Using GUI To view a list of low level logs using Log Viewer, complete the following steps: Step 1. Repeat steps 1-5 from Searching Low Level Logs Using Simple Search on page 130. Step 2. Depending on the information you have, perform either a simple search or an advanced search. Based on the search criteria, the log records are displayed in a tabular format. For information on viewing the low level logs using GUI, select Help on the action pane of the Log Viewer page. Viewing List Of Low Level Logs Using CLI To view a list of low level logs using the CLI, enter the following command at the HP-UX prompt: # evweb logviewer -L -b <current archive> Where: -L is an option used to obtain a list of low level log summary. -b is a switch used to specify the location from where the low level logs have to be fetched. You can also use the following switches with the -L option: -i <Log ID> -n <Log Index> -j <Log Type> -x <Device ID> -y <Device Type> -p <Physical Location> Chapter 5 133

134 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer -g <Log Source> -a <number for age> (:) (mm dd) -t [eq le ge bw](<mm:dd:yyyy>)[,<mm:dd:yyyy>] NOTE The -a and the -t switches are mutually exclusive and can be used with the -L option only. -s[asc desc] <column name> -o <Offset Number> -c <Number of Logs> NOTE The -s, -o, and the -c switches can be used with the -L option only. For information on viewing a list of low level logs using the CLI, see evweb_logviewer (1). Viewing Details of Low Level Logs You can view a details of low level logs using the Log Viewer. The detailed information about the low level logs include information, such as Log ID, Log Index, Log Type, Log Source, Log Version, Device ID, Device Type, Log Version, Time of occurrence, and Buffer. Viewing Details Of Low Level Logs Using GUI To view details of low level logs using Log Viewer, complete the following steps: Step 1. Repeat steps 1-5 from Searching Low Level Logs Using Simple Search on page 130. Step 2. Depending on the information you have, perform either a simple search or an advanced search. Based on the search criteria, the log records are displayed in the Log Summary Table. Step 3. Select the desired low level log from the Log Summary Table. 134 Chapter 5

135 Administering Indications and Instances Using HP SMH Viewing Low Level Logs Using Log Viewer The details of a low level log is displayed in the Log Viewer page. For information on viewing the low level logs using GUI, select Help on the action pane of the Log Viewer page. Viewing Details Of Low Level Logs Using CLI To view details of low level logs using the CLI, enter the following command at the HP-UX prompt: # evweb logviewer -E -b <current archive> -i <Log ID> -n <Log Index> Where: -E is an option used to obtain details of low level log information. -b is a switch used to specify the location from where the low level logs have to be fetched. -i is a switch used to specify the Log ID. -n is a switch used to specify the Log Index. NOTE The -n switch is mandatory. You can also use the following switch with the -E option: -r For information on viewing details of low level logs using the CLI, see evweb_logviewer (1). Chapter 5 135

136 Administering Indications and Instances Using HP SMH Tracing EVWEB Tracing EVWEB This section provides an overview of tracing and information about the various trace levels in EVWEB. This section also describes administrative tasks such as enabling, modifying, and disabling tracing. This section discusses the following topics: Overview on page 136 Enabling Tracing Using EVWEB GUI on page 139 Modifying Tracing Using EVWEB GUI on page 140 Disabling Tracing Using EVWEB GUI on page 141 Overview Tracing is an error logging and reporting facility. You can use this facility to log information about problems encountered while using EVWEB. All information about errors is logged in sfm.log. The default location of the sfm.log file is /opt/sfm/log/sfm.log. You can send these log files to the HP support center whenever you encounter a problem. Following is a sample of the information logged in sfm.log. 01/04/06 06:50:08 EVMAN_COMMANDS ERROR Subscription with this name already exist, Please choose different name and try again. Table 5-4 describes the various fields included in the sfm.log file. Table 5-4 Entries in sfm.log Field Description Date Time Displays the date when the message was logged in the sfm.log file. Displays the time when the message was logged in the sfm.log file. 136 Chapter 5

137 Administering Indications and Instances Using HP SMH Tracing EVWEB Table 5-4 Field Module Name Severity Process ID Thread ID Message Entries in sfm.log (Continued) Description Displays the name of the module or the providers that logged the message in the sfm.log file, for example, EVWEB_CLI, FMDProviders. Displays the severity of the message logged in the sfm.log file. Displays the 10-digit process ID. Displays the thread ID. Displays the text message. To change the default location of the sfm.log file, you must configure the /opt/sfm/conf/fmloggerconfig.xml file. You can enable tracing for an EVWEB session. A session is the duration between a login and a logout. When you enable tracing, make sure that you set a trace level. Table 5-5 describes the trace levels in EVWEB. Table 5-5 Trace Levels in EVWEB Trace Level 1-Critical Description The system logs only those situations in EVWEB that cause major failures. Example: The database server is not functioning properly or is down. Chapter 5 137

138 Administering Indications and Instances Using HP SMH Tracing EVWEB Table 5-5 Trace Level 2-Error 3-Warning 4-Information Trace Levels in EVWEB (Continued) Description The system logs those situations that cause an error. Example: There is more than one name. EVWEB accepts only one name. Critical situations are also logged at the Error trace level. The system logs situations that result in warning messages. Example: A warning is generated when the default setting is modified. Both critical and error situations are logged at the Warning trace level. The system logs situations that result in information messages. Example: An information is generated when a non-administrator attempts to perform a task that can be performed only by an administrator. Critical, error, and warning situations are logged at the Information trace level. EVWEB logs traces for a session for the set trace level. At the end of a session, tracing is automatically disabled. In an active session, the trace level remains valid until you modify it. 138 Chapter 5

139 Administering Indications and Instances Using HP SMH Tracing EVWEB The traces for a session are also logged in the samlog.log. The path to the samlog.log file is /var/sam/log/samlog.log. From the GUI, you can access the samlog.log file from HP SMH home page -> Logs -> Samlog. The samlog.log file contains all the administrative commands executed on a system. The errors generated during the execution of these administrative commands are also stored in the samlog.log file. NOTE Tracing is available for administrators only. However, non-administrators can view the trace files. Enabling Tracing Using EVWEB GUI To enable tracing, complete the following steps: Step 1. Log in to the System Management Homepage. To log in to HP SMH, enter in the address bar of a Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Do one of the following: Select Tools -> Subscription Administration. or Select Logs -> Event Viewer. Step 5. Select Enable Tracing available at the top right corner of the page. The Enable tracing page is displayed. NOTE The Enable Tracing option is not displayed if tracing is already enabled. Instead, Disable Tracing and Modify Tracing options are displayed. Chapter 5 139

140 Administering Indications and Instances Using HP SMH Tracing EVWEB Step 6. Set the trace level by selecting the level in the Trace Level list. Step 7. Select Enable Tracing. The tracing level is set and a confirmation message is displayed. Step 8. Click OK on the confirmation message window. For more information on enabling tracing using the HP SMH GUI, select Help on the action pane of either the Event Viewer or the Event Subscription Administration page. Enabling Tracing Using EVWEB CLI To enable tracing using EVWEB CLI, you must export the environment variable, EVWEB_TRACE_LEVEL. At the HP-UX prompt, enter the following command: # EXPORT EVWEB_TRACE_LEVEL=<trace value> Tracing is now enabled. The trace value refers to the trace level that you want to set. Modifying Tracing Using EVWEB GUI To modify tracing, complete the following steps: Step 1. Log in to the System Management Homepage. To log in to HP SMH, enter in the address bar of a Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Do one of the following: Select Tools -> Subscription Administration. or Select Logs -> Event Viewer. Step 5. Select Modify Tracing available at the top right corner of the page. 140 Chapter 5

141 Administering Indications and Instances Using HP SMH Tracing EVWEB The Modify Tracing page is displayed. NOTE The Modify Tracing option is not displayed if tracing is not enabled. Step 6. Change the trace level by selecting the level in the Trace Level list. Step 7. Select Modify Tracing. The tracing level is modified and a confirmation message is displayed. Step 8. Click OK on the confirmation message window. For more information on modifying tracing using the HP SMH GUI, select Help on the action pane of either the Event Viewer or the Event Subscription Administration page. Modifying Tracing Using EVWEB CLI To modify tracing using EVWEB CLI, enter the following command at the HP-UX prompt: # EXPORT EVWEB_TRACE_LEVEL=<new trace value> Tracing is now modified. The new trace value refers to the trace level that you want to set. Disabling Tracing Using EVWEB GUI To disable tracing, complete the following steps: Step 1. Log in to the System Management Homepage. To log in to HP SMH, enter in the address bar of a Web browser. The HP SMH login screen is displayed. Step 2. Enter your user name and password in the appropriate text boxes. Step 3. Click Sign In on the login screen. The HP SMH home page is displayed. Step 4. Do one of the following: Select Tools -> Subscription Administration. Chapter 5 141

142 Administering Indications and Instances Using HP SMH Tracing EVWEB or Select Logs -> Event Viewer. Step 5. Select Disable Tracing available at the top right corner of the page. The tracing is disabled and a confirmation message is displayed. NOTE The Disable Tracing option and the Modify Tracing options not displayed if tracing is not enabled. Step 6. Click OK on the confirmation message window. For more information on disabling tracing using the HP SMH GUI, select Help on the action pane of either the Event Viewer or the Event Subscription Administration page. Disabling Tracing Using EVWEB CLI To disable tracing using EVWEB CLI, you must reset the trace value that you have set. At the HP-UX prompt, enter the following command: # unset EVWEB_TRACE_LEVEL Tracing is now disabled. NOTE Tracing is automatically disabled at the end of an EVWEB session. 142 Chapter 5

143 6 Troubleshooting SFM This chapter describes how to troubleshoot SFM providers and EVWEB. This chapter addresses the following topics: Troubleshooting Instance Providers on page 145 Chapter 6 143

144 Troubleshooting SFM Troubleshooting Indication Providers on page 149 Troubleshooting EVWEB on page Chapter 6

145 Troubleshooting SFM Troubleshooting Instance Providers Troubleshooting Instance Providers This section describes techniques for troubleshooting instance providers, such as the CPU Instance Provider, Memory Instance Provider, Filter Metadata (FMD) Provider, and Environmental Providers. Problem The serial number and part number property of memory modules, or bulk power supplies are not available. Cause Either or both of the following can be the cause of this problem: These properties are not supported on the system. The provider is not configured properly. Solution Complete the following steps to check whether the part number and serial number are supported on the given system, and whether the provider is configured properly: Step 1. Enter the following command at the HP-UX prompt: # mstm Step 2. Select System in the product list. Step 3. Click Tools > Information > Run. If the name of the property is displayed in the output, the property is supported. NOTE Not all properties are supported on every supported system. Problem Requests for instances do not return any value. Chapter 6 145

146 Troubleshooting SFM Troubleshooting Instance Providers Cause 1 The Common Information Model Object Manager (CIMOM) is not running. Solution Enter the following command at the HP-UX prompt: # ps -eaf grep cimserver If the name cimserver is displayed in the output, the CIMOM is running properly. If cimserver is not displayed in the output, stop the CIMOM by entering the following command at the HP-UX prompt: # cimserver -s To restart the CIMOM, enter the following command at the HP-UX prompt: # cimserver Cause 2 The provider is not registered properly. Solution Enter the following command at the HP-UX prompt: # cimprovider -ls grep SFMProviderModule If the following output is displayed, all the providers are registered properly: SFMProviderModule OK If the output displayed is different from this output, the provider module is not registered. To register the provider module, enter the following command at the HP-UX prompt: # cimmof -nroot/pg-interop\ /opt/sfm/schemas/mof/sfmprovidersr.mof If no errors are displayed, the provider module is registered successfully. If errors are displayed, restart the CIMOM by entering the following command at the HP-UX prompt: # cimserver After the CIMOM restarts, enter the following command at the HP-UX prompt to register the provider module: 146 Chapter 6

147 Troubleshooting SFM Troubleshooting Instance Providers # cimmof -nroot/pg-interop\ /opt/sfm/schemas/mof/sfmprovidersr.mof After the provider module is registered, create a link between the SFM providers and the CIMOM by entering the following command at the HP-UX prompt: On Itanium-based systems, enter: # ln -s /opt/sfm/lib/libsfmproviders.1\ /opt/wbem/providers/lib/libsfmproviders.so On PA-RISC-based systems, enter: # ln -s /opt/sfm/lib/libsfmproviders.1\ /opt/wbem/providers/lib/libsfmproviders.sl To check whether the link is created, enter the following command at the /opt/wbem/providers/lib directory: # ls Following is a sample output indicating that the link is created: On Itanium-based systems: # lrwxr-xr-x 1 root sys 30 Jan 12 06:56 libsfmproviders.so -> /opt/sfm/lib/libsfmproviders.1 On PA-RISC-based systems: # lrwxr-xr-x 1 root sys 30 Jan 12 6:56 libsfmproviders.sl -> /opt/sfm/lib/libsfmproviders.1 If the link is already present, the following error message appears: # ln: /opt/wbem/providers/lib/libsfmproviders.sl exists Problem First request on systems does not return with required information immediately. Cause Requested information is being collected. The following message is displayed: Inventory is being built currently. Please try after some time. Chapter 6 147

148 Troubleshooting SFM Troubleshooting Instance Providers Solution Wait a while, then request for the information again. Providers respond with requested information when information has been gathered. Problem Indications fulfilling the conditions defined in the HP-Known HP-Defined filters, are not logged in the Event Archive. Cause The HP-Known filters and HP-Known subscriptions have been deleted from the CIMOM. Solution Create the following EnumerateInstances.xml file and save it in any location: EnumerateInstances.xml -> <?xml version="1.0" encoding="utf-8"?> <CIM CIMVERSION="2.0" DTDVERSION="2.0"> <MESSAGE ID="25000" PROTOCOLVERSION="1.0"> <SIMPLEREQ> <IMETHODCALL NAME="EnumerateInstances"> <LOCALNAMESPACEPATH> <NAMESPACE NAME="root"/> <NAMESPACE NAME="cimv2"/> </LOCALNAMESPACEPATH> <IPARAMVALUE NAME="ClassName"> <CLASSNAME NAME="HP_KnownFilter"/> </IPARAMVALUE> </IMETHODCALL> </SIMPLEREQ> </MESSAGE> </CIM> To execute the file, enter the following command at the HP-UX prompt: # wbemexec <full path>/enumerateinstances.xml The full path is the absolute path of the EnumerateInstances.xml file. This recreates HP-Known filters and HP-Known subscriptions in the CIMOM repository, and the indications start logging in the Event Archive. 148 Chapter 6

149 Troubleshooting SFM Troubleshooting Indication Providers Troubleshooting Indication Providers This section describes the techniques for troubleshooting the EMS Wrapper Provider and the SFMIndicationProvider. NOTE The SFMIndicationProvider is available on Itanium-based systems only. The SFMIndicationProvider generates WBEM indications only if you choose to use it. Otherwise, the EMS monitors generate EMS events. These events are converted into WBEM indications by the EMS Wrapper Provider. Problem Indications corresponding to events generated by the Event Monitoring Service (EMS) monitors, are not logged in the Events List. Cause 1 CIMOM is not running. Solution Enter the following command at the HP-UX prompt: # ps -eaf grep cimserver If the name cimserver is displayed in the output, the CIMOM is running properly. If cimserver is not displayed in the output, stop the CIMOM by entering the following command at the HP-UX prompt: # cimserver -s To restart the CIMOM, enter the following command at the HP-UX prompt: # cimserver Cause 2 The provider module is not registered. Solution To check whether the provider module is registered, and to check its status, enter the following command at the HP-UX prompt: Chapter 6 149

150 Troubleshooting SFM Troubleshooting Indication Providers # cimprovider -l -s MODULE ComputerSystemModule SFMProviderModule HPUX_ControlProviderModule ErrorMetadataProviderModule EMArchiveConsumerModule FMDModule STATUS OK OK OK OK OK OK If the status displayed is not OK, the provider module is not registered properly. To register the provider module, enter the following command at the HP-UX prompt: # cimmof -nroot/pg-interop\ /opt/sfm/schemas/mof/sfmprovidersr.mof If no errors messages are displayed, the provider module is registered properly. If errors are displayed, restart the CIMOM by entering the following command at the HP-UX prompt: # cimserver After the CIMOM restarts, enter the following command at the HP-UX prompt to register the provider module: # cimmof -nroot/pg-interop\ /opt/sfm/schemas/mof/sfmprovidersr.mof After the provider module is registered, create a link between the SFM providers and the CIMOM by entering the following command at the HP-UX prompt: On Itanium-based systems, enter: # ln -s /opt/sfm/lib/libsfmproviders.1\ /opt/wbem/providers/lib/libsfmproviders.so On PA-RISC-based systems, enter: # ln -s /opt/sfm/lib/libsfmproviders.1\ /opt/wbem/providers/lib/libsfmproviders.sl To check whether the link is created, enter the following command at the /opt/wbem/providers/lib directory: # ls Following is a sample output indicating that the link is created: 150 Chapter 6

151 Troubleshooting SFM Troubleshooting Indication Providers On Itanium-based systems: # lrwxr-xr-x 1 root sys 30 Jan 12 06:56 libsfmproviders.so -> /opt/sfm/lib/libsfmproviders.1 On PA-RISC-based systems: # lrwxr-xr-x 1 root sys 30 Jan 12 6:56 libsfmproviders.sl -> /opt/sfm/lib/libsfmproviders.1 If the link is already present, the following error message appears: # ln: /opt/wbem/providers/lib/libsfmproviders.sl exists Cause 3 The provider is not registered under the module. Solution To check whether the provider is registered under a module, enter the following command at the HP-UX prompt: # cimprovider -l -m SFMProviderModule The following sample output on Itanium-based systems indicates that the provider is registered under the module: CPUProvider CPUStatusProvider EMSWrapperProvider EventIndicationConsumer SFMIndicationProvider MemoryProvider MemoryStatusProvider StateChangeIndicationProvider ChassisProvider CoolingStatusProvider PowerStatusProvider ThermalProvider VoltageProvider The following sample output on PA-RISC-based systems indicates that the provider is registered under the module: CPUProvider CPUStatusProvider EMSWrapperProvider EventIndicationConsumer MemoryProvider MemoryStatusProvider Chapter 6 151

152 Troubleshooting SFM Troubleshooting Indication Providers StateChangeIndicationProvider ChassisProvider CoolingStatusProvider PowerStatusProvider ThermalProvider VoltageProvider Cause 4 Subscriptions do not exist. Solution Create the following enumerateinstances_sub.xml file and save it in any location: <?xml version="1.0" encoding="utf-8"?> <CIM CIMVERSION="2.0" DTDVERSION="2.0"> <MESSAGE ID="25000" PROTOCOLVERSION="1.0"> <SIMPLEREQ> <METHODCALL NAME="EnumerateInstances"> <LOCALNAMESPACEPATH> <NAMESPACE NAME="root"/> <NAMESPACE NAME="PG_InterOp"/> </LOCALNAMESPACEPATH> <IPARAMVALUE NAME="ClassName"> <CLASSNAME NAME="CIM_IndicationSubscription"/> </IPARAMVALUE> </IMETHODCALL> </SIMPLEREQ> </MESSAGE> </CIM> To enumerate instances, enter the following command at the HP-UX prompt: # wbemexec <full path>/enumerateinstances_sub.xml The full path is the absolute path of the enumerateinstances_sub.xml file. The output of this command indicates the presence of subscriptions, as shown in the following sample output: <INSTANCENAME CLASSNAME="CIM_IndicationFilter"> <KEYBINDING NAME="CreationClassName"> <KEYVALUE VALUETYPE="string"> CIM_IndicationFilter 152 Chapter 6

153 Troubleshooting SFM Troubleshooting Indication Providers </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="Name"> <KEYVALUE VALUETYPE="string"> EventConsumerFilter </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="SystemCreationClassName"> <KEYVALUE VALUETYPE="string"> CIM_ComputerSystem </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="SystemName"> <KEYVALUE VALUETYPE="string"> hpdst348 </KEYVALUE> </KEYBINDING> </INSTANCENAME> </VALUE.REFERENCE> </KEYBINDING> <KEYBINDING NAME="Handler"> <VALUE.REFERENCE> <INSTANCENAME CLASSNAME="CIM_IndicationHandlerCIMXML"> <KEYBINDING NAME="CreationClassName"> <KEYVALUE VALUETYPE="string"> CIM_IndicationHandlerCIMXML </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="Name"> <KEYVALUE VALUETYPE="string"> EventConsumerHandler </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="SystemCreationClassName"> <KEYVALUE VALUETYPE="string"> CIM_ComputerSystem </KEYVALUE> </KEYBINDING> <KEYBINDING NAME="SystemName"> <KEYVALUE VALUETYPE="string"> hpdst348 </KEYVALUE> </KEYBINDING> </INSTANCENAME> Chapter 6 153

154 Troubleshooting SFM Troubleshooting Indication Providers </VALUE.REFERENCE> </KEYBINDING> </INSTANCENAME> Cause 5 The indication providers are not loaded properly. Solution Determine the current monitoring mode by entering the following command at the HP-UX prompt: # /opt/sfm/bin/sfmconfig -w -q If the EMS Hardware Monitors are enabled, the following output displayed: EMS hardware monitors are enabled & SysFaultMgmt is not monitoring any device. If the SFMIndicationProvider is enabled, the following output is displayed: EMS hardware monitors are disabled & SysFaultMgmt is monitoring devices. 1. If the EMS Hardware Monitors are enabled, complete the following steps to check whether the EMS Wrapper Provider is loaded properly: Step 1. Open the /opt/sfm/conf/fmloggerconfig.xml file. Step 2. Using an editor, change the severity of logs from WARNING to INFORMATIONAL. Step 3. Enter the /opt/sfm/bin/sfmconfig command with the /opt/sfm/conf/fmloggerconfig.xml option: # /opt/sfm/bin/sfmconfig /opt/sfm/conf/fmloggerconfig.xml Step 4. Enter the following command to generate a sample indication: # /etc/opt/resmon/lbin/send_test_event <monitor_name> For example: # /etc/opt/resmon/lbin/send_test_event disk_em 154 Chapter 6

155 Troubleshooting SFM Troubleshooting Indication Providers Events generated by the disk_em monitor are translated into indications and reported to the CMS. You can view these indications in the Events List. NOTE You can create sample indications using only those monitors that are supported on your system. For the list of monitors supported on your system, see the EMS Wrapper Provider Data Sheet posted at: Step 5. Open the /opt/sfm/log/sfm.log file. NOTE The /opt/sfm/log/sfm.log file is the file specified in the Target field of the FMLogger.xml file. Following is an example of how the sfm.log file is displayed when you change the logging level to INFORMATIONAL, indicating that the provider is loaded properly: 04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Using port /19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Provider Enabled 04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /storage/events/disks/default/0_0_0_2_0.6.0 Accepted. RequestID : /19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/chassis/chassis_log Accepted. RequestID : /19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/core_hw/core_hw Accepted. RequestID : Use the information available in the file to analyze the problem. Step 6. When you complete testing, revert to the default severity settings in the FMLoggerConfig.xml file using a text editor. If you do not revert to the default settings, the logs consume more disk space. Chapter 6 155

156 Troubleshooting SFM Troubleshooting Indication Providers 2. If the SFMIndicationProvider is enabled, complete the following steps to check whether the SFMIndicationProvider is loaded properly: Step 1. Open the /opt/sfm/conf/fmloggerconfig.xml file. Step 2. Using an editor, change the severity of logs from WARNING to INFORMATIONAL. Step 3. Enter the /opt/sfm/bin/sfmconfig command with the /opt/sfm/conf/fmloggerconfig.xml option: # /opt/sfm/bin/sfmconfig /opt/sfm/conf/fmloggerconfig.xml Step 4. Enter the following command to generate a sample indication: # /opt/sfm/bin/sfmconfig -t -p Indications related to the processor are generated and reported to the CMS. You can view these indications in the Events List. Step 5. Open the /opt/sfm/log/sfm.log file. NOTE The /opt/sfm/log/sfm.log file is the file specified in the Target field of the FMLogger.xml file. Following is an example of how the sfm.log file is displayed when you change the logging level to INFORMATIONAL, indicating that the provider is loaded properly: 04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Using port /19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Provider Enabled 04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /storage/events/disks/default/0_0_0_2_0.6.0 Accepted. RequestID : /19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/chassis/chassis_log Accepted. RequestID : /19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/core_hw/core_hw Accepted. RequestID : Chapter 6

157 Troubleshooting SFM Troubleshooting Indication Providers Use the information available in the file to analyze the problem. Step 6. When you complete testing, revert to the default severity settings in the FMLoggerConfig.xml file using a text editor. If you do not revert to the default settings, the logs consume more disk space. Chapter 6 157

158 Troubleshooting SFM Troubleshooting EVWEB Troubleshooting EVWEB Problem While you are deleting an event stored in the Event Archive, the following error message is displayed: An error occurred while deleting the event. Cause EVWEB is unable to delete an event from the Event Archive. The Event Archive Database service is not running properly. Solution To check the status of the Event Archive Database service, enter the following command at the HP-UX prompt: # ps -eaf grep sfmdb If the output of this command is sfmdb, the Event Archive Database service is running. If the Event Archive Database service has stopped, enter the following command at the HP-UX prompt to start the service: # /sbin/init.d/sfmdb start If the Event Archive Database service is running and the problem persists, check for error logs in the /opt/sfm/log/sfm.log file. For further assistance, contact the HP support center. Problem While you are accessing an event from the Event Archive, either of the following errors are displayed: Could not fetch the details of the events. The connection to the database could not be established. Cause You receive the first message, if EVWEB is unable to access the details of an event stored in the Event Archive. The second message indicates that the EVWEB is unable to establish a connection with the Event Archive. 158 Chapter 6

159 Troubleshooting SFM Troubleshooting EVWEB The Event Archive Database service is not running properly. Solution To check the status of the Event Archive Database service, enter the following command at the HP-UX prompt: # ps -eaf grep sfmdb If the output of this command is sfmdb, the Event Archive Database service is running properly. If the Event Archive Database service is stopped, enter the following command at the HP-UX prompt to start the service: # /sbin/init.d/sfmdb start If the Event Archive Database service is running and the problem persists, check for error logs in the /opt/sfm/log/sfm.log file. For further assistance, contact the HP support center. Problem WBEM Indications are not logged in to the Event Archive. Cause The Event Archive Consumer is disabled. Solution To check the status of the Event Archive Consumer, enter the following command at the HP-UX prompt: # ps -eaf grep sfmdb If the Event Archive Consumer is disabled, enter the following command at the HP-UX prompt to enable the Event Archive Consumer: # /opt/wbem/bin/cimprovider -e -m EMArchiveConsumerModule If the Event Archive Consumer is enabled and if the indications are still not logged in the Event Archive, check for error logs in the /opt/sfm/log/sfm.log file. For further assistance, contact the HP support center. Problem WBEM Indications are not mailed to your address. Cause Chapter 6 159

160 Troubleshooting SFM Troubleshooting EVWEB The Consumer is disabled. Solution To check the status of the Consumer, enter the following command at the HP-UX prompt: # ps -eaf grep sfmdb The system registers the Consumer only when the first event subscription that has as the destination is created. As the Consumer is initially inactive, you can disable or enable the Consumer only after an event subscription having an as its destination, is created. Ensure that you have entered the correct address while subscribing to an event. To enable the Consumer, enter the following command at the HP-UX prompt: # /opt/wbem/bin/cimprovider -e -m EM ConsumerModule If the Consumer is enabled, and the indications are not logged in the Event Archive, check for error logs in the /opt/sfm/log/sfm.log file. For further assistance, contact the HP support center. NOTE For you to enable or disable the Event Archive Consumer and the Consumer, the CIM server must be running. EVWEB does not log events when the Event Archive Consumer or the Consumer is disabled. Problem The response time for a command used to view indications from the Event Archive is long. Cause The locale on your system is set to a language other than English. Solution To improve performance of the Event Viewer, set the locale to English. 160 Chapter 6

161 Glossary A-B Admin-Defined event subscription Subscriptions created by the administrator using the CLI. These subscriptions cannot be deleted. Admin-Defined filters Filters that can be created, deleted, and modified to set the criteria for indications that must be logged. C Central Management Server (CMS) The server monitoring the client systems in the network using SFM. Common Information Model (CIM) An object-based model for describing managed resources. CIM uses the object-oriented paradigm, where managed objects are modeled using the concepts of classes and instances. Common Information Model Object Manager (CIMOM) The component of WBEM that manages the interaction between the providers and other modules in the WBEM environment. CIMOM manages CIM objects. It receives and processes CIM operation requests and issues responses. CIM client An entity in WBEM architecture which sends CIM Operation requests and receives CIM Operation responses. For example, HP SIM and other network management applications are considered CIM clients. CIM server The component of WBEM that manages the interaction between the providers and other modules in the WBEM environment. It is also known as CIMOM. consumer A recipient of services. For example, an indication consumer will receive indications (events) that occur in system hardware components. D disk_em An EMS monitor that monitors hard disks. Distributed Management Task Force (DMTF) An industry organization involved in the development, adoption, and interoperability of management standards and initiatives for enterprise and Internet environments. E enumerate instances To check whether subscriptions to indications are present. event An alert generated when an unusual activity is detected on a monitored hardware device. Event Archive Database for indications. Indications generated on hardware devices are logged in this location. EVWEB User component that enables administering and viewing WBEM indications generated on the system on which SFM is installed. Event Subscription Administration A component of EVWEB used to subscribe to indications. Event Viewer A component of EVWEB used to view indications present in the Event Archive. Glossary 161

162 Glossary External subscriptions External subscriptions These are subscriptions created by tools other than EVWEB. F-G fmcontrol The command used to configure software error logging parameters. fmdcontrol The command used to create, delete, and modify Admin-Defined filters. H HP-Advised event subscription Subscriptions that are provided by HP. HP-Defined filters Filters defined by HP, and present in the FMD repository at the time of installation. HP-Known event subscription Subscriptions that are provided by HP. These subscriptions include both Admin-Defined subscriptions and HP-Advised subscriptions. HP Systems Insight Manager (HP SIM) HP's management application installed on the CMS that uses WBEM instrumentation on operating systems such as HP-UX, Linux, and Windows. HP System Management Homepage (HP SMH) HP's management application installed on the local system that uses WBEM instrumentation on operating systems such as HP-UX, Linux, and Windows. I-K indication An alert or a warning about the failure of a monitored hardware device. It is equivalent to an event in the Event Monitoring Service (EMS) framework. Indication Consumer A component of EVWEB for Event Archive to store indications in the Event Archive. Indication Consumer for A component of EVWEB to send indications to the configured address. indication filters They are configured by the Filter Metadata (FMD) Provider to set the criteria for the indications that must be logged. indication provider It translates events generated by the Event Monitoring Service (EMS) monitors into WBEM indications, and reports them to the CIMOM. instance A representation of the actual physical object that belongs to a class. instance provider It provides information about devices, such as model number and serial number of a CPU. In the Support Tools Manager (STM), this functionality is accomplished by Information (Info) Tools. L Logfile A file that includes details about the SFM software installation and removal. M-R managed resource A hardware device that is monitored. 162 Glossary

163 management application Any application that can be used to query for information about monitored devices and view indications and instances. Examples: HP Systems Insight Manager (SIM), HP System Management Homepage (HP SMH). Glossary WBEM (Web-Based Enterprise Management) mstm STM command to display the properties supported on the system. S sfmdb The output of a command that indicates that Event Archive Database service is running properly. subscription Configuring SFM for consumers to receive indications. For example, HP SIM could subscribe to indications generating on hardware devices on a system. SysFaultMgmt The name of the bundle that includes the SFM software. T-V Tracing Tracing is an error-logging and reporting facility provided by EVWEB. W-Z WBEM (Web-Based Enterprise Management) A collection of standards that aid large-scale systems management. WBEM allows management applications to monitor systems in a network. Glossary 163

164 Glossary management application 164 Glossary

165 Index A administrator, 91 Autoselect dependency, 30 B benefits SFM, 14 C Central Management Server See CMS CIMOM, 22, 24 cimserver, 146 -s option, 146 CMS, 22 command-line interface, 30 Common Information Model Object Manager See CIMOM Common Information Model Object ManagerSee CIMOM configuration SFM, 32 SFMIndicationProvider, 53 cooling device, 88 cooling devices on a system, 81 CPU instance provider, 87 creation subscription, 61 D delete event subscription, 99, 115 WBEM indication, 127 E Consumer configuring, 101 EMS hardware monitor property, 76 EMS Wrapper Provider no subscription error, 152 not loaded properly error, 154 property, 76 Enables, 14 Enforce dependency, 31 Environmental Provider, 88 Event Archive, 50, 159 HP-Known HP-Defined filter, 50, 148 troubleshooting, 158, 159, 160 event list, 72 Event Monitoring Services See EMS event subscription Admin-Defined, 92 copying, 95, 99 creating, 91, 93, 95, 111, 113 deleting, 100, 116 external subscription, 103 HP-Advised, 103 HP-Known, 95 managing, 91 modifying, 97, 99, 114 viewing external event subscription, 108 EVWEB, 90 CLI, 91, 123 component, 90 GUI, 91, 123 local administration, 90 tracing, 136 user interface, 91 using CLI, 91 using GUI, 91 F features SFM, 14 Filter Metadata, 17 FMD, 17 FMD repository, 50 H HP SIM, 18 HP SMH, 21 logging, 91, 123 HP-Defined filters, 50 HP-Known HP-Defined filter, 50, 148 I indication, 159 troubleshooting, 149, 159 viewing, 91 indication provider, 15 SFMIndicationProvider, 19 indications, 61 instance provider, 15, 145 CPU, 16, 145 Environmental, 16, 145 Filter Metadata,

166 Index Memory, 16, 145 J jobid, 37 L Log Viewer, 129 Archive Log Database, 129 Current Log Database, 129 Logfile, 36, 37 logging, 136 logs /opt/sfm/log/sfm.log file, 136 /var/sam/log/samlog.log file, 139 M memory configuration, 80 memory module troubleshooting, 145 modify event subscription, 97, 114 module troubleshooting, 151 N non-administrator, 91 O /opt/sfm/conf/evweb.conf file, 101 /opt/sfm/conf/fmloggerconfig.xml file, 137 /opt/sfm/log/sfm.log file, 136 OEUR, 29 online diagnostics version, 29 OnlineDiag, 29 OpenSSL, 29 Operating Environment Update Release See OEUR P physical memory, 88 power status, 82 power supply, 88 printable report, 70 processor, 87 processor configuration, 79 processor status, 79 property information, 16 provider indication provider, 15 instance provider, 15 S search WBEM indication, 123 SFM, 13, 14 indication provider, 18 provider, 13, 15 SFM instance provider type of query, 21 SFMIndicationProvider, 19, 54 Simple Mail Transfer Protocol See SMTP SMTP, 101 status of memory, 80 status of processors, 79 subscription creating, 90, 110 managing, 90, 110 subscriptions creating, 61 swinstall command, 34 swjob, 36, 37, 38 swlist command, 33 swremove command, 39 SysFaultMgmt, 33, 45 SysMgmtWeb, 29 System Fault Management See SFM System Page of HP SIM, 78 T temperature, 89 temperature status, 83 terminal user interface, 30 Throttling Configuration, 110, 118 throttling policy, 110 tracing, 136 troubleshooting, 159 EMS Wrapper Provider, 152, 154 Event Archive, 158, 160 memory module, 145 module, 151 V /var/sam/log/samlog.log file, 139 verify SFM, 33 view EVWEB event subscription, 104,

167 Index external event subscription, 107 WBEM indication, 125, 126 view indications, 65 voltage, 89 voltage status, 83 W WBEM, 13 administer, 90 component, 13 HP Systems Insight Manager, 13 HP WBEM services, 13 viewing, 90 WBEM Indication administer, 90, 110 delete, 127 search, 124 summary, 125 WBEM provider, 13 Web-Based Enterprise Management See WBEM 167

168 Index 168