HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

Introduction
HP Product Interaction
Chapter 1
24
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, adding up the numbers results in a total of nine CPUs
for the server when there are actually only five physical CPUs.
• (PA-RISC only) The WINSTALL Boot Kernel Paths with Different Versions of Ignite-UX and the vparboot
-I command
The examples in this document use the Ignite-UX bootable kernel WINSTALL path as
/opt/ignite/boot/WINSTALL
This is the correct path for Ignite-UX versions B.05.xx and earlier. However, if you are using Ignite-UX
version C.06.xx or later, the WINSTALL path has changed to
/opt/ignite/boot/Rel_B.11.NN/?INSTALL
where NN completes the HP-UX version and
where ? is W for PA-RISC systems
For example, if vPars is using HP-UX 11i v2 (11.23) instances on a PA-RISC server with Ignite-UX
version C.06.xx, the path is:
/opt/ignite/boot/Rel_B.11.23/WINSTALL
Thus, if you are using HP-UX 11i v2 (11.23) on a PA-RISC server and
— Ignite-UX version B.05.xx or earlier:
you should specify /opt/ignite/boot/WINSTALL on the command line (/opt/ignite/boot is the
default); for example
# vparboot -p <target_partition> -I <ignite_server>,/opt/ignite/boot/WINSTALL
— Ignite-UX version C.06.xx or later:
you must specify the absolute path /opt/ignite/boot/Rel_B.11.23/WINSTALL on the command line
(because /opt/ignite/boot is the default); for example
# vparboot -p <target_partition> -I <ignite_server>,/opt/ignite/boot/Rel_B.11.23/WINSTALL
• Ignite-UX Recovery and Expert Recovery
Beginning with vPars A.02.03, the creation of make_tape_recovery tapes is supported on vPars-enabled
servers. However, there are limitations:
— (PA-RISC Only) Recoveries using tapes within the vPars environment is supported beginning vPars
A.03.03, A.04.03, and A.05.01. See “Using make_tape_recovery within a vPars-environment on
PA-RISC Servers (vPars A.03.03, A.04.03, A.05.01)” on page 327 for more information. If you are
using an earlier release of vPars, you must perform the recovery outside of the vPars environment.
— (Integrity Only) Recoveries using make_tape_recovery tapes must be done outside of the vPars
environment; they cannot be used to recover a system from within a virtual partition. For example,
the tape cannot be used with the vparboot -I command. See “Using make_tape_recovery Outside of
a vPars Environment” on page 321 for a sample disaster recovery recipe that uses
make_tape_recovery.
Ignite-UX Recovery via make_net_recovery requires additional steps as noted in “Network and Tape
Recovery” on page 317.