HP XC System Software Administration Guide Version 3.1

Global service configuration scripts are located in the /opt/hptc/etc/gconfig.d directory.
• Node-Specific Configuration
The node-specific service configuration step uses the results of the global service configuration step
described previously to apply to a specific node its “personality” with respect to the service. User
interaction is not permitted because this step runs on a per-node basis.
The configuration of the service is accomplished in a script called by the node-specific service
configuration controller (nconfig) script. The nconfig controller script runs at system startup, and
it reports if is executing as part of the initial boot of a client node after an installation operation. If so,
the nconfig controller script queries the CMDB to determine which node-specific service configuration
scripts to execute, thus providing the per-node personality to each node.
Per-node configuration scripts are located in /opt/hptc/etc/nconfig.d directory.
Run the per-node configuration scripts on each node with the following commands after successfully
synchronizing each client node with the golden image. This returns the per-node personality following
the golden image update:
# cexec -a -x `nodename` -f128 "/sbin/service nconfig nconfigure"
# cexec -a -x `nodename` -f128 "/sbin/service nconfig nrestart"
The number of simultaneous remote commands are increased by using the cexec command's -f option.
You can monitor the execution of the per-node configuration scripts from a central location by monitoring
the /hptc_cluster/adm/logs/imaging.log file. Run the following command from the imaging
server node (currently, the head node):
# tail -f /hptc_cluster/adm/logs/imaging.log
The per-node configuration scripts log their execution locally to the /var/log/nconfig.log file.
10.4 Determining Which Nodes Will Be Imaged
The startsys command features a --test option that returns a list of nodes that have been set to be
imaged on the next boot, as shown here:
# startsys --test
Enabled nodes: n[1-512]
Removing the execution node: n512
Boot hierarchy of specified nodes is: n[498-512],[1-497]
Available nodes that require imaging -> n[1-511]
10.5 Golden Image Checksum
Each time the golden image is created or updated, a checksum of the golden image file structure is
computed, and a timestamp is recorded. This helps to ensure the integrity of the created golden image
tar file, and to identify the unique revision of the golden image. Both the checksum and the timestamp
are saved in the hptc_system table of the configuration and management database (CMDB). You can
view this information with the dbsysparams command, as follows:
# dbsysparams -r '.*'
cmdb_version: 1.26
golden_client: n512
golden_image_md5sum: 2e22d69e5c8b0bc0570b0dfffe5883a1
golden_image_modification_time: date and time stamp
golden_image_tar_valid: 1
golden_image_valid: 1
imaging_log_server_port: 523
node_prefix: n
NTP_SERVER1:
NTP_SERVER2:
NTP_SERVER3:
10.4 Determining Which Nodes Will Be Imaged 135