Release Notes for EMS Hardware Monitors (HP-UX 11i V2.0, June 2003)

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

These release notes cover the June 2003 release of the Support Tools (diagnostics) for HP-UX 11i V2.0.

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 products 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 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. 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/monconfig .

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 Diagnostics section of Hewlett-Packard's online documentation Web site at:

     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.

For the most current information on HP-UX 11i V2.0 diagnostics, see the following Web pages at the Diagnostics site:

• "DIAGNOSTICS.readme for HP-UX 11i V2.0 (June 2003)" at:

  http://docs.hp.com/hpux/onlinedocs/diag/st/str_1123.htm
  

• "Release Notes for STM on HP-UX 11i V2.0 (June 2003)" at:

  http://docs.hp.com/hpux/onlinedocs/diag/stm/str_1123.htm
  

• "Release Notes for EMS Hardware Monitors (HP-UX 11i V2.0, June 2003)" at:

  http://docs.hp.com/hpux/onlinedocs/diag/ems/emr_1123.htm
  

Changes

For 11i V2.0, the EMS hardware monitors use version A.03.30 of the EMS platform. HP-UX 11i V2.0 does not support the full functionality of the EMS platform. However, all EMS functionality required by the hardware monitors is provided.

The notification method "SNMP" that can be configured (in previous releases) for EMS HW Monitors will probably NOT be available to monitors running on HP-UX 11i V2.0 (Check the latest the latest Web page version of the EMS Release Notes for the most current information).

Memory Page Deallocation (MPD) and the memlogd daemon are not implemented on the RX 4610 computer.

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

• Changes to Multiple Monitors
• Changes to Individual Monitors
• Changes to Platform and Interface
• Customer-Vi sible Interface Changes

Changes to Multiple Monitors

• JAGae55067
  The following monitors had a problem with polling time out:
  • dm_TL_adapter
  • sysstat_em

  Now the problem is rectified to make them work properly.

Changes to Individual Monitors

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

• Chassis Code Monitor (dm_chassis).
  
  • N/A
• CMC Monitor (cmc_em).
  
  • JAGae74094
    When the CMC data sent by the O/S to the CMC montitor was greater than 4,8Kb, the EMS dropped the monitoring request. Because the request was dropped, all future CMCs would not be processed, as a result of which, the Dynamic Processor Resilience Action would not kick in, either. This has now been fixed.
  • The severity of the event 100701 has been changed from INFORMATION to MINOR_WARNING.
  • The following changes have been made to the CMC monitor in the HP-UX 11.23 release:
    1. The monitor will support Cellular systems on which CPU deconfiguration feature will be available. It will continue to support Foundation-based systems, on which CPU deconfiguration is not available.
    2. The monitor will now generate the following events depending on the number of CPUs in the system, and whether it is a Cellular or Foundation-based system:

       100601 : Informational : A Processor Cache error occurred
       100611 : Serious       : Threshold for Dynamic Processor Resilience
                                 (DPR)action was met. This will be followd by
                                 one of the events in the range 100621-100630.
       100621-630 : Serious   : Events informing the user about the result of
                                 of the DPR action taken by the monitor.
       100641  : MajorWarning : Reminds the user about prior DPR action taken
                                 by the  monitor for a processor.
       100642  : MajorWarning : Informs the user about excessive number of CMCs
                                 occurring on a particular processor.
       100651  : Serious      : Informs the user that processor against which
                                 DPR action was taken is found to present after
        system reboot and that the monitor has
                                 deactivated it.
       100652  : Serious      : Informs the user that processor against which
                                 DPR action was taken is found to present after
                                 system reboot and that the monitor was not
                                 able to deactivate it.
       

