HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

Note that only the vPars shell command vparboot can be used to boot a subsequent virtual
partition for installation (or recovery); the vPars Monitor command vparload cannot do this. Thus,
you need at least one virtual partition successfully booted to use the vparboot command.
Integrity
The following is the sequence of events when a vparboot -I is issued from an existing virtual
partition to boot a target virtual partition for an Integrity System:
NOTE: vPars A.05.04 supports Directed Lan Boot (DirectBoot) capability. With this feature, you
can install to a virtual partition from an Ignite Server which can be in a different subnet. For more
information, see the vparboot(1M) and vpardbprofile(1M) manpages.
1. The vPars Monitor sets the necessary variables such that the EFI shell will execute alanboot
select from the target virtual partition.
2. lanboot select lists the lan cards that are supported for boot that are within the target
virtual partition and prompts the user to select one of the listed cards.
NOTE: You will need to switch to the console of the target virtual partition using Ctrl-A to
see the list of cards.
3. Using the selected card, the target virtual partition performs a network boot and connects to
the Ignite-UX server.
4. Once connected, the target virtual partition uses tftp to download the bootable kernel and file
system IINSTALL and IINSTALLFS
5. Then, the target virtual partition uses IINSTALL and IINSTALLFS to boot and contacts the Ignite-UX
server for the remainder of the installation.
Therefore, you should ensure the following:
• The target virtual partition owns a network card that is supported for boot on Integrity.
For more information on supported network cards, see the section titled “Networking Cards”
in the HP-UX Virtual Partitions Ordering and Configuration Guide.
• The selected network interface card (NIC) 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. Note that in this case, the MAC address
of the selected NIC is in the Ignite-UX server’s/etc/bootptab.
◦ 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. Note that in this case, the MAC address of the selected NIC must be in
the boot helper’s/etc/bootptab.
CAUTION: lanboot select connects to the first Ignite-UX server from which its gets a response.
Make sure that the NICs MAC address is registered with only one Ignite-UX server or boot helper
in the subnet. If there are more than one Ignite-UX servers in the subnet and if one of them does
not contain the latest Ignite-UX software, booting from an incompatible kernel may bring down the
entire nPartition.
As on PA-RISC, only the vPars shell command vparboot can be used to boot a subsequent virtual
partition for installation (or recovery); the vPars Monitor command vparload cannot do this. Thus,
you need at least one virtual partition successfully booted to use the vparboot command.
Ignite-UX, the LAN, the LAN card, and vparboot -I 77