System Fault Management Release Notes
HP-UX 11i v3 September 2007

Announcement

System Fault Management (SFM) is a collection of tools used to monitor the health of HP servers and receive information about hardware such as memory, CPU, power supplies, and cooling devices. SFM operates in the Web-Based Enterprise Management (WBEM) environment.

SFM includes the following tools:

• SFM Providers
• EVWEB
• EMT

This document contains the following sections:

• SFM Providers
  • What Is New in This Version
  • Supported EMS Hardware Monitors
  • Defect Fixes
• EVWEB
  • What Is EVWEB
  • Benefits
  • Features
  • What is New in EVWEB
  • Limitations
• EMT
  • What Is EMT
  • Benefits
  • Features
  • Defect Fixes
  • Limitations
• System Requirements
• Supported Browsers
• Limitations and Workarounds
• Product Documentation
• Software and Documentation Availability in Native Languages
• Product Structure
• Reporting Defects

SFM Providers

SFM providers are tools that gather information related to various hardware devices and report to the Common Interface Model Object Manager (CIMOM).

Following lists the SFM providers, and their respective functions:

Providers	Functions
CPU Instance Provider	Retrieves information about processor inventory and consolidated health of the processor subsystem
Memory Instance Provider	Gathers information about memory inventory and consolidated health of the memory subsystem
EMS Wrapper Provider	Converts events generated by the EMS Hardware Monitors into indications and reports those indications to the CIMOM
Filter Metadata (FMD) Provider	Provides the facility to predefine the important filter in a repository. FMD also ensures that all important or chosen indications are logged to the local event archive. FMD creates HP-advised subscriptions when SFM is installed.
Environmental Providers	Retrieve information about cooling devices (fans) and power supply (bulk power supply and AC input lines) on HP servers. They also retrieve consolidated health of cooling, power, system temperature, and system voltage subsystems on HP servers.
Event Manager Common Information Model (EVM CIM)Provider	Converts EVM events into indications and reports those indications to the CIMOM
SFMIndicationProvider	Generates WBEM indications when an abnormal activity is detected on the monitored devices and reports these WBEM indications to the EMS framework.
Firmware Revision Instance Provider	Retrieves information about the firmware revision of system hardware components, such as system firmware version and Management Processor (MP) firmware version.
Disk Instance Provider	Retrieves information about the consolidated health status and inventory information of direct attached disk drives, such as SCSI drives.
MP Instance Provider	Retrieves information about the management processor of the system.
Enclosure Instance Provider	Retrieves information about the Onboard Administrator (OA), such as OA description, OA IP address, OA MAC address, and the URL to launch the OA.

What Is New in This Version

The following new providers are included in this release:

• SFMIndicationProvider
• Firmware Revision Instance Provider
• Disk Instance Provider
• MP Instance Provider
• Enclosure Instance Provider

On Itanium-based systems, you can choose to use the SFMIndicationProvider instead of the following EMS Hardware Monitors:

• Corrected Platform Error Monitor (cpe_em)
• IPMI Forward Progress Log Monitor (fpl_em)
• CMC Monitor (cmc_em)
• Itanium Core Hardware Monitor (ia64_corehw)
• Itanium Memory Monitor (memory_ia64)

On HP 9000 systems, you can choose to use the SFMIndicationProvider instead of the following EMS Hardware Monitors:

• IPMI Forward Progress Log Monitor (fpl_em)
• Itanium Core Hardware Monitor (ia64_corehw)

Note: Inventory is built once every 10 minutes. If a cell is added or deleted within the 10-minute time window, and a request for inventory details is made, values available at the previous build are reported. However, requests made at the end of the 10-minute time window retrieve the latest information. This is expected behavior.

Supported EMS Hardware Monitors

The following Event Monitoring Service (EMS) monitors are supported on HP 9000 servers running the HP-UX 11i v3 operating system:

• LPMC (now CPU) (lpmc_em)
• Memory (dm_memory)
• Core HW (dm_core_hw)
• Chassis Code (dm_chassis)
• Disk (disk_em)
• Integrity Core Hardware Monitor(ia64_corehw)
• IPMI Forward Progress Log Monitor (fpl_em)

The following EMS hardware monitors are supported on Itanium-based servers running the HP-UX 11i v3 operating system:

• Corrected Platform Error Monitor (cpe_em)
• IPMI Forward Progress Log Monitor (fpl_em)
• CMC Monitor (cmc_em)
• Itanium Core Hardware Monitor(ia64_corehw)
• SCSI Disk Monitor (disk_em)
• Itanium Memory Monitor (memory_ia64)

