Ignite-UX Installation Booting

7
host1
host2
host3
vPars
monitor
Booting an HP9000 virtual partition
This example is illustrated with an rp8400 system that has been split into three Virtual Partitions
(vPars). The virtual partition, host1, has already been installed with the vPars software and the
vPars monitor is running. The remaining two virtual partitions have been configured but not
installed.
The virtual partition host1 has Ignite-UX
installed previously and has depots that
contain the HP-UX B.11.11 OE, the vPars
software, and enablement patches. The
required Ignite-UX configuration is
complete.
You execute the vparboot command to
start one of the other virtual partitions so
that you can begin the operating system
installation using Ignite-UX with the
following command:
vparboot -p host2 –I WINSTALL
2
The –I option of vparboot(1M) by
default obtains files from
/opt/ignite/boot if no path is
specified.
In addition, the –I option allows a host
name or IP address with the kernel. When
used in this way, the vparboot command
will tftp the installation kernel and file
system from the remote Ignite-UX server to
the local vPars partition, and then the
installation kernel is passed to the vPars
monitor.
vparboot -p host2 –I \
10.0.0.5,WINSTALL
The monitor uses the installation kernel and file system to boot the vPar
3
This boot process is completely different from the way that a HP9000 system would normally boot.
. The monitor puts the
WINSTALL and WINSTALLFS into the memory owned by the partition that is booting and then
starts the partition running.
2
As of Ignite-UX version C.6.0.x, the vparboot command will not know about the new locations of installation kernels within the Ignite-UX
product. You must give the full path to the installation kernel if you are using vPars and Ignite-UX version C.6.0.x or later. For example, HP-UX
11i v1 (B.11.11) requires /opt/ignite/boot/Rel_B.11.11/WINSTALL and HP-UX 11i v2 (B.11.23) requires
/opt/ignite/boot/Rel_B.11.23/WINSTALL.
3
This description indicates that if there are no partitions running (just the monitor), it is not possible to use a network-based Ignite-UX server
from just the monitor prompt since the monitor is not capable of communicating over the network.