Release Notes for STM on HP-UX 11i (June 2004)
These release notes cover the June 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
- JAGaf17889
The data field of data type "physical location" contains source,
source detail, and levels[0-7]. The data in the level is deciphered
from the combination of source and source detail. In some cases, the
level data would be reserved and would result in '!' being displayed
in the event log file. Modifications have been made so that '!' is not displayed in such scenarios.
- Online memory diagnostics were enabled on HP 9000/785/C8000
and rp4440 platforms.
- Licensing was enabled on rp3440, rp4440, and HP 9000/785/C8000
machines.
- JAGaf02165
The event description was decoding the Reporting Entity ID of the
encoded chassis code, and would provide the Cabinet, Cell, and CPU
information associated with it. This problem has been fixed.
- JAGae42546
Mt_memlogd might show a status of "deallocated" even when the page was
"marked for deallocation". This has been fixed.
- The diagnostics process which creates fru sdr data files has been
renamed from ipmid to diagipmid.
- JAGaf11815
The description of A9782A (1000Base-SX/F Combo Adapter) was changed in
STM. The description of A9784A (1000Base-T/F Combo Adapter) was also
changed in STM.
- JAGae85967
The STM id module now recognises the MSA 1000 Storage Device as
a Disk Array, and the MSA 30 as a Disk Enclosure.
- JAGaf05704; JAGaf06248
In MSTM, when the user selected a default key (options -->Map-->f3) to load default values, the keypad at the bottom disappeared.
This problem was applicable to MSTM only when the user started MSTM on
vt100, xterm, and dtterm terminals. This has now been fixed.
- JAGae40333
A problem with the XSTM Graphical User Interface was fixed, where
XSTM showed more than one highlighted device, when the user
selected a device from the text map. This problem appeared only in the
XSTM text map, and if the device path exceeded 20 characters, and one
or more devices showed the same string (map entry) in the text map.
- JAGae36443
Memlogd was terminating, because the Astro Chip (used on the A-Class,
and on some L-Class systems and workstations) is sometimes unable to
convert an address to its physical location.
This has been fixed now.
- JAGae65172
Fixed a problem with the XSTM Graphical User Interface(GUI). STM's
exit dialog box displays three buttons (ok, cancel, help), but the
buttons were very thin and difficult to read.
- JAGaf02267
Code changes were made to diagmond, to prevent the exerciser logs
from being removed.
- JAGae79015
With memlogd, the wrong errno was being reported for some ioctls,
because of system calls which were called before the error was
logged. This has been fixed.
- JAGaf03663
LPMC errors logging is suspended due to an excessive logging rate.
This suspension is vital, as the monitor would miss some valid errors.
The algorithm created for monitoring the PA8800 processor requires
that all LPMCs that are acknowledged by the hardware must be
passed on to the lpmc_em monitor. The reason for this is that the
LPMC for the particular processor (and reason, like L2 cache error) is disabled by the firmware when an LPMC occurs. The diagnostics then
re-enable that LPMC for L2 cache errors, up to 100 during a 15-minute period. All LPMCs must be seen, in order that the true error rate be seen, and so the algorithm can function properly. This problem is
specific to the PA8800.
- JAGae85382
With the hp_memory decode tool, 2 bits were being used to
decode the bus number, instead of 3 bits, from the memory address for
the V-2500 and V-2600 class of machines. This has now been fixed.
- JAGae97875
Memlogd was making multiple requests for de-allocation of pages to the
PDT. This has been fixed.
- JAGae97441; JAGae93156
An intermittent problem with the System Info tool on IPMI machines has
been fixed. If the FRU data is not programmed properly, MSTM UI will
go down, upon receiving some Unicode character data, so all Unicode
characters have been displayed as blanks in the FRU information of
the System Information tool.
- JAGaf01025
LPMC errors are being logged to the os_error_log file, but will NOT
have any information about how many are actually acceptable.
An individual LPMC error logged to the os_error_log file is not
relevant for confirming the system problem. It is necessary to analyze
the correctable errors to determine whether there is risk of system
problems. Threshold analysis is performed by the monitor, and so there
is no need for logging the LPMC errors.
- JAGae96961
The SDR file was sometimes seen as being incomplete by the system info tool. This has now been fixed.
General
Changes to Tools
Changes to
Specific Tools
- Information tools:
- JAGaf14613
Code changes were made to abort the CPU Information tool, if the
selected processor was in an Inactive state, or if the Processor
was not in the current partition in the vPar environment.
- JAGaf06854
Code changes were made to:
- To pre-enable the rp4440 platform.
- To display the CPU speed correctly on rp3440.
- Enable HP 9000/785/C8000 Workstation.
- JAGaf12279
Fixed a problem, where the info command, while running on the
ql_adapter info tool, would display an incorrect
'description'(only) of the fields that the tool displays when run.
- JAGaf08181
New tape device (SDLT600) is not supported by STM, but by LTT.
- JAGaf07246
The Information Log for the FC SCSI MUX Information tool
(scsi_mux) contained an incorrect hardware path. This problem has now been fixed.
- JAGae58017
With the DLPI information tool, the IODC revision was being
displayed for PCI cards, also. This information is not valid for
these card types. This has been fixed.
- JAGae95021
The system info tool has been enhanced to show CPU slots, as well as CPU numbers, in the CPU bitmap, under cell information, on
Dual Core Processor systems.
- Exerciser tools:
- When a tool is running on any one of the CPUs, the CPU
Exerciser tool can't be initiated on any other CPU. Initiating
the CPU Exerciser tool on one CPU, exercises all the CPUs in the
system.
- Code changes were made to the CPU exerciser, to keep it from
hanging, when being run on heavily loaded machines (4 cells or
greater on machines like SD-32000, SD-32A, SD-64000, SD-64A).
- Verifier tools:
- Diagnose tools:
- Firmware update tools:
- Expert tools:
- The behavior of CPU Expert tool has been changed to facilitate
user tasks. The CPU Expert tool used to write the CPU Display
information to the scrolling text window. The impact of this was
that the user would not be able to read display information for
all CPUs, if there were more CPUs on the machine. Now the CPU
Display function writes CPU Display information to an interactive
file viewer. This enables the user to scroll and read informationi
for all CPUs. This viewer can be closed at any time while
scrolling.
CSTM script users will be impacted by this change.
The following is a simple example of the cstm script:
-------------
Select -all
Select Dev 6
ExpertTool
Activate Cancel
Display
Exit OK
--------------
Now the user has to change the script slightly, by adding a "Done"
command after the "Display" and "ExpertTool" commands (By default, the
Expert tool will issue the "Display" command):
------------------
Select -all
Select Dev 6
ExpertTool
Done
Activate Cancel
Display
Done
Exit OK
------------------
- JAGae48303
Memory errors found by the expert tool on cellular machines were
not always logged in the memlog. This is fixed now.
- JAGae90241
Code changes have been made so that the current year is displayed
in the Copyright description of the CPU Expert Information log.
- Logtool:
- Utilities:
Known
Problems
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
Top of Page
/ Diagnostics HOME
URL:
http://docs.hp.com/hpux/onlinedocs/diag/stm/str_0406_11i.htm
Last updated: Wed May 12 10:54:00 PDT 2004