Defect Fixes

• JAGag36451
  Problem: On the following systems based on PA-RISC processors and sx2000 chipset, SFM does not display serial and part numbers of DIMMs in the memory property pages:
  
  • SD16B
  • SD32B
  • SD64B
  Resolution: This problem is fixed. Serial and part numbers are displayed correctly.
• JAGag36284
  Problem: SFM reports incorrect power status on the following systems:
  • rx3600
  • rx6600
  Resolution: This problem is fixed.
• JAGag39970
  Problem: While installing or removing the PHSS_36078 patch, the patch scripts attempt to disable the SFMProviderModule. This is expected behavior. However, on high-end systems, the SFMProviderModule does not terminate instantly. As a result, the installation of the patch may fail and an error message is displayed. You must retry the operation to complete the process without errors.
  Resolution: This problem is fixed.

EVWEB

This section describes EVWEB.

What Is EVWEB

EVWEB is a tool that can be used to view and administer WBEM indications generated on the HP-UX 11i v3 system.

The EVWEB tool includes the following components:

• Event Subscription Administrator
  Event Subscription Administrator enables users to subscribe to an indication and view it. In addition, users with administrative privileges can also modify, and delete subscriptions. By subscribing to an indication, users can obtain detailed information about various WBEM indications. Users can also view indications generated by the High Availability Monitors. Indications generated by High Availability Monitors are called HP threshold indications.
  As a part of event subscription, users must specify event subscription criteria. Users must also select one or more destinations to receive information about indications.
  Users can select one or more destination from the following list:
  • Event Archive: The path to Event Archive is /var/opt/sfmdb/pgsql. Event Archive is the default destination.
  • syslog: The path to syslog is /var/adm/syslog/syslog.log.
  • Email: Event notification will be emailed to the specified email address. Users can specify multiple email addresses.
• Event Viewer
  The Event Viewer enables users to view the indications stored in the Event Archive. In addition, users with administrative privileges can also delete these indications. By default, HP-advised subscriptions are stored in the Event Archive. The Event Viewer also enables users to search for an indication logged in the Event Archive.
• Log Viewer
  The Log Viewer enables users to view and search the low level logs stored in the log database.

Benefits

Following lists the benefits of EVWEB:

• Enables users to manage all WBEM indications that are supported by SFM.
• Provides an option to customize the indication destination to receive information about HP-advised subscriptions.
• Enables users to view the command-line equivalent of an action performed using the GUI, thereby, educating users about the usage of various commands.

Features

Following lists the features that EVWEB offers:

• Provides quick search and advanced search mechanisms to view events from the Event Archive
• Generates a list of events in a printer-friendly format (GUI only)
• Enables users with administrative privileges to delete indications
• Enables users with administrative privileges to manage subscriptions, such as creating, modifying, and deleting indications
• Enables users to view subscriptions created using EVWEB
• Enables users to view externally created subscriptions.
  Subscriptions created by using tools other than EVWEB are termed as externally created event subscriptions.
• Enables users to view HP-advised subscriptions. HP-advised subscriptions are provided by default by HP.

Note: EVWEB supports these features on browser-based GUI and the CLI.

What Is New in EVWEB

• The Event Subscription Administration includes a new administrative feature, Throttling Configuration, on HP 9000 and Itanium-based systems. Using this feature, you can view and administer a throttling configuration.
• The Log Viewer component is available on HP 9000 and Itanium-based systems.
• The following table lists the modified column names of the Event Summary table:

  Old Field Names	New Field Names
  EventNo	EvArchNo
  EventId	Event #
  Time of Archive	Archive Time

• Additional fields are included in the event details.
• A -x option is added to the evweb eventviewer -L command. This new option enables you to list events and their respective details based on your search criteria.

Defect Fixes

• JAGag27895
  Problem: An event notification e-mail does not contain the correct severity level associated with the event. The severity level is displayed as 'Not Available'. However, the severity level is accurately displayed in the subject line of the email.
  Resolution: This inconsistency in the display of severity level is now fixed.
• JAGag29956
  Problem: If you click Preview while creating a subscription using the EVWEB GUI, the selected throttling configuration is lost. Instead, the default throttling configuration is selected.
  Resolution: This issue is now fixed.
• JAGag37984
  Problem: The subscribe option in the evweb command fails for EVM events.
  Resolution: This issue is now fixed.

Limitations

• When a HP-advised subscription is copied to create or modify another subscription, the subscription criteria is not copied. However, only destinations are copied to the new subscription.
• Event details displayed in EVWEB Event Viewer and embedded in the EVWEB email notification may not have similar readability or formatting as provided by the EMS event notification. However, this issue is not applicable to HP_DeviceIndication class indications.

