Support Tools (logo)

System Fault Management: Installation

System Fault Management (SysFaultMgmt) is a collection of tools for monitoring the health of HP servers and getting information about hardware, such as memory and CPU. These tools operate within the Web-Based Enterprise Management (WBEM) environment.

NOTE: For information about SysFaultMgmt installation on HP-UX 11i v1, click here.

Contents

For the latest and most complete information, see the "System Fault Management" section on the Diagnostics Homepage at http://docs.hp.com/hpux/diag/index.html.

Requirements

The following software is required for SysFaultMgmt:

Installation

To install the SysFaultMgmt bundle:

  1. If desired, check whether the server is supported by the CPU and Memory Providers. (The CPU and Memory Providers support a sub-set of servers running this OS, The EMS Wrapper Provider supports all servers running this OS.)

    For a list of supported systems, refer to the Release Notes in the "System Fault Management" section on the Diagnostics Homepage at http://docs.hp.com/hpux/diag/index.html. You can find out the server name with the "model" command "model -V" for the hversion).

  2. Make sure that the required software is loaded:
    • HP WBEM Services V2.0 and upwards
    • HP Systems Insight Manager (SIM) V4.1 and upwards (or other network management application compatible with HP WBEM services V2.0). HP SIM is required on the server managing the network, not on the server being monitored.
    If you are not familiar with WBEM and HP Systems Insight Manager, refer to the SysFaultMgmt Product Overview webpage (available on the HP Software Depot webpages and on the "System Fault Management" section of the Diagnostics Homepage.)

  3. Make sure that the OnlineDiag bundle is installed on your computer. This bundle should have been installed when the operating system was installed. (The OnlineDiag bundle contains the EMS core and EMS hardware monitors that are required by the EMS Wrapper Provider.)

    To verify that the OnlineDiag bundle is installed, enter the command:
    swlist | grep OnlineDiag
    
    If the OnlineDiag bundle is not installed, install the most current version (available through HP Software Depot).

  4. Verify that you have the correct version of EMS (A.04.00 or upwards), by entering the command:
    /etc/opt/resmon/lbin/monconfig
    
    Sample output:
     
    ============================================================================
    ===================       Event Monitoring Service       ===================
    ===================      Monitoring Request Manager      ===================
    ============================================================================
    
      EVENT MONITORING IS CURRENTLY ENABLED.
      EMS Version : A.04.00 
      STM Version : A.40.00
    
  5. Look at the EMS and STM version numbers in the monconfig display to see whether you need to load a new version of OnlineDiag:
    • HP strongly recommends you install the latest version of OnlineDiag for your operating system to ensure you have up-to-date functionality for all devices.
    • The minimum version for OnlineDiag on HP-UX , but newer versions may be required for some platforms.
    • The minimum EMS version is A.04.00 or upwards.
    You can obtain the the most current version of the OnlineDiag bundle through HP Software Depot. Install the entire bundle.
    (For more information on STM and EMS versions, see Finding your version number and Table of versions.)

  6. Go to the Software Depot website at http://www.hp.com/go/softwaredepot. Product and installation information is available for SysFaultMgmt on that site. (SysFaultMgmt is only available online.)
    The exact path is: http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=SYSFAULTMGMT. The product ID (number) is SYSFAULTMGMT, and the product is listed under the category of "high availability."

  7. At the Software Depot site, download the SysFaultMgmt.depot, and copy it to the machine on which the product is to be installed.

  8. There is only one bundle. The appropriate filesets are selected, depending upon the type of machine.
  9. Use the swinstall command to install the depot, using the complete path for the depot filename:
    swinstall -s FULLY_QUALIFIED_DEPOT_FILENAME   SysFaultMgmt
    

    NOTE:SysFaultMgmt is always the software to be entered in this command line.

    For example, if the depot is in the /tmp directory, you would enter one of the following commands.

    For all servers:
    swinstall -s /tmp/SysFaultMgmt.depot SysFaultMgmt 
    
    HP recommends that you install all the products in the bundle. Do not do a partial install.

Verification

