HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

◦ PCI Error Recovery Product Note
◦ PCI Error Recovery Support Matrix
• Support Tools
For information on the required version of the Support Tools package that can run on your
vPars server, see the section on Online Diagnostics in the HP-UX Virtual Partitions Ordering
and Configuration Guide.
Prior to STM version A.43.00 (December 2003), in a vPars environment if the LPMC (Low
Priority Machine Check) Monitor (now known as CPU Monitor) of the Support Tools bundle
deactivates a processor, it does not automatically replace the failing processor with an iCAP
(formerly known as iCOD) processor. The processor replacement must be performed manually
using theicod_modify command. For more information, see the Instant Capacity User’s
Guide.
Beginning with STM version A.43.00, in a vPars environment, the LPMC monitor automatically
replaces a failing processor with an iCAP processor if an iCAP processor is available.
CAUTION: CPU Expert Tool is supported on vPars servers. However, using this on vPars
servers may cause unpredictable results. For complete information on using the Support Tools
with vPars, go to the BSC website at www.hp.com/go/hpux-diagnostics-online-docs and see
the STM and Virtual Partitions (VPAR) document.
• CSTM’s CPU Info Tool
With STM version A.43.00, the CSTM's cpu info tool will show information about the bound
CPUs assigned to that partition and unbound CPUs not assigned to any partition. For unbound
CPUs assigned to other partitions, it shows N/A.
With STM version C.48.00 (HWE0505) and later, the CSTM's cpu info tool will show
information about all the CPUs that are assigned to the current partition.
When using CSTM’s info command, information is shown only for the CPUs that are currently
owned by the virtual partition from which the info command is run. For CPUs which are not
assigned to the virtual partition, the information is displayed as N/A.
• ODE Diagnostic and I/O Card Utilities (Integrity Only)
ODE diagnostics utilities, such as CEC, CPU, or MEM, do not operate in vPars mode. Also,
the I/O card and diagnostic utilities, such as FCFUPDATE and IODIAG.efi, do not operate
in vPars mode.
You must boot the nPartition into nPars mode to operate these utilities.
For more information on modes, see “Modes: Switching between nPars and vPars Modes
(Integrity Only)” (page 124)
• Ignite-UX
◦ Making Depots for Ignite-UX:
For information on where to find a “cookbook” for setting up your Ignite-UX server for
use with vPars, see “Setting Up the Ignite-UX Server” (page 75).
◦ Reading the CPU counts from Ignite-UX (vPars A.03.xx and earlier):
When Ignite-UX reports the Total Number of CPUs for a partition, it includes unassigned,
unbound CPUs in the count. For information on bound and unbound CPUs, see “CPU:
Bound and Unbound” (page 239).
For example, if you have three virtual partitions, each with one bound CPU, and two
unbound CPUs not assigned to any of the partitions, this is a total of five CPUs in the
server. Ignite-UX will report three CPUs (one bound and two unbound CPUs) for each
partition. The data on unbound CPUs is repeated for each virtual partition. Therefore,
20 Introduction