Release Notes for EMS Hardware Monitors on HP-UX 11.23 (March 2006)

• Overview
• Configuring Hardware Monitoring
• Changes
• Known Problems
• Monitors Provided
• Monitor Dependencies
• Additional Support
• Product Documentation
• SD Product Structure
• Reporting Defects

This release notes reflects the changes made to the EMS Hardware Monitors for HP-UX 11.23, March 2006 release.

Note: No tape drives are supported by Online Diagnostics on HP-UX. Although some of the Support Tools Manager (STM) tools may function with tape drives, they are not supported. The diagnostic tools and utilities that support these devices are HP StorageWorks Library and Tape Tools (L and TT). These tools are available at http://www.hp.com/support/tapetools.

Overview

Included with the OnlineDiag bundle of support tools are the EMS Hardware Monitors - an important tool for maintaining system availability. The EMS Hardware Monitors allow 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 the Support Tools Manager (STM). Once the monitoring software is installed, monitoring is automatically enabled.

By default, event messages with severity levels major, warning, serious and critical generated by the monitors will be conveyed in the following ways:

• Written to /var/adm/syslog/syslog.log
• Sent to EMAIL address root

All events will be stored in /var/opt/resmon/log/event.log file.

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

The Peripheral Status Monitor (PSM) and the Kernel Resource Monitor (krmond) are configured differently. They use the Event Monitoring Service (EMS) Graphical User Interface (GUI). See: http://docs.hp.com/en/diag/ems/ems_gui.htm

Changes

Changes made to the EMS Hardware Monitors for the the March 2006 release include the following:

• Changes to Monitors
• Changes to Platform and Interface
• Customer-viewable Interface Changes

• 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)

    The following change applies to systems running on the PA-RISC platform:

    • JAGaf80771
      Problem: The monitor does not deallocate the file descriptors in certain failure conditions.
      Solution: The monitor now deallocates the file descriptors in all conditions.

  • Core Hardware for Itanium (ia64_corehw)

    The following change applies to systems running on the Itanium platform:

    • JAGaf79895
      Problem: The monitor does not report events to the syslog when the temperature crosses the safety limit, on some systems.
      Solution: The monitor now reports events to the syslog when the temperature crosses the safety limit, on all systems.

    The following change applies to systems running on either the Itanium platform or the PA-RISC platform:

    • JAGaf83091
      Problem: Events whose severity is Information are incorrectly reported.
      Solution: The client configuration file of the fpl_em monitor is modified. Severity of events is now reported as Information, if applicable.

  • Core Hardware Monitor -- Asama (ipfcorehw_asama)
    • Not applicable

  • Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi)
    • Not applicable

  • CPE Monitor (cpe_em)
    • Not applicable

  • CPU Monitor (lpmc_em)
    • Not applicable

  • CPU Monitor -- Hitachi (cmc_em_hitachi)
    • Not applicable

  • Disk Array FC60 Monitor (fc60mon)

  • Disk Monitor (disk_em)
    • Not applicable

  • Fibre Channel Adapter (ql_adapter)
    • Not applicable

  • Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter)
    • Not applicable

  • Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
    • Not applicable

  • Fibre Channel Switch (dm_fc_sw)
    • Not applicable

  • Forward Progress Log (FPL) Monitor (fpl_em)
    • Not applicable

  • High Availability Disk Array Monitor (ha_disk_array)
    • Not applicable

  • High Availability Storage System (dm_ses_enclosure)

    The following change applies to systems running on either the Itanium platform or the PA-RISC platform:

    • JAGaf77053
      Problem: The Probable Cause/Recommended Action section of Event 402 reads "The enclosure services controller cards have different versions of firmware. Update the controllers to the same version of firmware." This text is incomplete. Event 402 is generated because of versions of controllers or the switch settings on the controllers.
      Solution: This text is modified. It now reads "The enclosure services controller cards have different versions of firmware or different switch settings on the controllers. Update the controllers to the same version of firmware or make the switch settings similar on the controllers."

  • 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 Storage Disk Array Monitor (msamon)
    • Not applicable

  • 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 the System Fault Management product is installed on your system, you must complete the following steps, before and after updating the OnlineDiag product:
  1. Type the following command to shut down the System Fault Management subsystem:

              /sbin/init.d/cimserver stop

  2. Perform the OnlineDiag update.
  3. Type the following command to restart the System Fault Management subsystem after the update is completed:

              /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 computer systems, does not work on RX 4610 systems. The activity log for memlogd includes a message that reads unsupported device.
  MPD cannot be implemented on the RX 4610 system because the system's design does not allow the memlogd daemon to run on it.

