Network

Booting, Installing, Recovery, and Sharing in a vPars Environment from DVD / CDROM / Tape / Network

Page 3 of 6

b) Installing/Creating subsequent boot disks and/or potential vpars

(1) Option1: Installing from outside of vPars (non-vPars

environment)

You can install additional boot disks and potential vpars outside of a

vPars environment serially using the cold install method to create

additional boot disks, each with the potential of being an active vpar.

This method requires the system (or nPartition) to come down to the

BCH or EFI for each install.

Using this method, you serially use the PDC to install to the boot disks

of the additional potential vpars. This is the same as cold-installing on

a non-vPars system, but you’re switching the destination disk each

time. All of this is performed from the BCH or EFI and not within a

vPars environment. After installing the first vpar, you would bring the

system back down to the BCH or EFI and start the HP-UX install

process again, pointing to the same install media again but pointing

to a different destination disk for each potential vpar. What you are

doing is simply creating multiple boot disks in preparation for multiple

vpars. But remember, at this time you are only creating standard HP-

UX boot disks (that have vPars software installed).

(2) Option 2: Installing from within vPars (i.e. the vPars

environment with the vPars Monitor running)

You can install additional vpars from within the vPars environment

using Ignite-UX and starting with A.03.03 and A.04.02, from Tape, to

install the additional vpars. This is performed from a running vpar.

The benefit of this method is the system (or nPartition) does not need to

come down to the BCH or EFI. All existing vpars can be up and

running while you create the additional vpars.

(a) A.04.xx IPF systems and PRE-A.03.03 and

PRE-A.04.02 PA-systems: Reasons You Cannot

Install Subsequent Boot Disks using DVD/CDROM

or TAPE Drives from within a vPars Environment

(i) PDC: The vPars Monitor resides between the PDC

and the OS. Unlike the PDC, the vPars Monitor

cannot traverse the core I/O and HBAs looking for

boot devices. This is the key reason the statement has

been made that you cannot boot vpars (while the

vPars Monitor is running) from DVD, CDROM, or

TAPE.

(ii) Drivers: The OS requires drivers in the kernel to

access boot devices, but a new vpar within a vPars