• Core Hardware for Itanium (ia64_corehw).
  
  • The code was changed to see if the BMC clock is set. If the value of the timestamp in the SEL data is between 0 and 0x20000000, the BMC clock is not set.

    In this case, the Event Time will show "BMC Clock is not set correctly".

    For example, the following would be the Event Details:

    Event Details :
    
         Event Date .............: BMC clock is not set correctly
         Sensor Number ..........: 0x30
         Sensor Type ............: Temperature
         Sensor Class ...........: Discrete severe
         Sensor Reading/Offset...: 0x01 (Offset)
         Event  Type.............: Assertion
         Entity ID ..............: 8
         Generic Message.........:
           Temperature :  Transition to Non-Critical from OK
         Entity FRU Id Info......:
           memory module (board holding memory devices) (Sensor ID: Mem Bd1 FRU)
    

  • JAGae64471
    At each poll interval, the monitor decides where to start processing the entries in SEL, by comparing with the RecordId of the last entry processed in the previous poll interval. Currently, the monitor reads the SEL entry pointed to by the saved-RecID - and also processes it. It should not. This submittal fixes the problem.
  • JAGae61294
    The prior version of the monitor logged a message in the api.log file, if it discovered the value of entity instances to be zero (as they were being read from the SDR). The IPMI specs had a discrepancy - that being resolved, the monitor will now allow zero to be the legal value, and will not log the error.

    The message in question is:

    -------------------Start Event--------------------
    User event occurred at Wed Sep  3 10:33:10.033015 2003
    Process ID: 28529 (/usr/sbin/stm/uut/bin/.../ia64_corehw)   Log Level:
    Error
    The monitor detected that the list specified in Entity Association
    Record is incorrect.
    -------------------End Event----------------------
    

  • JAGae32973
    A user-visible change is the fix for JAGae32973: i.e., the monitor did not recognize the OEM_AZUSA box (the box-id is 0x100000).
• Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi).
  
  • N/A
• CPE Monitor (cpe_em).
  
  • This monitor has been enhanced to process CPEs on Pinnacle-based systems. New events added are 100211-100219. Please refer to the www.docs.hp.com site for explanation of these events.
  • The cpe_em monitor is now enabled for HP-UX 11.23.
  • This submission is for a new EMS monitor -- cpe_em -- which monitors non-Memory Corrected Platform Errors on IPF systems. It decodes the error data, and generates EMS events to notify the user about them. The monitor will be known as the CPE Monitor, and the executable name will be cpe_em.

    Currently, the monitor will process data for errors from the following sources:

    • PCI Bus
    • ROPE I/O Controller
    • HP Platform
    • PCI Components
    For more information, please refer to the Data Sheet and the Event listing.
• CPU Monitor -- Hitachi (cmc_em_hitachi).
  
  • N/A
• Disk Array FC60 Monitor (fc60mon).
  
  • N/A
• Disk Monitor (disk_em).
  
  • JAGae77424
    Fixed the following problem:

    The disk_em monitor was causing a file handle leak. Eventually, all system file handles would be used by this process.

  • JAGae68999
    The disk_em monitors was not starting on machines which were PCI OL* capable. This has now been fixed.
  • JAGae19531; JAGae23668; JAGae44953; JAGae47608; JAGae54206; JAGae54859

    For JAGae44953, the new defect table is as follows:

    a) 2GB and <2GB                                         1024 (P+G) list
    b) 4GB and 9GB(Mdl # ST19171XX only)                    2048 G-list only
    
    All other 9Gb and above                                 Rely on SMART
    

    Enabled SMART event handling for New HP, as well as for HP legacy HDD drives.

    For JAGae47068, the moncheck was reporting duplicate disk resources, mainly because of a particular variable (whose value defines num of HW paths monitored by this monitor) not getting updated to the actual number of HW paths to be monitored by this monitor. Now this has been corrected.

    For JAGae47608, the moncheck was reporting that DVD and MO drives were being monitored by disk_em monitor. These drives are not supported by the disk_em monitor, so they are not polled by it, nor does it handle their synchronous events. But the moncheck was reporting that these drives were monitored by disk_em monitor, because a particular variable (whose value defines num of HW paths monitored by this monitor) was not getting updated to the actual number of HW paths to be monitored by this monitor. Now this has been corrected.

    For JAGae54206, disk_em monitor was generating information event 6 unnecessarily for 73.3GB SEAGATE FC drives. This was because of spurious response data from these drives for the READ DEFECT command (this disk drive behavior was unexpected). Now the disk_em monitor has been modified so that it does not generate event 6, even if spurious response data from drive is returned by the execution of the READ DEFECT command.

    For JAGae54859, when logtool was used to see the details of an I/O error related to sdisk being logged by the driver giving rawfiles as input to the tool, the tool displayed only header info, but not other details related to the error; e.g., error description, cause/action, etc. This problem was due to the fact that the disk_em monitor doesn't log sdisk messages when running as a decoder. Now this problem has been fixed.

• Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
  
  • N/A
• Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).
  
  • N/A
