HP XC System Software Administration Guide Version 3.2

The --infile and --outfile options to the cluster_config command enable you to export
and import configuration data, and to bypass much of the cluster_config utility interface if
the hardware configuration is unchanged. The configuration data includes the configuration of
availability sets (for systems using improved availability), role assignments, and external
connections. The following lists the sequence of events for using the cluster_config command
with these options:
1. Save the current configuration to a file with the --outfile option of the cluster_config
command:
# cluster_config --outfile conf_file
2. Copy the output file to a file system external to the HP XC system.
3. At some time, you may need to reinstall or modify the existing configuration.
4. Copy the saved configuration file from the external file system back on to an HP XC system
file system, preferably to a disk local to the head node.
5. Run the cluster_config command with its --infile option; specify the saved
configuration file:
# cluster_config --infile conf_file
For more information about this command, see cluster_config(8) and the HP XC System Software
Installation Guide.
11.6.2 The updateimage Command
The updateimage command updates the golden image from the golden client; it does not run
any service configuration scripts. As superuser, you must run this command on the golden client
node. The updateimage command provides a --dry-run option. This option enables you to
inspect the files that will be added to (or deleted from) the golden image, without making any
changes.
In the following example, the nodename command is executed and resolves to the node name
of the golden client:
# updateimage --gc `nodename` --dry-run
If you are satisfied with the list of files that will be updated in the golden image, issue the
command to perform the update:
# updateimage --gc `nodename`
When the updateimage command completes, the golden image is synchronized with the golden
client and the golden image tar file is updated. You are ready to deploy the golden image to all
the nodes in your HP XC system.
Note:
By default, the updateimage command sets all client nodes to network boot from their Ethernet
adapter, connected to the administration network, the next time the nodes are rebooted. This
causes the nodes to reinstall themselves automatically, thus receiving the latest golden image.
On CP6000 systems, for nodes to be set to network boot, the nodes must be operational. The
updateimage command displays any nodes that could not be reached and thus are not set to
network boot. This is a problem only on CP6000 systems because each node's EFI environment
must be modified. You must resolve the EFI environments manually for those nodes. If the node
is not operational when the updateimage command is run, you must set the nonoperational
nodes to network boot from the EFI boot menu the next time the nodes are booted.
The --no-netboot option of the updateimage command overrides this default action and
maintains the boot order for each client node.
Run the following command to update the golden image but keep the client nodes from network
booting the next time the nodes are rebooted:
148 Distributing Software Throughout the System