As long as the client is currently booted, use bootsys -ato 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 -foption.

2.Run this from the Ignite-UX server: bootsys -aclient

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 must be needed for tftp access.

•Check /etc/inetd.conf

•Files in INDEX must 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, lvlnboot, used by save_config does not work when a disk is removed and the system is in this intermediate state. If this command is not working, a recovery cannot succeed.

Question:

Why is the EFI volume not restored during a recovery?

Ignite-UX destroys the old EFI volume on the boot disk and creates a new EFI volume every time the system is installed. At no point during the installation is the old EFI volume copied and restored to the disk.

To restore the EFI volume to the disk, reinstall the application or look at the SD configure scripts for the application and then rerun the commands that put the EFI volume in place on the disk.

Question:

Why does make_net_recovery fail when the image is 2 or more?

The make_net_recovery command uses NFS to write/read the system image from the client to/from the server. To manage images greater than 2 requires that both the client and server use NFS protocol Version 3 (PV3). NFS PV3 is standard on all HP-UX 11i releases.

222 Recovery