• Fibre Channel Switch (dm_fc_sw).
  
  • JAGae85918
    No events from the dm_fc_sw monitor were being generated, and messages were not being logged in the api.log, indicating that the clcfg file for the monitor was not present. The problem was resolved with the submittal of the clcfg file.
• Forward Progress Log (FPL) Monitor (fpl_em).
  
  • The Intelligent Platform Management Interface (IPMI) 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. Clear, concise 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)
  
  • JAGae34667
    After generating an event, the dm_ses_enclosure monitor leaves the file /var/tmp/dm_ses_enclosure.fmt. This might fill up the file system if the monitor does not delete this file after the event has been sent. This problem has been fixed.
  • JAGae32316
    This is a change made in the tlses.h file. The buffer overflow in the tlses.sl library was causing the monitor to exit with SIGSEGV error, when DS2300 is connected with 2 controllers. Now the monitor does not restart every 2 minutes.
• iSCSI Driver Subsystem Monitor (dm_iscsi_adapter)
  
  • JAGae75914
    Added a new decoder and monitor, dm_iscsi_adapter, which is support for the Hewlett-Packard iSCSI driver subsystem, available as a technology release for target vendor and early adopter customer testing.
  • JAGae78442
    For an iSCSI monitor to work as expected, a fix had to be made in the file, get_data_from_os_error_info.c, version 1.40, which is included with 11.23.
• Kernel Resource Monitor (krmond)
  
  • N/A