EMT

This section describes EMT.

What Is EMT

Error Management Technology (EMT) is a component of SFM. EMT includes Common Error Repository (CER), which is an online, searchable, and updateable error repository. The CER contains error metadata such as error description, error number, error type, severity, cause of the error, and corrective actions for errors generated on the HP-UX 11i v3 system.

Benefits

Following lists the benefits of EMT:

• Enables users to view most errors that can occur on the HP-UX 11i v3 system.
• Provides an option to the administrators to add, modify, and delete custom solutions.
• Enables users to view the command-line equivalent of an action performed using the GUI, thereby, educating users about the usage of various commands.

Features

EMT offers the following features:

• Provides both quick search and advanced search mechanisms to view error metadata from CER
• Generates a list of errors in a printer-friendly format (GUI only)
• Enables users with administrative privileges to create, modify, and delete custom solutions

Note: EMT supports these features on browser-based GUI and the CLI.

Defect Fixes

• JAGag37884
  Problem: The emtui command displays an error message when you provide the following valid keywords with the -e option:
  
  • errno
  • generic
  • gsp
  Resolution: This problem is fixed.
• JAGag38452
  Problem: The Add Custom Solution to Selected Causes feature in EMT does not function as expected. For example, if an error has multiple causes and if you select one cause to add a custom solution, EMT adds the custom solution to all the causes.
  Resolution: This problem is fixed.
• JAGag34215
  Problem: The SysFaultMgmt bundle fails under the following conditions:
  
  • The postmaster service is not started before installing EMT.
  • The permission for the /opt/sfm/lib directory is not 644.
  Resolution: This problem is fixed.
• JAGag38226
  Problem: EMT incorrectly indicates that the events generated by the fpl_em monitor are generated by the FPL_IndicationProvider.
  Resolution: This problem is fixed.
• JAGag37886
  Problem: The EMT manpage, emtui(1), displays incorrect information about the error types that EMT supports.
  Resolution: This problem is fixed. The emtui(1) displays the correct information.
• JAGag38461
  Problem: The Add Custom Solution to Selected Causes feature in EMT does not function as expected. When a Custom Solution is added to more than one cause, the Custom Solution is interchanged with the HP Defined actions.
  Resolution: This problem is fixed. The Custom Solutions and the HP Defined actions are not interchanged.

Limitations

Following is a limitation of EMT:

• When you make a generic query to the CER, a huge amount of data is retrieved from the CER. However, this behavior may affect the performance of EMT.

System Requirements

SFM is supported on the following systems running the HP-UX 11i v3 operating system:

• HP 9000 servers
  • rp3410
  • rp3440
  • rp4410
  • rp4440
  • rp7405
  • rp7410
  • rp7420
  • rp8400
  • rp8420
  • SD16, SD32, SD64
  • SD16A, SD32A, SD64A
  • SD16B, SD32B, SD64B
• Itanium-based servers
  • cx2600
  • cx2620
  • rx1600
  • rx1620
  • rx2600
  • rx2620
  • rx2660 (supports PCI-X IO backplane only)
  • rx3600
  • rx4640
  • rx5670
  • rx6600
  • rx7620
  • rx7640
  • rx8620
  • rx8640
  • SD16A, SD32A, SD64A
  • SD16B, SD32B, SD64B
  • BL60p HP Server Blade

SFM supports the following systems based on the IntelŪ ItaniumŪ Processor 9100 series and running the HP-UX 11i v3 operating system:

• rx7640
• rx8640
• SD16B
• SD32B
• SD64B

Following lists the software requirements for using SFM:

• HP-UX 11i v3 February 2007
• OpenSSL Version A.00.09.07e.013 or later
• WBEM Services Version A.02.05 or later
• EVM-EventMgr B.11.31
• SysMgmtBase B.00.02.03
• SysMgmtWeb version A.2.2.4 (HP-UX Web Based System Management User Interface)
• Online Diagnostics B.11.31.01.yy
  Notes:
  • SysMgmtWeb is optional. However, you will not be able to access EVWEB GUI if SysMgmtWeb is not installed on the system. SysMgmtWeb, WBEMServices, and Online Diagnostics are available on the Operating Environment (OE) media.
  • HP recommends that you install HP Systems Insight Manager (HP SIM) version 5.0.01 to remotely administer indications and instances.
  • The mentioned versions of the software are minimum requirements. All future versions support SFM by default.

Supported Browsers

