Release Notes for EMS Hardware Monitors on HP-UX 11i v2 (11.23) (December 2007)

• Online Diagnostics
• Required and Recommended Patches
• Loading Patches
• EMS Hardware Monitors Overview
• Configuring Hardware Monitoring
• Changes
• Known Problems
• Monitors Provided
• Product Documentation
• SD Product Structure
• Reporting Defects

Online Diagnostics

The Online Diagnostics software is a collection of tools that enables you to monitor and test server hardware. It comprises the Event Monitoring Service (EMS) framework, the EMS Hardware Monitors, and the Support Tools Manager (STM).

The Online Diagnostics tools are all contained in a Software Depot (SD) bundle, called the OnlineDiag bundle. This bundle is distributed in the following ways:

• OE media
• HP Software Depot Web site

The following generic command lists various levels of content of the depot:

swlist -l <level> -s /<mount_point>/DIAGNOSTICS/<os_release>

where <level> 
         = bundle       Bundle level listing
         = product      Product level listing
         = subproduct   Sub-product level listing
         = fileset      File set listing

      <mount_point>     Location where the CD file system
                        is mounted.

      <os_release>      The OS contents of the depot.
         = B.11.00

For OnlineDiag on HP-UX 11i v2 December 2007 release, the following apply:

• Online Diagnostics supports the BL870C HP Server Blade.
• All diagnostic defect repairs and enhancements as of August 2007, are included. Any future patches dated after August 2007 must be loaded after this version of OnlineDiag.
• The new hardware resources in all active releases as of September 1, 2007 are supported.
• Online Diagnostics is updated to monitor PCI Express events on the following HP Integrity systems:
  • rx7640
  • rx8640
  • SD16B
  • SD32B
  • SD64B

---

Required and Recommended Patches

For the HP-UX 11i v2 December 2007 release, the following patch is included in the HWEnable11i bundle of the OE media:

• PHKL_32653 (diag2)

The PHKL_32653 (diag2) patch is required to support the information tool for PCI cards on Itanium-based systems. Also, Online Diagnostics on Itanium-based vPar systems require this patch.

The patch bundles are available at the following locations:

• OE media
• HP Software Depot Web site

---

Loading Patches

You can install the patches in one of the following ways:

Method 1:
Install the entire Hardware Enablement Bundle (HWE) or Quality Pack (QPK) patch bundle for your system. This is a simple and tested process. However, the volume of the patch bundle can be big.

Method 2:
Install only the individual patches required from the patch bundle available on the OE media. This method is advantageous because the size of the patches is small. However, you must select and install patches manually.

Method 3:
Install individual patches from the HP IT Resource Center at:
http://us.itrc.hp.com/

Notes:

• After installing individual patches from the HP IT Resource Center, you must restart your system.
• You must install the patches mentioned before installing Online Diagnostics.

---

EMS Hardware Monitors Overview

EMS Hardware Monitors are a set of tools for maintaining system availability. They enable you to monitor the operation of a wide variety of hardware resources and be alerted immediately if any failure or other unusual event occurs.

Hardware event monitoring provides a high level of protection against system hardware failure. By using hardware event monitoring, you can eliminate the most undetected hardware failures that could interrupt system operation or cause data loss.

---

Configuring Hardware Monitoring

The EMS Hardware Monitors are installed at the same time as STM. Once the monitoring software is installed, monitoring is automatically enabled.

By default, events with severity levels MAJOR WARNING, MINOR WARNING, SERIOUS, or CRITICAL that are generated by the monitors are notified in the following ways:

• Written to /var/adm/syslog/syslog.log
• Sent to the superuser's E-mail address.

All events generated by all the monitors are stored in the /var/opt/resmon/log/event.log file.

To configure, enable, or disable hardware event monitoring, run the /etc/opt/resmon/lbin/monconfig monitoring request manager.

The Peripheral Status Monitor (PSM) and the Kernel Resource Monitor (krmond) are configured differently. They use the EMS GUI. For more information, see:
http://docs.hp.com/en/diag/ems/ems_gui.htm

---

Changes

Changes made to the EMS Hardware Monitors for the December 2007 release include the following:

• Changes to the monconfig Tool
• Changes to Monitors
• Changes to Platform and Interface
• Customer-Viewable Interface Changes

• Changes to the monconfig Tool
  This section describes the changes made to the monconfig tool.

  The swlist command executed by the monconfig tool to retrieve the EMS version on the system may abort during the installation of a product. This problem is fixed. The monconfig tool operation is made independent of the swlist command. The tool achieves similar results using an alternate method. However, there is no change in the interface for this fix.

