Release Notes for STM on HP-UX 11i (11.11) (June 2002)

• Overview
• Documentation
• Changes
  • Changes to User Interface and Platform
  • General Changes to Tools
  • Changes to Specific Tools
• Known Problems
• Defect Reporting
• SD Product Structure

These release notes cover the June 2002 release of Support Plus for HP-UX 11i (11.11) running on S800/S700 systems.

Overview

The Support Tools Manager (STM) provides a complete set of online support tools for HP-UX systems, enabling you to verify and troubleshoot PA-RISC system hardware, and to examine system logs.

STM offers several tool types, including information tools, verifiers, exercisers, expert tools, firmware update tools, diagnostics and utilities.

Installed with STM (as of IPR 9902) 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. For more information, see /usr/sbin/stm/Rel_NOTES.HWE.

Documentation

For the latest and most complete information on STM and EMS Hardware Event Monitors, 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.

Changes

The online Support Tools Manager (STM) was enhanced and updated for the current release.

Changes to User Interface and Platform

• JAGae10868
  A fix was made for JAGae10868, to solve occasional CPU Information Tool failures.
• Added support for the following CD-ROMs: TEACDV-28E-A, TEACDV-28E-b, TEACDW-28E, LITE-ONLTR-24102B, and HL-DT-STD VD-ROM GDR8161B.
• JAGae16777
  Fixed a potential problem with dc_chassis, that may cause the file system to fill up, if attempting to decode a corrupt raw chassis code file.
• Updated diagmond to keep track of OLA/R capable pci slots, to determine which associated hardware paths may be suspended, in order to update the monitor hardware paths list, so suspended paths can be ignored by EMS monitors.
• Updated diaglogd to handle MCA data processing.
• Error messages are no longer logged if a driver name does not exist for a given io tree token.
• Updated iSCSI by adding mapping of iscsi driver.
• Licensing now supports:

          Keystone(Perfpak)  hversion 0x5eb
          Matterhorn(Leone)           0x5eb
          Marcato W+ DC-              0x5da
          Superdome(Pacu)             0x5ea
  

• JAGae13080
  Fixed a problem where the 14x optical libraries would fail to be recognized as supported devices.
• Included the Mt Hamilton and Mt Hamilton DC- hversion mnemonics.
• JAGae09320
  Added support for the missing MARCATO_W_DC_MINUS hversion for STM tools.
• JAGae09320
  Added support for MARCATO_W_DC_MINUS 0x5DA/Marcato W+ DC- w/Landshark Processors.
• JAGae68931
  This is a submittal to provide support for Marca to W+ DC- machines, by including the Marcato (L3000) W+ DC- (0x5DA) hversion mnemonic.
• JAGad97675
  Added a security governer into a libdiaggs.sl library function that creates new stm directories. This function was modified so it may now either refuse to allow the new directory to be created or it may alter the access modes for the new directories being created. If the new path is /var/stm/ or any path under this, then the user must be root to create the directory. Otherwise the directory will not be created and an error message will be logged. All directories under /var/stm/ shall be created with rwxr-xr-x permissions, with the exception of /var/stm/logs and /var/stm/catalog which shall both be created with rwxrwxrwxt permissions. All other directories may be created by anyone, but will be created to be writable by the creator only.

General Changes to Tools

• There is a new evlib routine, that will remove all iscsi related devices in list of device paths. The SCSI-related monitors which use this routine are:
  • armmon
  • disk_em
  • dm_fc_scsi_mux
  • dm_ses_enclosure
  • dm_stape
  • fc60mon
  • fw_disk_array
  • ha_disk_array
  If any of these tools are monitoring a SCSI device that is a descendant of an iscsi virtual node, then that device will be removed from that monitor's pathlist of resources, and will no longer be monitored.