You can verify that SysFaultMgmt has been installed correctly in several ways:

Using HP Systems Insight Manager (SIM)

To view the information from the providers, you use a WBEM-based network management application, such as HP Systems Insight Manager (SIM).

For a description of the configuration and use of HP SIM for SysFaultMgmt, see the "System Fault Manager: Operating Guide" at http://docs.hp.com/hpux/onlinedocs/diag/sfm/sfm_oper.htm.
If you are using a different network management application, refer to the documentation for it instead.

Effective use of SysFaultMgmt requires a familiarity with HP Systems Insight Manager. Refer to the extensive documentation and training available at websites such as:

Patches

You can load the patches in one of three different ways:

Method 1: Entire patch bundle. Install the entire HW or HWCR patch bundle for your system. Advantages: simple and tested process. Disadvantages: the bundle can be many megabytes in size.

Choose the Hardware Critical (HWCR) or Hardware (HW) patch bundle appropriate for your system. For example, choose XSWHWCR1100 for a Series 800 system running HP-UX 11.00.

The patch bundles are distributed via the HP Software Depot website. The procedure for using swinstall to load the patches is described in Chapter 5 of the "Support Plus: Diagnostics Users Manual."

Method 2: Individual patches from bundle. Install ONLY the individual patches required for your system from the HW or HWCR patch bundle described above. Advantages: Small number of patches. Disadvantages: Requires knowledge of SD (swinstall) to select patches (interactive selection or command line selection).

Method 3: Individual patches from website. You can also obtain the patches through the HP IT Resource Center (http://us.itrc.hp.com). A problem with loading individual patches from this website is that a system reboot is required for every patch that requires a reboot (patches to the kernel, indicated by "PHKL" in the patch name, all require a reboot).

Configuring SysFaultMgmt Logging

Currently only logging-related configuration can be changed for SystFaultMgmt. In general, HP recommends that you keep the default configurations for SysFaultMgmt and the providers as they come from the factory.

If desired, you can change the logging threshold or specify a new logfile.

To configure logging for SysFaultMgmt:

  1. With an ASCII editor, call up the configuration file /opt/sfm/conf/FMLoggerConfig.xml. The contents of the file should appear similar to the following:
    <SFMConfig>
        <LoggerConfig>
                    <Severity> WARNING </Severity>
                    <Target> /opt/sfm/log/sfm.log </Target>
            </LoggerConfig>
    </SFMConfig>
    
  2. To modify the threshold logging level, change the Severity value. In increasing level of severity, the possible values are:
    INFORMATIONAL
    WARNING (default)
    ERROR
    CRITICAL
    

    CAUTION
    HP suggests that you not set the threshold to INFORMATIONAL, except perhaps temporarily. The INFORMATIONAL setting can generate many messages and use a sizable amount of disk space.

  3. To specify a new logfile, change the Target value. The possible values are: STDOUT (all log messages are delivered to console) or the complete path to the file where the log messages are to be written. The default logfile is /opt/sfm/log/sfm.log. (The path to the logfile should already exist and should be writable by root-user).

  4. After you have finished editing the configuration file, run the /opt/sfm/bin/fmControl program, to specify the changed configuration file. Specify the complete path of the configuration file. For example:
    $ /opt/sfm/bin/fmControl /opt/sfm/conf/FMLoggerConfig.xml
    

Removing SysFaultMgmt

If you wish to remove the SysFaultMgmt product after it has already been installed, type:

swremove SysFaultMgmt     

Further Information

For the latest and most complete information, see the "System Fault Management" section on the Diagnostics Homepage at http://docs.hp.com/hpux/diag/index.html.

For release-specific information (for example, a list of systems supported by a particular release of SysFaultMgmt), see the release notes for that release. The release notes can be viewed at the Diagnostics Homepage, or by looking at the ASCII file REL-NOTES.SFM in the directory /opt/sfm, available after the bundle is installed.


Top of Page

/ Diagnostics HOME


URL: http://docs.hp.com/hpux/onlinedocs/diag/sfm/sfm_inst.htm
Last updated:Wednesday July 06