Following lists the browsers supported by SFM:

• Internet Explorer version 6.0 and above
• Mozilla version 1.5 and above

Limitations and Workarounds

• After the system is rebooted or the CIMOM is restarted, the first request to SFM hardware inventory providers such as the CPU Instance Provider, Memory Provider, and the Environmental Providers may fail with the generation of the CIM_ERR_FAILED status code. Also, a message is displayed on the client system that states " Inventory information is being built currently. Please try after some time" . However, on subsequent requests, the SFM hardware inventory providers respond with requested information instantaneously.
• Hardware inventory providers are not supported on HP Virtual Machines.
• JAGag36913
  Symptom: SFM dumps core in /var/opt/wbem/ during an OE update on HP 9000 systems.
  Workaround: Remove the dump. Shortly after, SFM starts functioning properly.
• JAGag42447
  Problem: If processors are added to a system after the system's migration into a vPar environment, serial numbers and part numbers of the newly added processors are not displayed. However, the remaining properties of the processors are displayed.
  Workaround: Complete the following steps to retrieve information from the Management Processor (MP):
  1. Enter the following command to connect to the MP:
     # telnet management port
     For example,
     # telnet abc1.ind.hp.com
     The MP Login prompt is displayed.
  2. Enter cm to select the Command Menu.
  3. Enter df.
  4. Enter S to view information about any Field Replacement Unit (FRU).
  5. Enter M to select processor module.
  6. Enter the cabinet number.
  7. Enter the cell slot number.
  8. Enter the processor module number of the cell.
     Note: All the values are available in the HP SMH property page for processors. For information on how to view the property pages, see the SFM Administrator's and User's Guide at:
     http://docs.hp.com/en/diag.html
     All the details of the processor module are displayed. The following is a sample output:
     

     FRU ID Definition Revision     : B
     Artwork Revision               : A4
     Engineering Date Code          : XB01
     Part Number                    : AB367-62005
     Serial Number                  : PR20448034
     FRU Name                       : MAKO-41-1068
     Scan Revision                  : 0x1
     FRU Specific Information       : 2E42C10B HAA    
     Checksum                       : 0x1e (valid)
     Manufacturing and Test History :
     Field 0 0x110504120601000000
     Field 1 0xac2104121501000000
     Field 2 0x000000004449000000
     Field 3 0x3aa407020000000000
     Field 4 0x000000000000000000
     Field 5 0x000000000000000000
     Field Spare 0x0000

• JAGag42218
  If some products are removed, a core is generated during a system reboot.

Product Documentation

For more information on SFM, see the following documents at:
http://docs.hp.com/en/diag.html

• SFM Frequently Asked Questions (FAQs)
• System Fault Management Administrator's Guide
• SFM Provider Data Sheets
• SFM Tables of Versions
• SFM Patch Descriptions

Software and Documentation Availability in Native Languages

SFM software and documents are available only in the English language.

Product Structure

The SFM product, consisting of SFM providers and EVWEB, is installed as part of the SysFaultMgmt bundle.

Following are the commands you must use to obtain the bundle, product, sub-product, and the fileset information about the SysFaultMgmt depot:

• Bundle
  

  $ swlist -s <SysFaultMgmt Depot Location>
  
  SysFaultMgmt C.02.00.xx.yy HPUX System Fault Management

• Product(s)
  

  $ swlist -l product -s <SysFaultMgmt Depot Location>
  
  SFM-CORE   C.02.00.xx   HPUX System Fault Management
  SFMDB      C.02.00.xx   HP System Management Database (SFMDB)

• Sub-product(s)
  

  $ swlist -l subproduct -s <SysFaultMgmt Depot Location>
  
  SFM-CORE.HS-PROVIDER     HS-PROVIDER
  SFM-CORE.ERROR-MGMT      Error Management Technology
  SFM-CORE.EVWEB
  SFM-CORE.FMD-PROVIDER    FMD-PROVIDER
  SFM-CORE.GS              GS
  SFM-CORE.SFM-HAS         SFM-HAS
  SFM-CORE.SFM-PROVIDER    SFM-PROVIDER
  SFMDB                    C.02.00.xx    HP System Management Database (SFMDB)

