System Fault Management Release Notes
HP-UX 11i v2 June 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

Note: Starting with the HP-UX 11i v2 March 2006 release, EVWEB is included in the SysFaultMgmt bundle.

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
• System Requirements
• Supported Browsers
• Limitations
• 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	Translates 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.
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 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:

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

Note:

• The SFMIndicationProvider now supports PA-RISC-based systems.
• The Enclosure Instance Provider is available on BL860c HP Server Blade only.

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 PA-RISC-based 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)

Supported EMS Hardware Monitors

The following EMS monitors are supported on PA-RISC-based servers running the HP-UX 11i v2 operating system:

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

The following EMS hardware monitors are supported on Itanium-based servers running the HP-UX 11i v2 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

• JAGag27501
  Problem: Events generated by the EMS Hardware Monitors do not include a log id in EVWEB Event Viewer. Instead, the log id field states Not Available. However, events generated by the SFMIndicationProvider include a log id.
  Resolution: This problem is fixed. Events generated by the EMS Hardware Monitors include error details in EVWEB Event Viewer. Events generated by the SFMIndicationProvider continue to include a log id.
• JAGag24831
  Problem: If the HP-UX 11i v2 September 2006 version of SFM is removed using the swremove command, some files are not deleted.
  Resolution: Changes are made to remove those files that are not required once SFM is removed.
• JAGag31617
  Problem: Temporary files that are created when the SFM database is archived are not removed by default.
  Solution: Changes are made to remove the temporary files by default.

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 v2 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.
  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 of Event Archive is /var/opt/sfmdb/pgsql. Event Archive is the default destination.
  • 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
  Log Viewer enables users to view low level logs that are generated on an HP-UX system. The low level logs are stored in the log database and contain information such as Log Id, Log Index, Log Version, Device Id, Device Type, Physical Location, and Time of occurrence.

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

EVWEB offers the following features:

• Provides both quick search and advanced search mechanisms to view events from the Event Archive
• Provides both simple and advanced search mechanism to search for low level logs from the Log Viewer.
• Generates a list of events in a printer-friendly format (GUI only)
• Enables users with administrative privileges to create, modify, and delete indications
• Enables users with administrative privileges to create, modify, and delete throttling configurations. This feature is available on PA-RISC and Itanium-based systems.
• 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

• HP Threshold Indications generated by EMS High Availability monitors are supported on PA-RISC and Itanium-based systems. These indications include the following fields, which are in addition to the fields available in the indications generated by the EMS Hardware Monitors:
  • ObservedValue
  • PerceivedSeverity
  • ProviderName
  • SystemName
  • ThresholdIdentifier
  • ThresholdValue
• The throttling configuration feature is supported on PA-RISC-based systems.
• The Log Viewer component is available on PA-RISC-based systems also.
• 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 search criteria.

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.

System Requirements

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

• PA-RISC-based servers
  • rp3410
  • rp3440
  • rp4410
  • rp4440
  • rp7400
  • rp7410
  • rp7420
  • rp7440
  • rp8400
  • rp8420
  • rp8440
  • SD16, SD32, SD64
  • SD16A, SD32A, SD64A
  • SD16B, SD32B, SD64B
  • 9000/800/A400-44
  • 9000/800/A400-6x
  • 9000/800/A500-7x
  • 9000/800/L1000-36
  • 9000/800/L2000-36
  • 9000/800/L1500-7x
  • 9000/800/L1500-8x
  • 9000/800/L3000-6x
  • 9000/800/L3000-7x
  • 9000/800/L3000-8x
• Itanium-based servers
  • cx2600
  • cx2620
  • rx1600
  • rx1620-2
  • rx2600
  • rx2620 based on Intel Itanium processor with Hyper Threading and Dual Core
  • rx2620-2
  • rx2660
  • rx3600
  • rx4640 based on Intel Itanium processor with Hyper Threading and Dual Core
  • rx5670
  • rx6600
  • rx7620
  • rx7640
  • rx8620
  • rx8640
  • rx9610
  • SD16A, SD32A, SD64A
  • SD16B, SD32B, SD64B
  • BL60p
  • BL860c based on Intel Itanium processor with Hyper Threading and Dual Core
  • Integrity Virtual Machine

Following lists the software requirements for using SFM:

• May 2005 HP-UX 11iv2 Operating Environment (OEUR) or later
• QPKBASE B.11.23.0706.064 Base Quality Pack Bundle for HP-UX 11i v2, September 2006
• OpenSSL A.00.09.07e.013 or later
• SysMgmtWeb version A.2.2.5 (HP-UX Web-Based System Management User Interface)
• WBEMServices A.02.05.04 WBEM Services CORE Product
• OnlineDiag version B.11.23.09.xx

