HP XC System Software Installation Guide Version 3.1

BOOT_PERCENTAGE=".01"
ROOT_PERCENTAGE=".49"
VAR_PERCENTAGE=".50"
5. Save your changes to the file.
6. Identify the node names of the login nodes:
# shownode servers lvs
n[135-136]
7. Create a symbolic link from the node names of the login nodes to the newly created master
autoinstallation script. Note that the node name is appended with a .sh extension:
for i in n135 n136
do
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 11:
Run the startsys Utility to Start the System and Propagate the Golden Image” (page 80) 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]
E.3 Configure Disks Statically
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 the 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.
134 Customizing Client Node Disks