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

1. During a recovery, the original I/O configuration is restored if I/O instance data is present
in the config. Some aspects of the configuration might be instantly changed. Some aspects
are temporarily changed and will be finalized during reboot. If the current system is different,
some aspects of the I/O configuration will be impossible to restore.
2. Create disk partitions if needed (Integrity systems only).
3. Create volume manager volumes as needed.
4. Create and mount file systems.
5. Determine software sources and selections.
6. Run pre-config control scripts.
7. Set boot path.
8. Set up and enable swap space.
9. Save final volume configuration data to disk file system.
10. Set locale.
11. Move needed content from RAM file system to disk file system. Load the complete set of
commands, libraries, and other files required to accomplish installation and recovery from
Ignite command archives to the new disk file system (SYSCMDS or SYSCMDSIA).
12. Change the root directory to the disk file system with chroot.
Phase 2
File content is installed or restored. The result of this phase is the final disk file system and content.
Some cleanup and processing that must be done after system reboot is still required. For the HP-UX
install kernel, the RAM file system is still the root disk. For the commands in this phase, the new
disk file systems is the root file system. A reboot is required to change the HP-UX kernel root disk
from the RAM disk to the final disk.
1. Release RAM disk space to accommodate software installation and kernel build processes to
be done later.
2. Load the archive if indicated in the config (for recovery and golden image installation).
3. Update mnttab so it appears to be correct during installation and kernel build.
4. Create device special files.
5. If needed, rename device files to make the I/O configuration appear fully restored.
6. Update bootconf.
7. Change I/O configuration files to match final instance config using ioinit and ioscan
-M.
8. Load depot-based software if indicated in the configuration.
9. Save configuration so it is available for reuse.
10. Build final system kernel.
11. Set up the inittab file so final Ignite-UX processing will be done after reboot.
12. Reboot system.
Phase 3
Software is configured and final installation or recovery cleanup is done. The result of this phase
is a fully installed or recovered system, ready for use after reboot. If configuration has been deferred,
the system will be set up to run FIRST-BOOT set_parms on initial boot so you may choose the
hostname, IP address, and other settings. Processing for this phase is done using the final disk-based
file system.
1. Update the AUTO boot file.
2. Configure software.
3. Configure final networking.
4. Generate a system manifest.
5. Save the installation information for deferred configuration.
How Ignite Works 21