HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

Ignite-UX, the LAN, the LAN card, and vparboot -I
NOTE:
Using vparboot -p target_partition -I On both PA-RISC and Integrity, before booting
a virtual partition for installation (in other words, using vparboot -p target_partition
-I...), be sure that you have specified a boot disk using the BOOT attribute
(io:boot_device:BOOT)for the virtual partition. This is performed during either the initial
vparcreate or subsequent vparmodify commands when configuring the target virtual partition.
If you have not specified a boot disk, you will not see the BOOT attribute in the vparstatus
-v output for the target virtual partition:
[IO Details]
0.1
0.8
0.3
If you have, you will see the BOOT attribute in the vparstatus -voutput:
[IO Details]
0.1
0.8
0.3
0.8.0.0.8.0.110.0.0.0 BOOT
PA-RISC
The following is the sequence of events when a vparboot -I is issued from an existing virtual
partition to boot a target virtual partition:
1. the virtual partition from which the vparboot command is run uses tftp to obtain
WINSTALL and WINSTALLFS. Note that the network interface card of the target virtual
partition (the virtual partition you are attempting to boot) is not used in this step. Neither
is bootp used.
2. WINSTALL and WINSTALLFS are transferred to the vPars Monitor.
3. the Monitor places them into the memory of the target virtual partition.
4. the target virtual partition uses WINSTALL and WINSTALLFS to boot and contacts the
Ignite-UX server for the remainder of the installation.
Therefore, you should ensure the following:
• the network interface card that is owned by the virtual partition from which the vparboot
command is issued allows tftp between the Ignite-UX server and this network interface.
You can check the tftp connection by verifying that the following works:
vpar1# tftp <ignite-ux_server>
tftp> get /opt/ignite/boot/WINSTALL
Received 20495138 bytes in 9.9 seconds
• the network interface card of the target virtual partition is able to connect to the Ignite-UX
server. This is performed by either:
— being on the same subnet as the Ignite-UX server
— entering IP and route information on the Ignite-UX screen that will be displayed on the
console during boot
— contacting a DHCP server (boot helper) to obtain the IP and route information to the
Ignite-UX server
74 Installing, Updating, or Removing vPars and Upgrading Servers with vPars