HP XC System Software Administration Guide Version 3.0

# tail -f /hptc_cluster/adm/logs/imaging.log
The per-node configuration scripts log their execution locally to the /var/log/nconfig.log file.
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]
The 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 s
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:
RPCNFSDCOUNT: 8
xc_version: Version number
The table entry golden_image_md5sum identifies the MD5 checksum of the golden image file structure.
The table entry golden_image_modification_time identifies the date and time the current golden
image was created.
The table entry golden_image_tar_valid is set to 1 when the compressed tar file of the golden image
is created. It is set to 0 while the during the creation of the golden image tarball.
The table entry golden_image_valid is set to 1 when the golden image file structure is successfully
created. It is set to 0 while the golden image file structure is created. The startsys command uses these
flags to identify whether it is possible to image nodes successfuly imaging operation is possible, based on
the state of the file structure and compressed tar file.
The golden image checksum and timestamp are imaged out to all nodes, by an override file, which allows
client nodes to identify their loaded image, relative to the golden image. The /var/hptc/gi_md5sum file
on each client node contains the checksum and timestamp. You can identify them as follows:
# cat /var/hptc/gi_md5sum
golden_image_md5sum=2e22d69e5c8b0bc0570b0dfffe5883a1
golden_image_modification_time=date and time stamp
A simple check to identify which nodes are running which versions of the golden image is as follows
# # cexec -a -x `nodename` "cat /var/hptc/gi_md5sum" | dshbak -c
----------------
xc9n[1-511]
----------------
Determining Which Nodes Will Be Imaged 83