• Memory IA64 (memory_ia64)
  
  • JAGae68296
    

    The memory_ia64 monitor (on HP IPF systems), when performing memory single-bit error trending analysis on the same address, same component (SAME_ADDR) events:

    • Event Number 3100 for Major Warning,
    • Event Number 3200 for Serious,
    • Event Number 3200 for Critical in the default_memory_ia64.clcfg file

    currently uses only the DIMM location of the memory single-bit error as the resource name for performing the trending analysis for the SAME_ADDR events. This is incorrect. To fix this, the memory_ia64 monitor has been modified to use both the the DIMM location, and the error address of the memory single-bit error, as the resource name for performing the trending analysis for the SAME_ADDR events.

  • Based on the firmware design to provide 128MB of contiguous zero based memory on the following IPF systems:
    • ia hp server rx5670
    • ia hp server rx2600
    • ia hp server rx4640
    • ia hp workstation zx6000
    • ia hp workstation zx2000

    the firmware will need to demote any permanent single-bit errors within this 128MB range to transient single-bit errors in th Page Deallocation Table (PDT) during reboots. As a result, the memory pages containing these errors will not be deallocated on the next reboot.

  • Added support for the following new systems:
    • ia64 hp superdome servers SD16A, SD32A, and SD64A
    • ia64 hp server rx8610
    • ia64 hp server rx7610
    • ia64 hp server rx4640
  • Modifications were made to some of the IA-64 Memory Monitor (aka IPF Memory Monitor) events. Please refer to the IPF Memory Monitor Event Descriptions web page (http://docs.hp.com/hpux/onlinedocs/diag/ems/memory_ia64.htm ) for more information on these changes.

  • JAGae49822
    Problem Description:

    The memory_ia64 monitor on IPF systems is currently reporting a page status of "Deallocated: Page is marked bad and is no longer in use" for both (1) pages that are "marked for deallocation," when it should be reporting a page status of "Pending: Page is marked for bad but can still be used"; and (2) pages that are "reserved (by the firmware)" when it should be reporting a page status of "Pending: Page is reserved by OS and is not obtainable" when displaying the memlog file via Logtool.

    For example, there may be a solid single-bit error (sbe) that has been entered into the Page Deallocation Table (PDT) which continues to occur. Although the memory_ia64 monitor has attempted to request the OS to set the page containing this sbe to bad to prevent further access to this page, (1) the page can only be marked for deallocation, but is still active; or (2) the page can not be deallocated because it is reserved (by the firmware), so is still active. Hence, if the page status of this page shows "Deallocated: Page is marked bad and is no longer in use", and errors on this page continue to occur, this page status is truly incorrect. This often then leads to confusion for the user asking: "The page is in the PDT and the page status shows that it is deallocated, so why am I still getting memory errors on this page?".

    In this case, the following is an example of the behavior that will be seen with this problem:

    *** Display of the memlog file via Logtool: a memory entry with a count of 2 and a page status of "Deallocated: Page is marked bad and is no longer in use":

    ========================================================================
    DIMM Slot:      DIMM 1A
    Error Type:     Single-bit error
    Page Status:    Deallocated: Page is marked bad and is no longer in use
    First Detected: Fri Jul 19 19:50:58 2002
    Last Detected:  Fri Jul 19 20:50:58 2002
    Error Count:    2
    Error Addr:     0x40752c3580
    ========================================================================
    

    *** Display of the memlog file via Logtool: sometime later, the count of the memory error goes up even though the page status of this memory error continues to still show "Deallocated: Page is marked bad and is no longer in use":

    ========================================================================
    DIMM Slot:      DIMM 1A
    Error Type:     Single-bit error
    Page Status:    Deallocated: Page is marked bad and is no longer in use
    First Detected: Fri Jul 19 19:50:58 2002
    Last Detected:  Fri Jul 19 21:50:58 2002
    Error Count:    3
    Error Addr:     0x40752c3580
    ========================================================================
    

    To fix this, the memory_ia64 monitor has been modified to correctly report the page status for both (1) pages that are "marked for deallocation" and (2) pages that are "reserved (by the firmware)."

  • Added support in the IA-64 Memory Monitor to support multi-cellular systems for:
    • ia64 hp superdome server SD16A, ia64 hp superdome server SD32A, ia64 hp superdome server SD64A
    • ia64 hp server rx8610
    • ia64 hp server rx7610
  • JAGae38344
    Enhancement Request Description:

    When the memory_ia64 monitor generates an event that is associated with a DIMM device, it should include the DIMM part number and serial number in the event.

    Enhancement Request Reason:

    Prior to HP-UX 11.23, the DIMM part number was available online via FRU ID information, but this information is no longer available online. For the customer or service personnel to determine the part number of a suspect DIMM, the user must have access to the system console, and use the management processor (MP) to access the FRU information.

    Including the DIMM part number in the memory_ia64 monitor's event, that is associated with a DIMM device, allows the customer and field to determine the correct replacement DIMM, without needing to access the system or the MP.

    Fix to Enhancement Request, JAGae38344:

    To fix this, the memory_ia64 monitor has been modified to include the DIMM part number and DIMM serial number in the memory_ia64 monitor's events (that are associated with a DIMM device).

  • JAGae30058
    Defect Description (JAGae30058):

    A temp file that the memory_ia64 monitor uses to generate an event is not removed after the event is processed.

    Fix to JAGae30058:

    To fix this, the memory_ia64 monitor has been modified to remove the /var/tmp/memory_ia64.fmt file, after the event is processed.

  • JAGae49822
    Problem Description:

    The memory_ia64 monitor on IPF systems is reporting the page status of "marked for deallocation" pages as having a page status of "Deallocated: Page is marked bad and is no longer in use", instead of a page status of "Pending: Page is marked for bad but can still be used", when displaying the memlog file via Logtool. For example, there may be a solid sbe that has been entered into the Page Deallocation Table (PDT) which continues to occur. Although the memory_ia64 monitor has requested the OS to set the page containing this sbe to bad to prevent further access to this page, the page can only be marked for deallocation, but is still active. Hence, if the page status of this page shows "Deallocated: Page is marked bad and is no longer in use", and errors on this page continues to occur, this page status is truly incorrect. This often then leads to confusion for the user asking: "The page is in the PDT, and the page status shows that it is deallocated, so why am I still getting memory errors on this page???". In this case, the following is an example of the behavior that will be seen with this problem:

    • *** Display of the memlog file via Logtool: a memory entry with a count of 2 and a page status of "Deallocated: Page is marked bad and is no longer in use":

      ========================================================================
      DIMM Slot:      DIMM 1A
      Error Type:     Single-bit error
      Page Status:    Deallocated: Page is marked bad and is no longer in use
      First Detected: Fri Jul 19 19:50:58 2002
      Last Detected:  Fri Jul 19 20:50:58 2002
      Error Count:    2
      Error Addr:     0x40752c3580
      ========================================================================
      

    • *** Display of the memlog file via Logtool: sometime later, the count of the memory error goes up even though the page status of this memory error was previously "Deallocated: Page is marked bad and is no longer in use":

      ========================================================================
      DIMM Slot:      DIMM 1A
      Error Type:     Single-bit error
      Page Status:    Deallocated: Page is marked bad and is no longer in use
      First Detected: Fri Jul 19 19:50:58 2002
      Last Detected:  Fri Jul 19 21:50:58 2002
      Error Count:    3
      Error Addr:     0x40752c3580
      ========================================================================
      

• Memory Monitor -- Hitachi (ipfmemory_hitachi).
  
  • N/A
• Peripheral Status Monitor (psmmon).
  
  • N/A
• Remote Monitor (RemoteMonitor).
  
  • N/A
• SCSI Disk Monitor (scsi_disk).
  
  • N/A
• SCSI Tape Monitor (dm_stape).
  
  • JAGae32036
    A fix was made for the situation where dm_stape.cfg is not the latest version [1.15], therefore the polling interval does not default to 0, as required. This is required to disable polling.
  • JAGae40361
    A cause/action message was added to event 5000, indicating that one possible cause for this event is that the PCI card attached to the device may have been deleted using PCI OL* mechanisms, or as part of a Cell OS* operation.
  • There have been conflicts running tape backup applications, while dm_stape is polling devices, so the default polling interval has been set to 0 (no polling).
• System Status Monitor (sysstat_em)
  
  • JAGae56558
    Sysstat_em was failing when the machine on which the monitor was run was rebooted. This problem has now been fixed.
  • JAGae55068
    The sysstat_em monitor did not recognize a machine to be in the UP state when it comes from the DOWN state to the UP state. This has now been fixed for Online diagnostics for HP-UX release 11.23.
• UPS Monitor (dm_ups).
  
  • JAGae56954
    When the dm_ups monitor comes up and detects that the ups_mond has not started, or if the FIFO communication channel between the two is discovered to be absent, then:
    1. dm_ups will not create the hardware exists file;
    2. Will reject all monitoring requests;
    3. Will log a Note level message in the api.log and will exit, since the resource to be monitored is absent.
    Previously, the dm_ups monitor would have generated event #42. This event will no longer be generated.
  • JAGae56140
    The dm_ups monitor was causing the persistence files to grow in size when ups_mond was killed, and the entry for ups_mond in the /etc/inittab file was removed to prevent re-spawning of the daemon. Code changes have been made to resolve this problem.

  Changes to Platform and Interface

  • JAGae84431
    System IP Address in all monitor events showed as 0.0.0.2, which was not correct. This problem has now been fixed and now event data contains correct system IP address.
  • JAGae55069
    An enhancement has been made to the output of the "aplsrv" debug trace tool. The user will see output with a time stamp added at the beginning of every line of output logged/displayed. Similar output goes to the log file /var/tmp/APL.LOG .
  • JAGae35427
    Fixed monitoring framework so that host information, such as serial number and model string, is correctly retrieved and sent with events.
  • JAGae36855
    Fixed monconfig to remove world-write permissions on *.sapcfg files, when modifying monitoring requests. Fixed monconfig, startmon_client, toggle_switch, moncheck, and send_test_event to remove world-write permissions on tmp.sapcfg file.
  • JAGae36855
    Fixed monconfig so it does not add world-write permissions to *,.sapcfg files, when modifying monitoring requests.

  Customer-Visible Interface Changes

  • N/A

  Known Problems

  ---

  PROBLEM: Incorrect WatchdogTimer actions may be specified with multiple versions of the ia64_corehw monitor (JAGae86338)

  The ia64_corehw monitor sets the value of action for the WatchdogTimer, when it starts. If and when the system hangs, as soon as the WatchDogTimer expires, the Management Processor will take the action that it is set to take.

  The default action is "No_Action", as specified in the ia64_corehw.cfg file. The configuration verb used for this is WATCHDOG_COMMAND. The action is user-configurable to one of four possible values: "No_Action", "Hard_Reset", "Power_Cycle",”and "Power_Down".

  There are three versions of the ia64_corehw monitor: ia64_corehw, ia64_corehw_asama, and ipfcorehw_hitachi. Potentially, all three of them can specify different actions in their respective .cfg files.

  When the system boots, all monitors get started; after they evaluate whether or not they are supposed to run on the current system/architecture, some of them will shut themselves down. On HP systems, ia64_corehw_asama and ipfcorehw_hitachi will also start up along with ia64_corehw, but then shut themselves down: only the ia64_corehw monitor will be left running.

  Currently, after the system boots, all these monitors try to set the watchdog timer BEFORE evaluating whether they are supposed to run on the current system or not. Because of this, if different actions are specified by the three versions of the monitor, one monitor will override another monitor's setting. Eventually, only the last monitor's action will be in effect.

  The workaround for this problem is to specify the same action in all three monitors' .cfg files. In this way, the correct WatchDogTimer action will be in effect.

  The problem will be fixed in the next release of OnLineDiags for HP-UX 11.23, by allowing different settings for each version of the ia64_corehw monitor.

  ---

  PROBLEM: Memory Page Deallocation (MPD) is not available on the RX 4610 computer.

  The Memory Page Deallocation (MPD), which runs on most current HP-UX computer systems, does not work on the RX 4610 computer. If you look in the activity log for memlogd, you will see a message saying, "unsupported device."

  MPD cannot be implemented on RX 4610 because of the design of that system. The memlogd daemon cannot run on it.

  ---

  PROBLEM: dm_fc_hub and dm_fc_sw monitors not functional.

  In the June 2003 release of 11i V2.0, the Fibre Channel Arbitrated Loop Hub monitor (dm_fc_hub) and the Fibre Channel Switch monitor (dm_fc_sw) are probably not functional, because these monitors depend on SNMP functionality which may not be included in this release (check the latest version of the Web page for the EMS Release Notes for the most current information) .

  ---

  Monitors Provided

  For the June 2003 release of HP-UX 11i V2.0, the following monitors are scheduled to be available:
  • CMC Monitor (cmc_em).
  • Core Hardware for Itanium (ia64_corehw)
  • Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi)
  • CPE Monitor (cpe_em)
  • CPU Monitor -- Hitachi (cmc_em_hitachi)
  • Disk (disk_em)
  • Disk Array FC60 (fc60mon)
  • Fibre Channel Adapter Model A5158 (dm_TL_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 (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 IA64 (memory_ia64)
  • Memory Monitor -- Hitachi (ipfmemory_hitachi)
  • Peripheral Status Monitor (psmmon)
  • Remote Monitor (RemoteMonitor)
  • SCSI Disk Monitor (scsi_disk)
  • SCSI Tape Devices (dm_stape)
  • System Status (sysstat_em)
  • UPS (dm_ups)
  The following monitors are NOT provided:
  • dm_core_hw: replaced by ia64_corehw
  • dm_FCMS_adapter
  • fw_disk_array: hardware not supported on system
  • lpmc_em: replaced by cmc_em
  • scsi123_em: hardware not supported on system

  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.hw_mon.hpux. 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.

  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