• Changes to Monitors
  This section describes the changes made to individual monitors. Monitors are listed in alphabetical order.
  • Chassis Code Monitor (dm_chassis)
    
    • Not applicable
  • CMC Monitor (cmc_em)
    • Not applicable
  • Core Hardware (dm_core_hw)
    
    • Not applicable
  • Core Hardware for Itanium (ia64_corehw)
    The following change applies to Itanium-based systems only:
    • JAGag45975
      The ia64_corehw monitor does not create the /tmp/wd_action.dbg debugging file anymore.
    The following change applies to PA-RISC-based and Itanium-based systems:
    • JAGag35925
      The ia64_corehw monitor may not generate events during the system boot, because the Get Sensor Reading IPMI command fails. This problem is fixed.
  • Core Hardware Monitor - Asama (ipfcorehw_asama)
    • Not applicable
  • Core Hardware Monitor - Hitachi (ipfcorehw_hitachi)
    • Not applicable
  • CPE Monitor (cpe_em)
    
    • JAGag46079
      The cpe_em monitor supports the HP Integrity BL870c Server Blade.
  • CPU Monitor (lpmc_em)
    The following changes apply to HP 9000 systems only:
    • JAGag33954
      On vPar systems that are managed by the Global Workload Manager (gWLM), the lpmc_em monitor generates Event 100 and Event 101 if gWLM adds or deletes processors. The monitor is modified to prevent it from generating these events.
    • JAGag45237
      While taking Dynamic Processor Resilience (DPR) action on a faulty processor, the lpmc_em monitor activates additional iCAP processors. This problem is fixed.
  • CPU Monitor - Hitachi (cmc_em_hitachi)
    • Not applicable
  • Disk Array FC60 Monitor (fc60mon)
    • Not applicable
  • Disk Monitor (disk_em)
    • Not applicable
  • DS2500 Enclosure Monitor (gazemon)
    • Not applicable
  • Fibre Channel Adapter (dm_ql_adapter)
    • Not applicable
  • Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter)
    • Not applicable
  • Fibre Channel Switch (dm_fc_sw)
    • Not applicable
  • Forward Progress Log (FPL) Monitor (fpl_em)
    
    • JAGag45618
      The fpl_em monitor generates events for old entries in the Forward Process Log (FPL). This is because the IPMI command fails with the completion code 0xcb (Requested record not present). As a result, the ia64_corehw monitor re-reads the FPL. This problem is fixed.
  • High Availability Disk Array Monitor (ha_disk_array)
    • Not applicable
  • High Availability Storage System (dm_ses_enclosure)
    • Not applicable
  • iSCSI Driver Subsystem Monitor (dm_iscsi_adapter)
    • Not applicable
  • Kernel Resource Monitor (krmond)
    • Not applicable
  • Memory (dm_memory)
    • Not applicable
  • Memory IA64 (memory_ia64)
    • Not applicable
  • Memory Monitor -- Hitachi (ipfmemory_hitachi)
    • Not applicable
  • MSA1000/MSA30 Storage Disk Array Monitor (msamon)
    The following change applies to HP 9000 and Itanium-based systems:
    • The msamon monitor logs Parm Page Get Failure information in the api.log file when either MSA1000, or MSA1000 and MSA1500 devices are connected to the system. Over a period of time, this information can overwrite other important information in the api.log file. This problem is fixed. The msamon monitor is modified to prevent the monitor from logging this information in the api.log file.
  • Peripheral Status Monitor (psmmon)
    • Not applicable
  • RAID Adapter (dm_raid_adapter)
    • Not applicable
  • Remote Monitor (RemoteMonitor)
    • Not applicable
  • SCSI Disk Monitor (scsi_disk)
    
    • Not applicable
  • System Status Monitor (sysstat_em)
    
    • Not applicable
  • UPS Monitor (dm_ups)
    
    • Not applicable
• Changes to Platform and Interface
  • Not applicable
• Customer-Viewable Interface Changes
  • Not applicable

---

Known Problems

• If System Fault Management (SFM) is installed on your system, you must complete the following steps before and after installing Online Diagnostics.
  1. To shut down the SFM subsystem, enter the following command at the HP-UX prompt:

            # /sbin/init.d/cimserver stop

  2. Install Online Diagnostics.
  3. To restart the SFM subsystem after the installation is completed, enter the following command at the HP-UX prompt:

            # /sbin/init.d/cimserver start

• If the maxssiz_64bit kernel parameter is set below the default value of 0x800000, it can cause the lpmc_em monitor to abort.
• The Memory Page Deallocation (MPD), which runs on most current HP-UX systems, does not work on rx4610 systems. The activity log for memlogd includes a message that reads unsupported device.
  MPD cannot be implemented on the rx4610 system because the system's design does not allow the memlogd daemon to run on it.
