Release Notes for EMS Hardware Monitors on HP-UX 11i (December 2003)

• Overview
• Configuring Hardware Monitoring
• Documentation
• Changes
  • Changes to Multiple Monitors
  • Changes to Individual Monitors
  • Changes to Platform and Interface
  • Customer-Visible Interface Changes
• Known Problems
• Monitors Provided
• Monitor Dependencies
• Defect Reporting
• SD Product Structure

These release notes cover the December 2003 release of Support Plus for HP-UX 11.0/11i running on S800/S700 systems.

NOTE: As of the September 1999 release, the name of the Diagnostic/IPR Media has been changed to Support Plus. In addition, the format has changed so that there is a separate CD-ROM for each version of the operating system (e.g., HP-UX 11i).

NOTE: The HP Storageworks SDLT 160/320 GB Tape Drive and HP Ultrium 460 External Tape Drive are NOT SUPPORTED by the OnlineDiag product. Even though some STM tools may function with these devices, they are still NOT SUPPORTED. The diagnostic tools and utilities that DO SUPPORT these devices are the HP StorageWorks Library and Tape Tools (L&TT). These tools can be downloaded, free of charge, at:

http://www.hp.com/support/tapetools

Overview

Included on the Support Plus CD-ROM 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 products and be alerted immediately if any failure or other unusual event occurs. Hardware event monitoring is available to users running HP-UX 11i and 11.00 (IPR 9902 and later).

Hardware event monitoring provides a high level of protection against system hardware failure. By using hardware event monitoring, you can virtually eliminate 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. Once the monitoring software is installed, monitoring is automatically enabled.

By default, messages regarding major warning, serious and critical events that occur on hardware being monitored will be:

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

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

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

The Peripheral Status Monitor (PSM) and the The Kernel Resource Monitor (krmond) are configured differently. They use the EMS GUI. See: http://docs.hp.com/hpux/onlinedocs/diag/ems/ems_gui.htm

Documentation

For the latest and most complete information on EMS Hardware Monitors and the Support Tools Manager (STM), see the Web page "Diagnostics": http://docs.hp.com/hpux/diag/

At this site, you will find Overviews, Tutorials, Quick Reference Cards, Frequently Asked Questions (FAQs), and much 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 above site. An electronic copy of this book is also included on the Support Plus CD-ROM in the <mount_point>/DIAGNOSTICS directory.

Changes

Changes in the EMS Hardware Monitors for the the December 2003 release include:

• Changes to Multiple Monitors
• Changes to Individual Monitors
• Changes to Platform and Interface
• Customer-Visible Interface Changes

Changes to Multiple Monitors

• N/A

Changes to Individual Monitors

Changes to each monitor are described below. (Monitors are listed in alphabetical order.)

• AutoRAID Disk Array (armmon).
  
  • JAGae82991
    Whenever a new 12H device is connected to the server, the customer needs to check to see if ARMServer is running. Once this check is done, the customer needs to issue the "arraydsp -R" command, so that the server will identify the device. This needs to be done before the monitor starts monitoring the device.
• Chassis Code Monitor (dm_chassis).
  
  • JAGae26463
    The dm_chassis monitor has been changed to ignore the chassis codes whose reporting entity type is HP-UX. The dm_chassis monitor does not identify these kinds of chassis logs.
  • The daemon cclogd and the dm_chassis monitor have been modified, so that they do not run on the following classes of machines:
    • rp8420
    • rp7420
    • sd16A/sd32A/sd64A
• Core Hardware Monitor (dm_core_hw)
  
  • JAGae86688
    Events #31 and #32 were disabled for the dm_core_hw monitor.
  • The dm_core_hw monitor now supports the monitoring of bus adapters on the following SPUs: sd16A/sd32A/sd64A, rp8420, rp7420, rp4440, rp3440, and c8000.
  • For bus adapters, Cabinet Fans and Power supplies monitoring is disabled in dm_core_hw, and will be supported by the ia64_corehw monitor.
  • Selective monitoring of individual hardware components is now in place. These can be configured through the variables of the dm_core_hw.cfg file. Four new variables have been added, which are:
    • XBC_DISABLE_MONITORING - To enable/disable Fabric monitoring
    • SBA_DISABLE_MONITORING - To enable/disable System Bus Adapter monitoring
    • CC_DISABLE_MONITORING - To enable/disable Cell controller monitoring
    • FAN_AND_PWRS_DISABLE_MONITORING - To enable/disable Cabinet monitoring. This variable does not affect the functioning of the monitor on the following class of machines: sd16A/sd32A/sd64A, rp8420, rp7420, rp4440, rp3440, and c8000.
    By default, these variables are set to zero, to allow monitoring of all the components mentioned above.
