Network

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

Page 2 of 6

III. Booting to Install (CD/DVD, tape, and network boot servers)

The standard devices such as CD, DVD, TAPE, and Network are all supported for the creation of HP-UX

boot disks and may be used to boot install media to begin the installation process for installing HP-UX and

the vPars software bundle onto potential vpar boot disks. Remember that a vPars environment begins with

standard HP-UX boot disks. The boot disks themselves may be created outside of a vPars environment

through the devices mentioned above.

“No Tape, DVD or Network booting” mentioned in other documents refers to booting each vpar within a

vPars environment via these boot devices. “Network booting” specifically means using bootp and does not

mean booting across the network using Ignite-UX.

Please note the difference in Tape Boot functionality between A.03.02 and A.03.03 and the same

difference between A.04.01 and A.04.02 as explained below.

A. Booting and Boot Devices During Installation

1. Non-vPars environment – Cold Install Process Background Information

a) The PDC traverses core IOs and external HBAs to find any available install

devices. Devices such as boot disks can be booted assuming an OS exists.

Other devices such as DVD, CDROM, and TAPE may be booted from if install

media (or recovery media) is found. The network may also be used to install

from if an Ignite-UX server has been set up.

b) The system will boot using the install media and take you through the standard

HP-UX install process, asking questions about what to install and where to

install it. Again, this is referred to as the “Cold Install Process”.

2. vPars environment

a) Installing the first vpar (or rather potential vpar)

(1) The first installation of HP-UX is exactly the same as the installation for

a non-vPars environment. You would use the standard cold install

process (see above) to install the OS and then install the vPars

software. At this point this is a potential but non-active vpar. After the

first boot disk is created, then you have a choice on how subsequent

potential vpar boot disks can be created (see options below).

Note for PA-systems: When planning the assignment of hardware

paths to vpars, the first vpar must own the hardware path of the

console.