• You cannot access online help on Itanium-based systems.
  Cause: You require a browser to view online help using the cstm, mstm, and xstm interfaces. The default supported browser is Mozilla. If you are using any other browser, you must configure STM for the interfaces.
  Note: You do not require a browser to access online help on PA-RISC-based systems.
  Action:
  To configure the browser for the xstm and mstm interfaces, complete the following steps:
  
  1. To start xstm, enter the following command at the HP-UX prompt:
     # /usr/sbin/xstm
  2. Select Options->General Options.
  3. Enter the full path of the browser.
  4. Click OK.
     The browser is configured.
  To configure the browser for the cstm interface, complete the following steps:
  1. Enter the following command at the HP-UX prompt.
     # gop
     A list of options is displayed.
  2. Select the appropriate options.
  3. Select the browser of your choice.
     The browser is configured.
  Note: You can also view online help for xstm, mstm, and cstm at:
  http://www.docs.hp.com/en/diag/stm/sth_summ.htm

---

Monitors Provided

For HP-UX 11i v2 December 2007 release, the following monitors are provided:

• CMC Monitor (cmc_em)
• Core Hardware (dm_core_hw)
• Core Hardware for Itanium (ia64_corehw)
• Core Hardware Monitor -- Asama (ipfcorehw_asama)
• Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi)
• CPE Monitor (cpe_em)
• CPU Monitor (lpmc_em)
• CPU Monitor -- Hitachi (cmc_em_hitachi)
• Disk (disk_em)
• Disk Array FC60 (fc60mon)
• DS2500 Enclosure Monitor (gazemon)
• Emulex PCI-e Fibre Channel Mass Storage Adapter (dm_fclp_adapter)
• Fibre Channel Adapter (dm_ql_adapter)
• Fibre Channel Adapter Model A5158 (dm_TL_adapter)
• Forward Progress Log (FPL) Monitor (fpl_em)
• High Availability Disk Array (ha_disk_array)
• High Availability Storage System (dm_ses_enclosure)
• iSCSI Driver Subsystem Monitor (dm_iscsi_adapter)
• Kernel Resource Monitor (krmond)
• Memory (dm_memory)
• Memory IA64 (memory_ia64)
• Memory Monitor -- Hitachi (ipfmemory_hitachi)
• MSA1000/MSA30 Storage Disk Array Monitor (msamon)
• Peripheral Status Monitor (psmmon)
• RAID Adapter (dm_raid_adapter)
• Remote Monitor (RemoteMonitor)
• Serial-Attached SCSI (SAS) Mass Storage Adapter monitor (dm_sas_adapter)
• SCSI Disk Monitor (scsi_disk)
• System Status (sysstat_em)
• UPS (dm_ups)

The following monitors are NOT provided:

• dm_FCMS_adapter
• Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
• fw_disk_array: hardware not supported on the system
• scsi123_em: hardware not supported on the system

For detailed information about the products and the monitors supporting them, and additional dependencies, see the Online Diagnostics Administrator's and User's Guide at:
http://docs.hp.com/en/diag/

---

Product Documentation

For the latest and most complete information on EMS Hardware Monitors and the STM, see the documentation of Online Diagnostics at:
http://docs.hp.com/en/diag/

For information on STM, see the STM Release Notes at:
/usr/sbin/stm/Rel_NOTES.STM

---

SD Product Structure

Following are the components of the OnlineDiag bundle:

SD Bundle: OnlineDiag
   Description: On-line Diagnostic System (Series 800/700)

   SD PRODUCT: Sup-Tool-Mgr
      Description: Support Tools Manager for HP-UX Systems

      SD SUB-PRODUCT: Manuals
      Description: Support Tools Manager Manual Pages

         FILESET: RELEASE_NOTES
            Description: HPUX STM Release Notes

         FILESET: STM-MAN
            Description: HPUX STM Manual Pages

      SD SUB-PRODUCT: Runtime
      Description: STM Manual Runtime

         FILESET: STM-CATALOGS
            Description: HPUX STM Shared Libraries

         FILESET: STM-SHLIBS
            Description: HPUX STM Shared Libraries

         FILESET: STM-UI-RUN 
            Description: HPUX STM User Interface
         
         FILESET: STM-UUT-RUN
            Description: HPUX STM Unit Under Test Runtime 

   SD PRODUCT: EMS-Config
      Description: EMS Config

         FILESET: EMS-GUI
            Description: Event Monitoring Service Graphical 
                         User Interface

   SD PRODUCT: EMS-Core
      Description: EMS Core Product

         FILESET: EMS-CORE
            Description: Event Monitoring Service Core Files

---

Reporting Defects

You can report defects and send suggestions to diag.onlinediag.docs using CHART. If you do not have access to CHART, contact your local HP representative to file a defect on your behalf.

/ Diagnostics HOME