Notes:

• SysMgmtWeb is optional. However, you will not be able to access EVWEB GUI if SysMgmtWeb is not installed on the system. SysMgmtWeb, WBEMServices A.02.02.05, and Online Diagnostics are available on the Operating Environment (OE) media.
• HP recommends that you install HP Systems Insight Manager (HP SIM) version C.05.01.00.01.xx 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

• If the default log directory is deleted, log messages are not logged. A message is logged in syslog stating that the SFM log file could not be opened. Only a root user can remove this directory. HP recommends that users do not delete this default log directory.
• 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.
• The errors processed by the SFMIndicationProvider cannot be sent to the EMS monitors when you switch from the SFMIndicationProvider to EMS monitors.

Known Problems and Workarounds

• JAGag34537 - SFM monitoring mode not retained after operating system upgrade.
  Symptom: SFM native indications are not generated from the SFMIndicationProvider after an upgrade to the 0706 version of OE.
  Problem: EMS is the default monitoring mode after an OE upgrade.
  Cause: In the OE update path, the monitoring mode is switched to EMS during upgrade. However, the monitoring mode is not reverted to SFM after the upgrade is completed.
  Workaround: After the OE upgrade, enter the following command at the HP-UX prompt to switch to the SFM mode manually:
  # /opt/sfm/bin/sfmconfig -w -s

  The following output 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 and EMS hardware monitors will be shutdown.

• JAGag36044 - Serial and part numbers for DIMMs are not displayed; 4GB cap blank; slots incorrect.
  Symptom: Serial and part numbers for DIMMs are not displayed in the memory property pages.
  Problem: On the following systems based on PA-RISC processors and sx2000 chipset, SFM does not support serial and part numbers:
  
  • SD16B
  • SD32B
  • SD64B
  However, SFM supports the display of 4GB DIMMs.
  Workaround: Complete the following steps to retrieve information from the 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 D to select a DIMM.
  6. Enter the cell number.
  7. Enter the DIMM location.
     All the details of the memory module are displayed. The following is a sample output:
     

     The Entity you have selected is DIMM
     FRU ID Definition Revision     : A
     Artwork Revision               : A4
     Engineering Date Code          : 4224
     Part Number                    : A6802-60001
     Serial Number                  : A56E03907459
     FRU Name                       :         DIMM_256
     Scan Revision                  : 0x100
     FRU Specific Information       :               MK
     Manufacturing and Test History :
     Field 0 0xa00002111905010000
     Field 1 0x000000000000000000
     Field 2 0x000000000000000000
     Field 3 0x000000000000000000
     Field 4 0x000000000000000000
     Field 5 0x000000000000000000
     Field Spare 0x0000

• JAGag36284 - SFM incorrectly reports power status on rx3600 and rx6600 systems.
  Symptom: The temperature and power status are reported as OK.
  Problem: The indication providers or the EMS Hardware Monitors generate events indicating that the temperature and power devices are removed. However, the system property pages display the status as OK.
  Cause: SFM does not support reading the temperature and power sensors on rx3600 and rx6600 systems.
  Workaround: Complete the following steps to retrieve information from the 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. Select the desired option.
     All the details of the selected device are displayed.
• JAGag36913 - Core file from 'cimprovagt' created during an OE update on PA-RISC-based systems
  Symptom: SFM dumps core in /var/opt/wbem/ during an OE update.
  Cause: Data corruption in CIMOM.
  Workaround: Remove the dump. Shortly after, SFM starts functioning properly.

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          B.04.00.06.xx  HPUX System Fault Management

• Product(s)
  

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

• Sub-product(s)
  

  $ swlist -l subproduct -s <SysFaultMgmt Depot Location>
  
  # SFM-CORE                      B.04.00.06     HPUX System Fault Management
    SFM-CORE.ERROR-MGMT           Error Management Technology
    SFM-CORE.EVWEB
    SFM-CORE.FMD-PROVIDER         FMD-PROVIDER
    SFM-CORE.GS                   GS
    SFM-CORE.HS-PROVIDER          HS-PROVIDER
    SFM-CORE.SFM-HAS              SFM-HAS
    SFM-CORE.SFM-PROVIDER         SFM-PROVIDER
    SFMDB                         B.04.00.06     HP System Management Database (SFMDB)

• Fileset(s)
  

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