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
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
•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
1.Rename or remove the config configuration file currently in the client’s directory, or use the bootsys
2.Run this from the
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
System Recovery 217