Ignite-UX Installation Booting

This program is responsible for loading everything else required from the tape to start the kernel

(along with its install file system) and hence set the recovery going.

The kernel completes its initialization. The installation continues with the kernel running init from

the installation file system loaded by the bootloader.

The Ignite-UX Administration Guide contains information on how to configure boot manager menu

options for tape boot on HP Integrity servers that support it.

Booting from a LAN

System booting from a LAN is as follows:

1. At the EFI boot manager menu, select a LAN device to boot from, or use the lanboot

command at the EFI shell prompt.

Please consult the documentation appropriate to the system for information on how to use EFI or

how to configure the boot manager menu.

2. The firmware sends a DHCP request with an Itanium®-based class-id set.

The DHCP server on HP-UX 11i v2 (B.11.23) and later replies to Itanium®-based PXE boot

requests, if configured appropriately.

For more information regarding how to configure DHCP on an HP-UX B.11.23 or later system to

respond correctly to Itanium®-based PXE DHCP requests, refer to the Ignite-UX Administration

Guide.

If a DHCP PXE response to a PXE boot request includes a class-id, it will attempt to contact a

PXE proxy server on the responding host. HP-UX does not currently provide a PXE proxy server,

so a DHCP PXE response including a class-id will cause a network boot to fail. HP-UX

releases prior to HP-UX 11.11 do not have the appropriate option to allow you to configure

DHCP to exclude a class-id in the DHCP PXE response. On HP-UX 11.11 (with

PHNE_28762 or later installed) and on HP-UX 11.23 and later from first release, the ncid

keyword prevents the class-id from being included in the PXE response. Other keywords

were also added at HP-UX 11.23 to make configuring DHCP for booting HP Integrity systems

easier. One of these keywords is re – without this keyword it is significantly harder to create a

dhcp_device_group in /etc/dhcptab that supports only anonymous booting of Itanium

clients, as you cannot use basic regular expressions to match the Itanium PXE DHCP class id.

3. The DHCP response directs the system to download /opt/ignite/boot/nbp.efi (“nbp”

means “network bootstrap program”) to continue booting.

4. After the nbp.efi process is downloaded and executed, it downloads and executes the

bootloader, hpux.efi.

5. The bootloader downloads the AUTO file, /opt/ignite/boot/AUTO.

The contents of the AUTO file control the operation of the bootloader and usually contain the

boot IINSTALL command.

6. The bootloader downloads the installation kernel, IINSTALL, and the installation file system,

IINSTALLFS, and executes the kernel.

HP Integrity systems cannot ask their bootloader to perform additional tasks (like the secondary

bootloader does on HP9000 systems). Because of this, the bootloader must load the installation