• The following id modules were modified, so they will ignore iSCSI devices:
  • scsi_dev
  • scsi_arry
  • scsi_mux_bus
  • i2o_raid
  If an iSCSI device is discovered while scanning hardware to build the S TM map, all paths below that device will be filtered out of the STM map. Example of STM map prior to filtering out iSCSI devices:

                                 hpfcs214.cup.hp.com
  
    Dev                                                 Last        Last Op
    Num  Path                 Product                   Active Tool Status
    ===  ==================== ========================= =========== ===== ========
      1  10                   Bus Adapter (582)
  2  10/0                 PCI Bus Adapter (782)
      3  10/0/12/0            Core PCI 100BT Interface
  .
  .
  .
     25  255/0/0.0            iSCSI Virtual Node (iSCSI
     26  255/0/0.0.0.0        SCSI Disk (SEAGATEST39103
     27  255/0/0.0.0.1        SCSI Disk (SEAGATEST39103
     28  255/0/1.0            iSCSI Virtual Node (iSCSI
     29  255/0/1.0.0.0        SCSI Disk (SEAGATEST39103
     30  255/0/1.0.0.1        SCSI Disk (SEAGATEST39103
     31  255/0/2.0            iSCSI Virtual Node (iSCSI
     32  255/0/2.0.0.0        SCSI Disk (SEAGATEST39103
  

  Example of STM map after filtering out iSCSI devices:

                                 hpfcs214.cup.hp.com
  
    Dev                                                 Last        Last Op
   Num  Path                 Product                   Active Tool Status
    ===  ==================== ========================= =========== ===== ========
      1  10                   Bus Adapter (582)
      2  10/0                 PCI Bus Adapter (782)
      3  10/0/12/0            Core PCI 100BT Interface
  .
  .
  .
     28  255/0/0.0            iSCSI Virtual Node (iSCSI
     29  255/0/1.0            iSCSI Virtual Node (iSCSI
     30  255/0/2.0            iSCSI Virtual Node (iSCSI
  

• JAGae11212
  New JBODs DS2300 (Smuggler) and DS2405 (Apex) have to be supported in existing STM tools and Monitors. Hence tlses.h is changed in such a way that it supports the new JBODs.

Changes to Specific Tools

• Information tools:
  • JAGae11212
    STM info tool supports the new JBODs DS2300 (Smuggler) and DS2405 (Apex) from this release onwards.
  • JAGae09438
    Fixed printing of long integer for max_block_addr in info/scsi_disk.
  • JAGae11065; JAGae11638; JAGae09438
    Fixed printing of Max Block Address in srm_disk information tool. Added support for new CD-ROMs and DVDs: TEACDV-28E-A, TEACDV-28E-B, TEACDW-28E, HL-DT-STDVD-ROM GDR8160B, and LITE-ONLTR-24102B in srm_disk information tool.
  • JAGae15588
    Info tool for DS2405 (Apex) was exiting with SIGSEGV. This problem was due to a bug in tlses library. This defect is fixed for this release.
  • JAGad89341
    Product_id description for MAXTOR drive problem is fixed. Earlier the buffer length for product_id description was 13 characters, so now it is changed to 16 characters to fix the problem.
  • JAGae09320
    Added functionality for the Marcato (L3000) W+ DC- machines.
  • JAGae05550
    The info activity log file would have the following message when there was a stable store problem; the stable store failing is not a problem and should not be logged:

    An unexpected return came from the stable store 
    function. This is informational only and does not
    materially effect the results.
    

• Exerciser tools:
  • JAGad92025
    This is a fix for the problem where "Exercise" Visualize-EG (Graffitti) graphics adapters are failing with a gopen error.
  • JAGae00180
    There is a message that occasionally is displayed in the activity log file for the exerciser/cpu that states: "child 25016 last wrote random data at: C4641FFC, 0 half (loop: 525,round: 0, pass !)" The portion "0 half" should not be in the message, which will now read "child 25016 last wrote random data at: C4641FFC, (loop: 0, round: 525, pass 0)", or some similar message.
• Verifier tools:
  • N/A
• Diagnose tools:
  • JAGae13462
    Corrected driver name so that bt100d diagnose tool displays information correctly.
• Firmware update tools:
  • JAGae11212
    STM firmware update tool supports the new JBODs DS2300 (Smuggler) and DS2405 (Apex) from this release onwards.
  • JAGad96592
    Fixed a problem with the Firmware Update Tool, to allow correct firmware downloading, when using the STK 9840 tape drives. The STM error message was "failed firmware download".
  • JAGad96592
    Fixed a problem with the Firmware Update Tool when using STK library systems L180 and L700. The STM error message was "Illegal Request Sense Key".
• Expert tools:
  • JAGae08770
    The catalog was update to the current version (A.02.10), which means users will see the correct messages for the version.
  • JAGae03687
    Previously, in the graphical version of STM, a warning message was displayed before CPU selection. With this bug fix, the warning message is displayed after a CPU is selected for activation.
  • JAGae01231
    This is a fix for the DDS expert tool, which would hang STM (this problem was noticed on 64-bit systems running HPUX 11.11). Although it would time out, the process was left running and no other STM access to that device was possible until the process was killed using kill -9. Exiting and re-starting STM would not reset it.
  • JAGae02480
    Certain users are unable to connect to Version A.29.00 of stm. When attempting to connect, the following error message may appear:

    -- Error --
    Hostname (sshapd1.rose.hp.com) could not be connected due to an invalid
    user login name or password.
    Please Refer to the UI Activity Log for more details.
    

    The current workarounds are to: 1) login as a different user. 2) change user password.
  • JAGad62032
    The following warning message has been changed from:

    CAUTION! RAID 0 DOES NOT PROVIDE DATA REDUNDANCY. THE FAILURE OF ANY
    DISK WITHIN A RAID 0 LUN WILL RESULT IN THE LOSS OF ALL DATA IN THAT
    LUN. RAID 0 SHOULD ONLY BE USED FOR NON CRITICAL DATA THAT COULD BE
    LOST IN THE EVENT OF A HARDWARE FAILURE. RAID 0 SHOULD ONLY BE USED
    IN SITUATIONS WHERE HIGH PERFORMANCE IS IMPORTANT THAT DATA
    PROTECTION.
    

    to:

    CAUTION!  RAID 0 does not provide data redundancy.  The failure of any
    disk within a RAID 0 LUN will result in the loss of all data in that
    LUN.  RAID 0 should only be used for non-critical data since it might
                                            ^              ^^^^^^^^^^^^^^
    be lost in the event of a hardware failure.  RAID 0 should only be used
    ^^
    in situations where high performance is more important than data
                                            ^^^^           ^^^^
    protection.
    

    where the ^^^^ indicates change in the message text.
  • JAGae00180
    There is a message that occasionally is displayed in the activity log file for the exerciser/cpu that states: "child 25016 last wrote random data at: C4641FFC, 0 half (loop: 525,round: 0, pass !)" The portion "0 half" should not be in the message, and will now read "child 25016 last wrote random data at: C4641FFC, (loop: 0, round: 525, pass 0)" or some similar message.
  • JAGae00185
    Fix was made for occasion where multiple cpus would be exercised when the user only requested one from the cpu expert tool. This would result in the following message:

    The child process with process ID xxxxx (0xhhhhh) exited with unexpected
    status (125 (0x7d)). This child process was launched to exercise 
    floating point coprocessor associated with processor x (0xh)
    at path xxxxxxxxxxx (at HPA 0hhhhhhhhhhhhhhhh).
    
     Possible Causes/Recommended Action:
    
    Internal application error.
    

  • JAGad92076
    The Memory Expert tool was printing the DIMM Slot with an extra /b/c/d in the slot string. The extra part of the string has been removed. Prior to the fix, a request for address resolution would return info of the form:

    Address:       0x00000000000001
    Page:          0
    Page Status:   RESERVED by operating system
    Board:         CELL 1/4  0a/b/c/d/b/c/d
    Physical Bank: N/A
    Logical Bank:  N/A
    

    whereas now, that same request returns

    Address:       0x00000000000001
    Page:          0
    Page Status:   RESERVED by operating system
    Board:         CELL 1/4  0a/b/c/d
    Physical Bank: N/A
    Logical Bank:  N/A
    

    (note the change for "Board:" not having /b/c/d displayed twice.)

  • Made a fix for running the exercise option in ET. It complained about IOCTL call failure.
  • Fixed a problem with selecting a SPU to be marked for deconfiguration. In previous releases, the SPU marked for deconfiguration would always be the last SPU, and not the SPU selected (unless it was the last one that was selected!)
  • Made the following two fixes: 1. Fix for : CPU expert tool logs an error, but behaves correctly. 2. Fix for : CPU expert tool does not reconfigure the processor that it just deconfigured.
• Logtool:
  • N/A
• Utilities:
  • There is a new release of cc_translator, which includes chassis codes from PDC firmware version 35.1.
  • JAGae09320
    Added support for missing MARCATO_W_DC_MINUS hversion for STM tools.

Known Problems

Info Tool Causes HPMCs on K- and T-Class (HP-UX 11i only)

K-Class and T-Class computers running HP-UX 11i will experience HPMCs or Data Page Faults if you run the STM Info Tool to retrieve configuration information from HP-PB SE SCSI adapters (JAGad88317, JAGad97126).

The root cause is a problem in the HP-UX 11i kernel, which is exposed when the Info Tool is run as described above. To correct the problem and avoid potential HPMCs, load patch PHKL_25552 or its successor. This is a kernel patch and requires a system reboot.

STM only exposes this problem if the Info Tool is run on HP-PB SE SCSI adapters. STM does not expose the problem if the Info Tool is run against other I/O devices.

Defect Reporting

Use CHART to report defects in STM. The project name is diag.stm.tools.hpux for individual tools, and diag.stm.ui.hpux for the user interface. If you don't have access to CHART, contact an HP representative to enter a defect for you.

SD Product Structure

The product number for STM is B4708AA.

SD PRODUCT: Sup-Tool-Mgr
   Description: On-line Diagnostic System (Series 800/700)

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

      FILESET: STM-MAN
         Description: S800/S700 STM Manual Pages

      FILESET: STM-SHLIBS
         Description: S800/S700 STM Shared Libraries

      FILESET: STM-UI-RUN Corequisite Filesets: STM-SHLIBS
         Description: S800/S700 STM User Interface
         
      FILESET: STM-UUT-RUN  Corequisite Filesets: STM-SHLIBS
         Description: S800/700 STM Unit Under Test Runtime 

/ Diagnostics HOME