Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
System Fault Management Administrator's Guide: HP-UX 11i v3 > Chapter 1 Introduction

Components of SFM

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

This section discusses the following topics:

  • EVWEB

  • Error Management Technology (EMT)

  • Providers

EVWEB

EVWEB is a component of SFM that enables you to administer and view WBEM indications generated on the local system on which SFM is installed. For more information on EVWEB, see “EVWEB Overview”.

EMT

EMT is a component of SFM, which contains most errors that can occur on the HP-UX 11i v3 system. You can view these error messages using HP SMH on the local system. For more information on EMT, see “EMT Overview”.

Providers

SFM providers are components of SFM that retrieve information about the inventory on a system and the events that occur on the hardware resources. SFM providers can be classified as instance providers or as indication providers. This section describes SFM providers.

Instance Providers

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.

Table 1-1 Instance Providers

Instance ProviderDescription
CPU

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.

Memory

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

Firmware Revision

The Firmware Revision Provider retrieves the following types of information:

  • System firmware revision

  • Management Processor (MP) firmware revision

Disk

The Disk Instance Provider retrieves the following types of information from the direct attached disk drives, such as the SCSI drives:

  • Consolidated health status

  • Inventory information

Management Processor

Retrieves information about the management processor on the system.

Enclosure

The Enclosure Instance Provider retrieves the following types of information:

  • Onboard Administrator (OA) description

  • OA IP address

  • OA MAC address

  • URL to launch the OA

NOTE: The Enclosure Instance Provider is available on BL860c HP Server Blade only.

 

Indication Providers

SFM includes two indication providers, the EMS Wrapper Provider and the Event Manager Common Information Model (EVM CIM) Provider. Table 1-2 describes the SFM indication providers.

Table 1-2 Indication Providers

Indication ProviderDescription
EMS Wrapper Provider

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.

EVM CIM Provider

The EVM CIM Provider does the following:

  1. Converts hardware, software, and kernel events generated by the EVM 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 EVM 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.

SFMIndicationProvider

The SFMIndicationProvider generates indications that are compliant with the WBEM standards. On Itanium-based systems, it replaces the following EMS monitors:

  • cmc_em

  • cpe_em

  • memory_ia64

  • fpl_em

  • ia64_corehw

On PA-RISC-based systems, it replaces the following EMS monitors:

  • fpl_em

  • ia64_corehw

You can choose to use either the SFMIndicationProvider or the EMS monitors that it replaces, to monitor your hardware. 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 equivalent to the events that the monitors it replaces generate.

  2. Reports these WBEM indications to the CIMOM.

 

NOTE: The following apply to indication providers:
  • The terms events and indications are used interchangeably.

  • Although both EMS Wrapper Provider and EVM CIM Provider generate events related to system hardware, the nature of events are different.

CIMOM identifies the SFM providers using SFMProviderModule. If a provider is not working properly, SFMProviderModule stops all the SFM providers. Starting with the HP-UX 11i v3 February 2007 release, SFM includes the cron job. Every 15 minutes, the cron job checks if SFMProviderModule is running. If SFMProviderModule is not running, the cron job starts SFMProviderModule which in turn starts all the providers.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2007 Hewlett-Packard Development Company, L.P.