Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

Because networking information can be changed using the interface and will not be overwritten
by files extracted from the image, it is natural to think about sharing recovery images for systems
with identical or nearly identical hardware. But unlike shared configurations that appear in the
configuration list for all clients, network recovery configurations only appear in the configuration
list of the client for which they were created.
The source for shared configurations is the /var/opt/ignite/data/INDEX file that is created
when Ignite-UX is installed, and the source for client-specific configurations is the CINDEX file that
is created by make_net_recovery in the /var/opt/ignite/clients/client directory.
One simple way to share a recovery configuration among two systems with similar hardware is
to copy the CINDEX file and the recovery directory of the client with the image to the directory of
the client without the image. The fact that the entries in CINDEX use relative paths means you do
not have to change the CINDEX file when you copy it. You will need to NFS export the directory
containing the image to the sharing client. For detailed information on this process, see “Cloning
a System Using make_net_recovery” (page 216).
Question:
I do not want to interact with the user interface after I reboot the client. How can I have my latest
network recovery image chosen automatically?
As long as the client is currently booted, use bootsys -a to start the installation process on the
client without the need to interact with the user interface.
Ignite-UX chooses a configuration to use based on these guidelines:
• If /var/opt/ignite/clients/client/config exists, use the cfg clause specified there.
• If /var/opt/ignite/clients/client/config does not exist, use the default cfg clause
for the client.
The default cfg clause for the client is the last applicable entry set to true in the CINDEX file
if it exists. Otherwise, the default cfg clause is the last applicable entry set to true in the INDEX
file. Because make_net_recovery sets the most recently created recovery cfg clause to true
in CINDEX whenever it creates a new image, that will be the default unless it is manually
changed.
To set Ignite-UX to choose the latest network recovery image automatically:
1. Rename or remove the config configuration file currently in the client’s directory, or use the
bootsys -f option.
2. Run this from the Ignite-UX server:
bootsys -a client
For information on automating an installation, see the descriptions of run_ui,
control_from_server, and INST_ALLOW_WARNINGS in instl_adm(4).
Question:
What causes tftp errors when recovering or installing a system?
• Only /opt/ignite and /var/opt/ignite should be needed for tftp access.
• Check /etc/inetd.conf
• Files in INDEX should not be in directories outside /opt/ignite and /var/opt/ignite.
Question:
What can I do when problems occur from hot-swapping disks during recovery?
Ignite-UX supports only hot-swappable disks that are completely in place and not removed when
creating a recovery image. Proper software and hardware procedures must be used for hot-swap
disk removal or replacement before or after recovery, but not during. The LVM command,
218 Recovery