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:

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.
WINSTALL and WINSTALLFS are transferred to the vPars Monitor.
the vPars Monitor places them into the memory of the target virtual partition.
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

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.

The vPars Monitor sets the necessary variables such that the EFI shell will execute alanboot select from the target virtual partition.
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.
Using the selected card, the target virtual partition performs a network boot and connects to the Ignite-UX server.
Once connected, the target virtual partition uses tftp to download the bootable kernel and file system IINSTALL and IINSTALLFS
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

Technical documentation

» Table of Contents

» Glossary

» Index

PA-RISC

Integrity