STM Release Notes for HP-UX 11i v3 March 2012 release

Prerequisites
Following are the prerequisites for installing Diagnostics and Support Tools:
EMS version A.04.20.31 or later
ProviderSvcsBase C.01.00.xx (March 2009) or later
Notes:
• The requirements are available on the Operating Environment (OE) media.
ProviderSvcsBase: The ProviderSvcsBase product offers interface for user space processes
(typically, but not limited to, WBEM Indication Providers) to retrieve error logs from HP-UX
Kernel. Using these error logs, a user space process can generate event (WBEM indication
or EMS event), when an event of interest occurs on the system.
• The OnlineDiag depot is available for download on the OE media and web. Starting from
HP-UX 11i v3 September 2011 release, all the products namely ProviderSvcsBase,
SysFaultMgmt, the I/O Providers namely HP-UX WBEM RAIDSA Provider, HP-UX WBEM SAS
Provider, HP-UX WBEM Fibre-Channel Provider, HP-UX WBEM Direct Attached Storage Provider
(DASProvider) must be installed together to maintain compatibility among the diagnostic
products.
On web:
September 2011 web release onwards, all the HP-UX 11i v3 version of WBEM
providers and Diagnostics products, are available for download on the WBEM
Management bundle for HP-UX 11i v3 bundle page at https://
h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=WBEMMgmtBundle.
NOTE: HP's WBEM Management bundle is released only on the web. All the
products from the WBEM Management bundle must be installed together. This is
due to product interdependency. These products might not work if they are installed
individually.
Defect fixes
This section describes the defect fixes and changes made to STM for the current release.
The following information applies to both Itanium Processor Family (IPF) and PA-RISC systems:
• None
The following information applies only to Itanium-based systems:
• QXCR1001172803
Problem: The cstm tool crashes while running the (ff) command.
Problem Description: While running file format (ff) command in cstm, the tool crashes
because the memcopy system call inlined using high optimization.
Resolution: This issue is fixed.
• QXCR1001142456
Problem: A warning message is logged by diag2 to syslog.log file.
Problem Description: A DIAGNOSTIC SYSTEM WARNING message is logged by diag2 which
mentions the STM and the names of diaglogd processes on HP integrity and NGIS systems
even though OnlineDiag is not supported.
Diagnostic System Warning:
The diagnostic logging facility has started receiving excessive errors from the I/O subsystem. I/O error
entries will be lost until the cause of the excessive I/O logging is corrected. If the diaglogd daemon
is not active, use the Daemon Startup command in stm to start it. If the diaglogd daemon is active, use
the log tool utility in stm to determine which I/O subsystem is logging excessive errors.
2 Contents