• Fileset(s)
  

  $ swlist -l fileset -s <SysFaultMgmt Depot Location>
  
  
  # SFM-CORE                      C.02.00.xx     HPUX System Fault Management
    SFM-CORE.HS_PRO_COREIA        C.02.00.xx     HealthState Instance Provider Platform Specific Fileset
    SFM-CORE.HS_PRO_COREPA        C.02.00.xx     HealthState Instance Provider Platform Specific Fileset
    SFM-CORE.CTR_PRO_COMM         C.02.00.xx     Control Provider Common Fileset
    SFM-CORE.CTR_PRO_COREIA       C.02.00.xx     Control Provider Platform Specific Fileset
    SFM-CORE.CTR_PRO_COREPA       C.02.00.xx     Control Provider Platform Specific Fileset
    SFM-CORE.EMT_COMM             C.02.00.xx     EMT Common components
    SFM-CORE.EMT_COREIA           C.02.00.xx     EMT core platform specific fileset
    SFM-CORE.EMT_COREPA           C.02.00.xx     EMT core platform specific fileset
    SFM-CORE.EVWEB_COMM           C.02.00.xx     Event Manager (EvWEB) Common components
    SFM-CORE.EVWEB_COREIA         C.02.00.xx     EvWEB core platform specific fileset
    SFM-CORE.EVWEB_COREPA         C.02.00.xx     EvWEB core platform specific fileset
    SFM-CORE.EVWEB_DOC            C.02.00.xx     EvWEB Online help fileset
    SFM-CORE.EVWEB_GUI_COMM       C.02.00.xx     EvWEB GUI common fileset
    SFM-CORE.EVWEB_GUI_IA         C.02.00.xx     EvWEB GUI platform specific fileset
    SFM-CORE.EVWEB_GUI_PA         C.02.00.xx     EvWEB GUI platform specific fileset
    SFM-CORE.EVWEB_MAN            C.02.00.xx     EVWEB Man pages fileset
    SFM-CORE.FMD_PRO_COMM         C.02.00.xx     Filter Metadata Instance Provider Common Fileset
    SFM-CORE.FMD_PRO_COREIA       C.02.00.xx     Filter Metadata Instance Provider Platform Specific Fileset
    SFM-CORE.FMD_PRO_COREPA       C.02.00.xx     Filter Metadata Instance Provider Platform Specific Fileset
    SFM-CORE.GS_COMM              C.02.00.xx     General Services Common Fileset
    SFM-CORE.GS_COREIA            C.02.00.xx     General Services Platform Specific Fileset
    SFM-CORE.GS_COREPA            C.02.00.xx     General Services Platform Specific Fileset
    SFM-CORE.HAS-IA               C.02.00.xx     Hardware Access ServicesIA
    SFM-CORE.HAS-PA               C.02.00.xx     Hardware Access Services PA
    SFM-CORE.MISC_COMM            C.02.00.xx     MISC Common Fileset
    SFM-CORE.MISC_COREIA          C.02.00.xx     MISC Platform Specific Fileset
    SFM-CORE.MISC_COREPA          C.02.00.xx     MISC Platform Specific Fileset
    SFM-CORE.SFM_PRO_COMM         C.02.00.xx     SysFaultMgmt Provider Module COMMON
    SFM-CORE.SFM_PRO_IA           C.02.00.xx     SysFaultMgmt Provider Module IA
    SFM-CORE.SFM_PRO_PA           C.02.00.xx     SysFaultMgmt Provider Module PA
  # SFMDB                         C.02.00.xx     HP System Management Database (SFMDB)
    SFMDB.SMPGSQL-DOC             C.02.00.xx     PostgreSQL  (SFMDB) Documentation Files
    SFMDB.SMPGSQL-INC             C.02.00.xx     PostgreSQL (SFMDB) Header Files
    SFMDB.SMPGSQL-LIB             C.02.00.xx     PostgreSQL (SFMDB) Library Files (Architecture dependent)
    SFMDB.SMPGSQL-LIB             C.02.00.xx     PostgreSQL (SFMDB) Library Files (Architecture dependent)
    SFMDB.SMPGSQL-MAN             C.02.00.xx     PostgreSQL (SFMDB) Manual Pages
    SFMDB.SMPGSQL-RUN             C.02.00.xx     PostgreSQL (SFMDB) Executable Files (Architecture dependent)
    SFMDB.SMPGSQL-RUN             C.02.00.xx     PostgreSQL (SFMDB) Executable Files (Architecture dependent)
    SFMDB.SMPGSQL-SHA             C.02.00.xx     PostgreSQL (SFMDB) Share File
    SFMDB.SMPGSQL-SRC             C.02.00.xx     PostgreSQL (SFMDB) Source Files
  

Reporting Defects

You can report defects related to SFM or EVWEB by filing a request on CHART. The name of the project is diag.sfm. If you do not have access to CHART, contact your local HP representative to file a defect on your behalf.

Diagnostics home