---

Monitors Provided

For the March 2006 release of HP-UX 11.23, 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)
• Fibre Channel Adapter (ql_adapter)
• Fibre Channel Adapter Model A5158 (dm_TL_adapter)
• Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
• 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 Storage Disk Array Monitor (msamon)
• Peripheral Status Monitor (psmmon)
• RAID Adapter (dm_raid_adapter)
• Remote Monitor (RemoteMonitor)
• SCSI Disk Monitor (scsi_disk)
• System Status (sysstat_em)
• UPS (dm_ups)

The following monitors are NOT provided:

• dm_FCMS_adapter
• 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 Diagnostics section of Hewlett-Packard's online documentation Web site: http://docs.hp.com/en/diag/

Monitor Dependencies

For a list of the current required patches, see the DIAGNOSTIC.readme file for this release.

Current monitor requirements are described in the Requirements and Supported Products file. Requirements are also listed in Chapter 2 of the EMS Hardware Monitors User's Guide.

Additional Support

Starting HP-UX 11i v2 March 2006, the following servers are also supported:

• HP Integrity rx1620-2 1-socket server with new Intel(r) Itanium(r) 2 processor
• HP Integrity rx2620-4 2-socket server with new Intel(r) Itanium(r) 2 processors
• HP Integrity rx4640-8 4-socket server with new Intel(r) Itanium(r) 2 processors
• HP Integrity rx7640-16 8-socket server with new Intel(r) Itanium(r) 2 processors
• HP Integrity rx8640-32 16-socket server with new Intel(r) Itanium(r) 2 processors
• 9000/800/SD16B SuperDome server having 16 sockets for new IPF processors
• 9000/800/SD32B SuperDome server having 32 sockets for new IPF processors
• 9000/800/SD64B SuperDome server having 64 sockets for new IPF processors

Product Documentation

For the latest and most complete information on EMS Hardware Monitors and the Support Tools Manager (STM), see the documentation of Online Diagnsotcs at http://docs.hp.com/en/diag/

At this site, you will find Overviews, Tutorials, Quick Reference Cards, Frequently Asked Questions (FAQs), and other material.

For complete information on installing and using EMS Hardware Monitors, as well as a list of supported hardware, refer to the "EMS Hardware Monitors User's Guide" available at the mentioned site.

For the most current information on HP-UX 11.23 diagnostics, see the following Web pages at the Diagnostics site:

• "DIAGNOSTICS.readme for HP-UX 11.23 (March 2006)" at:

  http://docs.hp.com/en/diag/st/str_0603.htm
  

• "Release Notes for STM on HP-UX 11.23 (March 2006)" at:

  http://docs.hp.com/en/diag/stm/stm_rel.htm
  

• "Release Notes for EMS Hardware Monitors on HP-UX 11.23 (March 2006)" at:

  http://docs.hp.com/en/diag/ems/ems_rel.htm
  

SD Product Structure

The EMS Hardware Monitors are installed as part of the OnlineDiag bundle (product number B4708AA). In addition, they require the EMS framework, product number B7609BA.

For information on the STM product, refer to the STM release notes file /usr/sbin/stm/Rel_NOTES.STM.

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 by filing a request on CHART. The name of the project is diag.hw_mon.hpux. If you do not have access to CHART, contact your local HP representative to file a defect on your behalf.

/ Diagnostics HOME