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:
Note: EVWEB is a new tool included in the SFM bundle.
- SFM Providers
- EVWEB
This document contains the following sections:
- SFM Providers
- EVWEB
- What Is EVWEB
- Benefits
- Features
- Limitations
- System Requirements
- Supported Browsers
- Known Issues
- 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-to-WBEM 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. Following are the new providers added in this release:
- FMD Provider
- Environmental Providers
Changes in the existing SFM providers for this release are as follows:
- CPU Instance Provider
- CPU Instance Provider now supports Dual core processors, such as, PA RISC 8800, PA RISC 8900 (+), and HP MX2 dual processor modules (Itanium). The CPU Instance Provider data sheet describes how information on dual-core processors is reported.
- CPU Instance Provider supports HP servers with Virtual Partitions (vPars).
- CPU Instance Provider reports inventory information for deconfigured processor modules.
- CPU Instance Provider now reports information about empty processor slots and processor slots that are mounted with processor modules.
- Consolidated health status of the processor subsystem is now available.
- CPU Provider now reports the serial number, part number, and model string for processors on platforms where the same information is available.
- The physical location of processor devices is now represented differently. For more information, see the CPU Provider Data Sheet at:
http://www.docs.hp.com/en/diag
- Memory Provider
- Single bit error condition of the Dual Inline Memory Module (DIMM) is restored when the CIMOM restarts.
- Consolidated health status of the memory subsystem is provided.
- The physical location of memory devices is now represented differently. For more information, see the Memory Provider Data Sheet at:
http://www.docs.hp.com/en/diag- Memory Provider now reports the serial number and part number for DIMMs on all supported platforms.
Supported EMS Hardware Monitors
The following Event Monitoring Service (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)
- 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 v2 operating system:
Defect Fixes
- 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)
- JAGaf34591
Problem
Monitors do not remain disabled after they are disabled using the monconfig request manager. Shortly after the hardware monitors are disabled by issuing the " kill" command in the monconfig request manager, some monitors restart despite the monconfig request manager stating that " Event Monitoring is currently disabled" . This behaviour is caused due to a problem in the mechanism used by the EMS Wrapper Provider to register with the Event Monitoring Service (EMS) framework.
Resolution
This problem is fixed.- JAGaf80165
Problem
Request to retrieve information from the CPU Instance Provider, Memory Instance Provider, and the Environmental Provider may time out on some platforms. This is because providers are slow in gathering inventory information. Also, providers do not inform the client that the inventory information is being gathered.
Resolution
This problem is fixed. Providers do not timeout anymore. Instead, a message is displayed on the client system that states " Inventory is being built currently. Please try after some time" . Once the inventory information is gathered, providers respond with requested information to the client when subsequent requests are made.
Note: After installation of the SFM product, the first request to any provider for information related to various devices is slow. Subsequently, requests are quick (even after a reboot).EVWEB
This section describes 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:
Benefits
- 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.Following lists the benefits of EVWEB:
Features
- 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.
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.
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. The readability or formatting will be enhanced in a future release.
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/L" 150" 0-7x
- 9000/800/L" 150" 0-8x
- 9000/800/L3000-6x
- 9000/800/L3000-7x
- 9000/800/L3000-8x
- Itanium-based servers
- cx2600
- cx2620
- rx1600
- rx1620-2
- rx2600
- rx2620
- rx2620-2
- rx3600
- rx4640
- rx5670
- rx6600
- rx7620
- rx7640
- rx8620
- rx8640
- SD16A, SD32A, SD64A
- SD16B, SD32B, SD64B
- BL60p
- Integrity Virtual Machine
Following lists the software requirements for using SFM:
Note:
- May 2005 HP-UX 11i v2 Operating Environment Update Release (OEUR) or later
- QPKBASE B.11.23.0603.040a Base Quality Pack Bundle for HP-UX 11i v2, March 2006
- OpenSSL Version A.00.09.07e.013 or later
- WBEM Services Version A.02.00.09 or later
- PHKL_32653 (diag 2) kernel patch
- SysMgmtWeb version A.2.2.2 (HP-UX Web Based System Management User Interface)
- OnlineDiag B.11.23.06.xx
- 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 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.
- When HP WBEM Services is shutting down and WBEM indications are generated simultaneously, CIMOM may produce a core and terminate.
- 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.
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
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.01.00.xx.yy HPUX System Fault Management- Product(s)
$ swlist -l product -s <SysFaultMgmt Depot Location> SFM-CORE B.01.00.xx HPUX System Fault Management SFMDB B.01.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 B.01.00.xx HP System Management Database (SFMDB)- Fileset(s)
$ swlist -l fileset -s <SysFaultMgmt Depot Location> # SFM-CORE B.01.00.xx HPUX System Fault Management SFM-CORE.HS_PRO_COREIA B.01.00.xx HealthState Instance Provider Platform Specific Fileset SFM-CORE.HS_PRO_COREPA B.01.00.xx HealthState Instance Provider Platform Specific Fileset SFM-CORE.CTR_PRO_COMM B.01.00.xx Control Provider Common Fileset SFM-CORE.CTR_PRO_COREIA B.01.00.xx Control Provider Platform Specific Fileset SFM-CORE.CTR_PRO_COREPA B.01.00.xx Control Provider Platform Specific Fileset SFM-CORE.EMT_COMM B.01.00.xx EMT Common components SFM-CORE.EMT_COREIA B.01.00.xx EMT core platform specific fileset SFM-CORE.EMT_COREPA B.01.00.xx EMT core platform specific fileset SFM-CORE.EVWEB_COMM B.01.00.xx Event Manager (EvWEB) Common components SFM-CORE.EVWEB_COREIA B.01.00.xx EvWEB core platform specific fileset SFM-CORE.EVWEB_COREPA B.01.00.xx EvWEB core platform specific fileset SFM-CORE.EVWEB_DOC B.01.00.xx EvWEB Online help fileset SFM-CORE.EVWEB_GUI_COMM B.01.00.xx EvWEB GUI common fileset SFM-CORE.EVWEB_GUI_IA B.01.00.xx EvWEB GUI platform specific fileset SFM-CORE.EVWEB_GUI_PA B.01.00.xx EvWEB GUI platform specific fileset SFM-CORE.EVWEB_MAN B.01.00.xx EVWEB Man pages fileset SFM-CORE.FMD_PRO_COMM B.01.00.xx Filter Metadata Instance Provider Common Fileset SFM-CORE.FMD_PRO_COREIA B.01.00.xx Filter Metadata Instance Provider Platform Specific Fileset SFM-CORE.FMD_PRO_COREPA B.01.00.xx Filter Metadata Instance Provider Platform Specific Fileset SFM-CORE.GS_COMM B.01.00.xx General Services Common Fileset SFM-CORE.GS_COREIA B.01.00.xx General Services Platform Specific Fileset SFM-CORE.GS_COREPA B.01.00.xx General Services Platform Specific Fileset SFM-CORE.HAS-IA B.01.00.xx Hardware Access ServicesIA SFM-CORE.HAS-PA B.01.00.xx Hardware Access Services PA SFM-CORE.MISC_COMM B.01.00.xx MISC Common Fileset SFM-CORE.MISC_COREIA B.01.00.xx MISC Platform Specific Fileset SFM-CORE.MISC_COREPA B.01.00.xx MISC Platform Specific Fileset SFM-CORE.SFM_PRO_COMM B.01.00.xx SysFaultMgmt Provider Module COMMON SFM-CORE.SFM_PRO_IA B.01.00.xx SysFaultMgmt Provider Module IA SFM-CORE.SFM_PRO_PA B.01.00.xx SysFaultMgmt Provider Module PA # SFMDB B.01.00.xx HP System Management Database (SFMDB) SFMDB.SMPGSQL-DOC B.01.00.xx PostgreSQL (SFMDB) Documentation Files SFMDB.SMPGSQL-INC B.01.00.xx PostgreSQL (SFMDB) Header Files SFMDB.SMPGSQL-LIB B.01.00.xx PostgreSQL (SFMDB) Library Files (Architecture dependent) SFMDB.SMPGSQL-LIB B.01.00.xx PostgreSQL (SFMDB) Library Files (Architecture dependent) SFMDB.SMPGSQL-MAN B.01.00.xx PostgreSQL (SFMDB) Manual Pages SFMDB.SMPGSQL-RUN B.01.00.xx PostgreSQL (SFMDB) Executable Files (Architecture dependent) SFMDB.SMPGSQL-RUN B.01.00.xx PostgreSQL (SFMDB) Executable Files (Architecture dependent) SFMDB.SMPGSQL-SHA B.01.00.xx PostgreSQL (SFMDB) Share File SFMDB.SMPGSQL-SRC B.01.00.xx PostgreSQL (SFMDB) Source FilesReporting 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.