Ignite-UX Administration Guide for HP-UX 11i (B3921-90080, November 2013)

Ignite can switch its source for command archives and depots if configuration information in the
install file system instructs it to, or if instructed to by the Ignite user interface.
Ignite will operate in the same manner, regardless of the boot source.
Installation Versus Recovery
Ignite internally uses the same approach, regardless of whether you are performing an installation
or recovery. The terms “installation” and “recovery” are valuable to describe intended use, but
Ignite's internal operation make it possible to blur the distinction between the two, such as when
you use golden images.
This design is quite powerful, and allows Ignite to handle significant system differences during
recovery by adapting as needed and regressing to more install-like behavior if required.
Network Booting and IP Addresses
When a system boots HP-UX from an Ignite-UX server, it needs an IP address to get the operating
system kernel. This first IP address is not necessarily the same IP address the system will be assigned
for networking when its kernel is up and running. The mechanisms for distributing the first and
second IP addresses are sometimes different.
PA-RISC Systems
When a PA-RISC system boots from an Ignite-UX server, the first IP address request is answered
by the instl_bootd daemon. This communication uses ports 1067 and 1068. The file /etc/
opt/ignite/instl_boottab is referenced to assign the first IP address to the booting system
whether it is registered or anonymous.
After HP-UX is running on a PA-RISC system, it requests a second IP address for networking. This
request is answered by bootpd using ports 67 and 68. The /etc/bootptab file is referenced
for registered clients; DHCP services are used for anonymous clients.
Itanium-Based Systems
When an Itanium-based system boots from an Ignite-UX server, the first IP address request is
answered by the bootpd daemon. This communication uses ports 67 and 68. The file /etc/
bootptab is referenced to assign the first IP address to a registered booting system. If the system
is not registered, and you are running HP-UX 11i v2 or HP-UX 11i v3 on the Ignite-UX server, DHCP
is used to assign the booting IP address.
When Itanium-based systems request a second IP address for networking, it uses the same daemon,
file and ports described above. Configuring DHCP for booting is separate from configuring DHCP
for assigning network IP addresses. See “Configuring an Ignite Server to Boot Anonymous
Itanium-Based Clients” (page 44) for information about how to configure DHCP for assigning first
(boot) and second (networking) IP addresses without conflict.
Phases of Operation
Ignite uses the sequence of high-level phases outlined below to accomplish installation and recovery.
Depending on configuration information, some steps within these phases might be skipped. At a
very high level, Ignite operates in four phases:
• Startup – The install environment is loaded from the boot source to the client memory. Ignite
runs in client memory. The operation is configured and launched. If the installation or recovery
is interactive, the user interface is run to create a configuration.
• Phase 1 – Storage is set up and Ignite moves to the client disk.
How Ignite Works 19