• Core Hardware Monitor for Itanium (ia64_corehw).
  
  • This is the initial release of the monitor on HP-UX 11.11. It will process entries in the System Event Log (SEL) on non-cellular Itanium systems only, and generate appropriate EMS events. On Cellular Integrity systems, the monitor will copy the contents of the Forward Progress Log (FPL) into logfile(s), which will be processed by the FPL monitor (fpl_em).

    In addition, the monitor will also receive PCI error data, and make it available to the FPL monitor. The FPL monitor will then generate appropriate EMS events. The PCI error-data processing will be available on IPMI-based, as well as non-IPMI based, HP-PA systems.

    The ia64_core_hw monitor also monitors fans and power supplies in non-Cellular PA and Cellular PA systems.

• CPU Monitor (lpmc_em).
  

  Note: As of the June 2002 release, the LPMC Monitor (lpmc_em) was renamed to "CPU Monitor". The binary name is still lpmc_em. The name was changed to reflect the monitor's enhancement to check floating-point functionality in the CPU.

  • JAGae95186
    Lpmc_em monitor has been further enhanced to catch floating point errors in processors.
  • JAGae94305
    During the DPR (Dynamic Processor Resilience) action, if the system is running vPar, lpmc_em monitor uses vPar commands to activate a floater CPU and bring the floater CPU in to the current virtual partition.
  • Lpmc_em monitor is now supported on the following new platforms: sd16A/sd32A/sd64A, rp8420, rp7420, rp4440, and rp3440.

    In addition to Level 1 Processor Cache, the CPU monitor now monitors the errors in Level 2 Cache, System Bus, and in the Translation Lookaside Buffer. The System Bus errors are monitored only on the following machines: sd16A/sd32A/sd64A, rp8420, rp7420.

    Errors in Level 1 Processor Cache, Level 2 Tag Cache, and System Bus are polled by the monitor: the polling frequency is set at 15 minutes.

    For Level 2 Data Cache and the Translation Lookaside Buffer, the monitor obtains error data through the diagnostics daemon, diaglogd.

• Disk Array FC60 Monitor (fc60mon).
  
  • JAGae90990
    Earlier, only one event was getting generated for any number of GHS enabled/disabled disks. A change that has been made in the configuration file enables reporting of all the GHS events, either enabling GHS disks, or disabling GHS disks, in the FC60 storage device.
  • Whenever a new fc60 device is connected to the server, the customer needs to check to see if AM60Srvr is running. Once this check is done, the customer needs to issue the "amdsp -R" command, so that the server will identify the device. This needs to be done before the monitor starts monitoring the device.
• Fast Wide SCSI Disk Array (fw_disk_array)
  • N/A
• Disk Monitor (disk_em).
  
  • N/A
• Fibre Channel Adapters (dm_FCMS_adapter).
  
  • N/A
• Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
  
  • N/A
• Fibre Channel Adapter Model A6826A Monitor (dm_QL_adapter)
  • N/A
• Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).
  
  • N/A
• Fibre Channel Switch (dm_fc_sw).
  
  • N/A
• Forward Progress Log Monitor (fpl_em)
  
  • The Forward Progress Log (FPL) Monitor is a new EMS monitor, designed to monitor the IPMI FPL log entries on the system. IPMI is used by system firmware, the operating system, and other components, to log hardware failures, warnings, and forward progress during system boot. If a problem is detected, the monitor immediately sends an event to the Event Monitoring Service, which alerts the user, using the notification methods defined for the monitor. Error messages identify the problem, what caused it, and what must be done to correct it. The monitor is launched automatically when the system is started, ensuring that the system is protected from undetected hardware failure.
• High Availability Disk Array Monitor (ha_disk_array).
  
  • N/A
• High Availability Storage System (dm_ses_enclosure)
  
  • JAGae84575
    The monitor consumed 100% of the CPU resources, when connected with DS2300 and SC10: this has been corrected.
• iSCSI Device Adapter (dm_iscsi_adapter)
  • N/A
• Kernel Resource Monitor (krmond)
  
  • N/A
• LPMC Monitor (lpmc_em).
  As of the June 2002 release, the LPMC Monitor (lpmc_em) was renamed to "CPU Monitor". The binary name is still lpmc_em. The name was changed to reflect the monitor's enhancement to check floating-point functionality in the CPU. For more information, see CPU Monitor (lpmc_em).
• Memory Monitor (dm_memory).
  
  • N/A
• Peripheral Status Monitor (PSM/psmmon).
  
  • N/A
• Remote Monitor (RemoteMonitor).
  
  • N/A
• SCSI Card Monitor (scsi123_em).
  
  • N/A
• SCSI Cascade Monitor (scsi_cascade).
  
  • N/A
• SCSI Disk (scsi_disk).
  
  • N/A
• SCSI Tape Monitor (dm_stape).
  
  • N/A
• System Status Monitor (sysstat_em).
  
  • N/A
• UPS Monitor (dm_ups).
  
  • N/A

Changes to Platform and Interface

• JAGae85463
  The System IP Address in all monitor events was being reported incorrectly. This problem has now been fixed.

Customer-Visible Interface Changes

• N/A

Known Problems

---

CAUTION: UPS Monitor May Need a Patch

In some cases, the UPS monitor (dm_ups) will not function and will instead generate event 45 (formerly event 42) with the text:

Probable Cause / Recommended Action:

The monitor was unable to locate the fifo pipe that should have been
created by ups_mond.  Therefore, information about the ups cannot be sent
to the monitor.

You need version (80.1.2.3) of ups_mond or greater.  To update your
system with the correct version of ups_mond, install the
following patch:

HPUX 11.11      : PHCO_23832

To fix the problem, load the indicated patch or load the HWE patch bundle which contains this patch. For HP-UX 11i, the ups_mond patch PHCO_23832 is also distributed on the Sept 01 OE.

This problem will affect most systems with a UPS when the September 2001 diagnostics are installed. The only systems not affected will be those which are being updating from certain versions of the diagnostics (September 2000 through March 2001) and which do not have patch PHCO_19040 (HP-UX 11.00) installed.

---

CAUTION: Monitoring Changes for disc30, sdisk and disk array devices

As of IPR 9902 (Feb 99 release), there has been a change to the way that monitoring is done for disc30, sdisk and the HA Disk Array Models 10, 20, and 30FC.

Formerly, the "diaglogd exec" programs (pdisc30_exec and psdisk_exec) handled driver error entries for these devices.

As of IPR 9902, these programs have been deleted and their functionality is now provided by the EMS Hardware Monitors.

If you had customized the configuration files for the diaglogd exec programs (disk30_exec.cfg and sdisk_exec.cfg) you may wish to re-configure the EMS Hardware Monitors to achieve the same results.

---

CAUTION: Compatibility Problem with EMS-Related Products (ServiceGuard, HA Monitors, etc.)

If you install the OnlineDiag bundle (Dec 99 or later) onto a computer running older revisions of EMS-related products, these products may experience compatibility problems. Affected products include MC/ServiceGuard, ServiceGuard OPS Edition and High Availability Monitors. The only critical problems occur with the following versions:

MC/ServiceGuard            A.10.10, A.11.01, A.11.03
ServiceGuard OPS Edition   A.11.02, A.11.03

Support Tools and the EMS hardware monitors are not affected. For complete information, see EMS Incompatibility Problem.

---

Monitors Provided

Monitors are provided to support the following:

• AutoRAID Disk Array (armmon)
• Chassis Code Monitor (dm_chassis)
• Core Hardware (dm_core_hw)
• Core Hardware for Itanium (ia64_corehw)
• CPU (lpmc_em)
• Disk (disk_em)
• Disk Array FC60 (fc60mon)
• Fast Wide SCSI Disk Array (fw_disk_array)
• Fibre Channel Adapters (dm_FCMS_adapter)
• Fibre Channel Adapter Model A5158 (dm_TL_adapter)
• Fibre Channel Adapter Model A6826A Monitor (dm_QL_adapter)
• Fibre Channel Arbitrated Loop Hub (dm_fc_hub)
• Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
• Fibre Channel Switch (dm_fc_sw)
• Forward Progress Log Monitor (fpl_em)
• High Availability Disk Array (ha_disk_array)
• High Availability Storage System (dm_ses_enclosure)
• iSCSI Device Adapter (dm_iscsi_adapter)
• Kernel Resource (krmond)
• LPMC (lpmc_em) renamed to "CPU Monitor" as of the June 02 release
• Memory (dm_memory)
• Remote (RemoteMonitor)
• SCSI Card (scsi123_em)
• SCSI Cascade (scsi_cascade)
• SCSI Disk (scsi_disk)
• SCSI Tape Devices (dm_stape)
• System Status (sysstat_em)
• UPS (dm_ups)

In addition, the Peripheral Status Monitor (PSM) is provided to monitor the current status of the products supported by the above list.

For detailed information concerning which products are supported by which monitors and additional dependencies, check the "Diagnostics" section of Hewlett-Packard's online documentation web site: http://docs.hp.com/hpux/diag/ .

Monitor Dependencies

Several of the monitors have special requirements, such as patches or certain versions of firmware. In particular:

• The Fibre Channel Arbitrated Loop Hub Monitor and the Fibre Channel Switch Monitor require special configuration which is described in their data sheets in the "EMS Hardware Monitors User's Guide" (chapter 6). A patch is also required.
• A patch is required if your system includes an HP SureStore E Disk Array FC60. This patch is required to to run the EMS hardware monitor (fc60mon) or STM tools for this device.

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

Current monitor requirements are described in the "Supported Products" page under "EMS Hardware Monitors" at http://docs.hp.com/hpux/diag . Requirements are also listed in chapter 2 of the manual "EMS Hardware Monitors User's Guide".

Defect Reporting

Use CHART to report defects in the EMS Hardware monitors. The project name is diag. If you don't have access to CHART, contact an HP representative to enter a defect for you.

SD Product Structure

The EMS hardware monitors are installed as part of the OnlineDiag bundle (product number B4708AA). In addition, they utilize the EMS framework, product number B7609BA.

Note: EMS Hardware Monitors are installed as part of the STM-UUT-RUN Fileset. However, the EMS Hardware Monitors are dependent on the EMS-Core and EMS-Config products and additional filesets in the Sup-Tool-Mgr Product.

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

/ Diagnostics HOME