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 operationIgnite 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.
•Phase 2 – HP-UX archives and depot software are installed. The HP-UX kernel is built. A reboot is required to start the final HP-UX kernel and make the new file system the root file system.
•Phase 3 – Software is configured. The system is now fully installed or recovered after a reboot or halt.
Startup
Ignite-UX software is started and the Ignite user interface is run to select, create, or modify the configuration that will be used to control installation or recovery. The result of this phase is a detailed system configuration to be used for installation or recovery. Processing for this phase is done on a RAM file system.
1.The install kernel and install file system are loaded from the boot source to the client memory via boot loader functionality. The HP-UX install kernel is started.
2.The Ignite software is started by the install kernel as an application process running on the install file system.
3.Additional RAM file systems are created to allow enough file system space for loading system setup content.
4.If the system has SAS disks, the I/O configuration is modified as needed to make the mapping between bays and HW paths consistent. This aids consistent installation and recovery.