6.Change the system networking parameters for the client during the installation.

For additional information regarding system cloning, see the Successful System Cloning using Ignite-UXwhite paper at

http://www.hp.com/go/ignite-ux-docs.

System recovery questions and answers

Question:

Can I use a network recovery image if my system is not on the same subnet as the Ignite-UX server?

Yes, there are the commands make_boot_tape , make_ipf_tape, and make_media_install that create minimal boot media for use by any client. The media contain just enough information to boot a client and then connect to the Ignite-UX server where the tape, CD, or DVD was created. If that is the server where the client’s recovery configuration files are stored, then the client can be recovered.

It is not possible to boot all systems from a tape device. See “Tape recovery with no tape boot support — two-step media recovery” (page 217).

If you initiate recovery tape creation from the Ignite-UX server, the server will warn you if the client requires boot media. If you ignore this warning, misplace your boot media, or find that your media are for the wrong Ignite-UX server, you can always create new boot media on the server you want to use. There is no client-specific information on the media.

Notice that media created by make_boot_tape, make_ipf_tape, and make_media_install are useful not only for recovery situations, but also for ordinary installations. If you do not want to set up a boot helper for systems on a separate subnet than the Ignite-UX server, you can simply create bootable media.

For more information, see Chapter 14 (page 180), make_boot_tape(1M), and make_ipf_tape(1M).

Other options include direct boot profiles (see “Direct boot profiles for Itanium-based systems” (page 102)) and boot helpers (see “Ignite-UXbootp boot helper” (page 56)).

Question:

How can I change my setup so a network recovery image is available not only on the system for which it was created, but also on other systems with very similar hardware?

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 220).

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?

System recovery 221