Release Notes for STM on HP-UX 11i (December 2004)

• 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 December 2004 release of Support Plus for 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

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

• JAGaf37354
  This relates to the tllibio library. This library is used by both monitors and tools. The call to this library causes a memory leak (of 36 bytes), if the device which is being checked for suspension is not Online Addition and Replacement (OLAR) capable. If the device is OLAR capable, then there is no memory leak.
• JAGaf37859
  On account of changes in the umask value for root user, STM could not be run by a non-root user.
• Licensing was enabled for the C8000 (running PA8900).
• Memory tools were enabled for the C8000 (running PA8900).
• JAGae62867
  If the user typed rn, ru, rcf, rncf, etc., at the cstm prompt, he/she could not return to the cstm prompt without making a valid selection.
• JAGaf39374
  The memlogd man page in the Other files section had an incorrect name for the memlogd activity log (/var/stm/logs/sys/memlogd_activity_log).
• JAGaf38484
  Errors similar to the following error sometimes occured, and could be found logged to diaglogd's daemon activity log, when diaglogd tried to write data for a monitor on the monitor's FIFO:

    ___ERROR_____________________________________________________________
    Diaglogd received (/var/stm/data/cmc_em.fifo) bytes of log data, which
    is larger than the maximum (cmc_em) bytes that can be sent via a fifo
    pipe (10296) to EMS monitor (0). Only (!) bytes were sent successfully.
    Diaglogd will try to send the rest of the record the next time it checks
    it's internal hold list of error entries and won't send any other data
    to this monitor until then.
    ___ERROR______________________________________________________________
    

  Now the fix has been made to replace garbled and out-of-order data under "()" to have relevant and/or meaningful data.

• Licensing functionality has been enabled for PA 8900 on 11.11.
• JAGaf36171
  This relates to diagmond, the ID module, and mstm.

  When an unrecognized SCSI Processor was connected to the system, the ID module was returning an unitialized string to diagmond. If the uninitialized string turned out to be a unicode character, then mstm crashed.

• JAGae68214
  Whenever the user escaped to the OS from MSTM, and returned to MSTM after invoking the vi editor at the shell prompt, the arrow keys failed to work.
• The cclogd manpage has been updated to include a section containing the list of systems on which the daemon is supported.
• JAGaf16336
  Uninstalling an hp-only license caused error messages to be logged in the local system activity log on a V-class machine.
• JAGae77022
  Diaglogd was logging envd messages sucessfully, along with an error. This error was misleading, because it might cause the user to get confused as to whether logging was successful or not.
• JAGaf24485
  A situation existed wherein memlogd on cell-based machines might not monitor all the cells. Thus, errors reported on memory belonging to those cells might not be reported.
• Event definition file was updated to include 2 events. This update allows Forward Progress Log (FPL) monitor to monitor 2 events.
• Code changes were made to support Processor sets for CPU tools.
• The Intelligent Platform Management Interface (IPMI) Event Library (tlcomev) has been enhanced to decode IPMI events of type 2.
• JAGae30446
  SCSI decoder messages describing the "Unit Attention" condition of a SCSI device have been enhanced to provide greater detail.
• JAGaf42474
  This problem occurs on rp3440, rp4440 and C8000 machines only.
  The address reported by memlogd (Memory Error Logging Daemon) was in an incorrect format and was not interpreted by the operating system. Therefore, the action taken by the operating system upon the occurrence of a single bit error was incorrect. However, the memlogd and the memory monitor (dm_memory) reported the correct DIMM slot, but memlogd was terminating the addresses reported to 32 bits. The address termination was causing the Memlog DIMM information and the Page De-allocation Table (PDT) DIMM information mismatch in case of higher addresses. The memlog was reporting the correct address in this case. This problem has been fixed. This fix requires Firmware Revision 44.44 or any higher revision. If the firmware fix is not available, the functionality of Memory Error logging daemon would be broken and it would report all addresses as zero.
• Code changes were made to pre-enable C8000 on workstations running on PA8800(new).
• JAGaf25052
  The psmctd daemon does not start at times.
• JAGaf25305
  On PA systems, STM reports RAIDSA controllers as RAID160. This is incorrect.
• JAGae65649
  Error messages logged by system library have been modified.
• JAGaf37842
  Permissions for the /var/stm/logs directory are incorrect.
• JAGaf26526
  Tombstone file from pdcinfo not complete following HPMC on rp4440.

General Changes to Tools

• JAGaf12089
  aplsrv IDs were too long and ambiguous in some cases. Those IDs are modified.

Changes to Specific Tools

• Information tools:
  • JAGaf16590; JAGaf19602
    When the system Information tool is not installed on a system, the monitor will not be able to retrieve the related system information. Events generated will display an "unavailable" string, instead of the system serial number, system original product number, and system current product number, in the additional system data text.

    It was incorrect for this error to contain a hardware path. The fix is to have no hardware path in the message. Also, typos were fixed in the catalog file.

  • Code changes were made to pre-enable C8000 (running PA8900).
  • JAGaf36936
    The display of power supply failures has been corrected.
  • JAGae95263
    The display of CPU information has been corrected on multicore systems.
  • Code changes were made to enable Pinnacles PA8900.
  • JAGae84418
    The message indicating PDC call failure, while obtaining FRU information, has been modified.
  • JAGaf19257
    Code changes were made for the removal of support for one of the firmware call options.
  • JAGaf42491
    On 64-way superdomes, System Information Tool does not display information related to all the processors.
• Exerciser tools:
  • JAGaf37694
    This relates to memory exerciser.
    The memory exerciser was encountering intermittent (non-critical) communication problems with diagmond, when run along with CPU Exerciser, on large configurations for extended periods of time.
  • JAGaf16953, JAGae98745
    Error handling for disk exerciser has been enhanced. Different error conditions are handled now.
• Verifier tools:
  • N/A
• Diagnose tools:
  • The memory diagnostics tools have been enabled for PA 8900 on 11.11.
• Firmware Update Tools:
  • JAGaf40627:
    While upgrading the firmware on DS2405 that is connected using A6826A HBA from HP04 to HP05, the STM Firmware Update Tool was failing.
• Expert tools:
  • JAGaf21150
    Code changes were made to prevent the deconfiguration of CPU #1 on PA8800 Processors, since selecting CPU #1 will lead to deconfiguration of the Monarch Processor.
• Logtool:
  • N/A
• Utilities:
  • N/A
• Contrib tools:
  • IPMI Event Viewer (slview) has been enhanced to display the decoded IPMI events of type 2.

Known Problems

• N/A

Defect Reporting

Use CHART to report defects in STM. The project name is diag 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