Installing and Managing HP-UX Virtual Partitions (includes A.04.01)

Introduction

HP Product Interaction

Chapter 1

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. However, 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, recoveries using these 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 page 11 for a sample disaster recovery recipe that uses

make_tape_recovery.

Ignite-UX Recovery via make_net_recovery requires additional steps as noted in “Recovery: Ignite-UX

Recovery” on page 205.

Expert recovery works as documented in the Ignite-UX manual; however, you must account for the vPars

differences described in “Recovery: Expert Recovery” on page 211.

For more information on using tape devices, see also the paper titled Booting, Installing, Recovery, and

Sharing in a vPars Environment from DVD/CDROM/TAPE/Network available at

http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions.