HP XC System Software Installation Guide Version 3.0

ln -sf login.master.0 $i.sh
done
8. Do one of the following to install the client nodes:
• If the client nodes were not previously installed with the HP XC System Software, see “Task 9: Run
the startsys Utility To Start the System and Propagate the Golden Image” (page 60) to continue
the initial installation procedure.
• If the client nodes were previously installed, issue the following sequence of commands to set the
nodes to network boot and reboot the client nodes (wait until the stopsys command completes
before invoking the startsys command):
# setnode --resync n[135-136]
# stopsys n[135-136]
# startsys --image_and_boot n[135-136]
Note
If you rerun the cluster_config utility at any time, the symbolic links revert to point to the
base_image.master.0 file, and you must recreate the links.
Static Disk Configuration
Static disk configuration relies on one or more preconfigured (static) disk configuration files that describe
the disk type, size, partition type and layout, and file system type of the disks in your client systems. These
configuration files are used as input to the creation of a master autoinstallation script. Static disk configuration
files follow a particular template as described in autoinstallscript.conf(5) .
In an ideal environment, client disks obtain their configuration directly from the golden client (the head node).
When the golden client and client nodes are of the same platform type, disk type, and disk size, this works
well. However, many HP XC system configurations have a heterogeneous mix of platform types, disk types,
and disk sizes. Allowing client disks to be separately configurable from the golden client becomes a
requirement, and this is a default behavior of the HP XC imaging installation when static disk configuration
is enabled.
Several predefined static configuration files are shipped as part of the HP XC software distribution. These
files match the supported platform types and enable the creation of a disk configuration specific for a
particular server platform. As an example, for a CP6000 cluster platform, the following static disk configuration
files are available in the /opt/hptc/systemimager/etc directory:
• rx1620.conf
• rx2600.conf
• rx2620.conf
• rx4640.conf
• rx8620.conf
During imaging environment creation, if static disk configuration is enabled, a master autoinstallation script
for each platform type detected in the cluster is automatically created with the appropriate static .conf file
used as input.
Each host of a particular server type is linked to its appropriate master autoinstallation script. If a client node
is the same server type as the golden client, the default action is to link the client node to the master
autoinstallation script cloned from the golden client.
By changing the contents of the appropriate .conf file, you can affect the disk configuration for a particular
node or group of nodes by linking those nodes to the associated master autoinstallation script. You can also
create your own .conf files and associated master autoinstallation script.
For information about creating your own master autoinstallation script, see mkautoinstallscript(8) .
Enabling Static Disk Configuration
Dynamic disk configuration method is the default behavior for the HP XC imaging environment. Before you
can use the static disk configuration method to customize the client disk configuration you must enable it.
You cannot use a combination of the two methods simultaneously.
Follow this procedure to enable static disk configuration:
1. Use the text editor of your choice to open the following file:
114 Customizing Client Node Disks