node0: ERROR: Could not open input file /opt/clustertest/bin/smartscripts/Get_FW_Version.xml
node0: Error processing the XML file: /opt/clustertest/bin/smartscripts/Get_FW_Version.xml
To ensure the Linpack test runs successfully, install the hponcfg package and the
1.Install the hponcfg RPM package on all nodes.
#rpm
2.Create the directory /opt/clustertest/bin/smartscripts/.
#mkdir
3.Extract the
#tar
NOTE: Download the HP
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/ ?lang=en&cc=us&sp4ts.oid=3884114&swItem=MTX_56762b8a5af94509901cca5940
8.Update the Cluster Test configuration file to define the cluster specifics. Do this by invoking Cluster Test:
#testnodes.pl
If this is the first time you have started the GUI, you will see a message window:
5 of 12 config file entries are missing/invalid
After clicking OK, the Cluster Test configuration settings window is displayed. Check each entry and modify as necessary:
•Cluster Test base directory – The location of the Cluster Test installation. This should always be /opt.
•Admin network alias name – The node prefix used in /etc/hosts for each node. The default is "node".
•Interconnect type – Must be one of the following. Note the entry is case sensitive.
◦
◦
◦
◦
Admin – When there is no separate interconnect and the Admin network is to be used as the interconnect.
GigE – When the interconnect is GigE.
10GigE – When the interconnect is 10GigE.
InfiniBand – When the interconnect is InfiniBand.
•Interconnect alias name – The interconnect alias prefix used in /etc/hosts. The default is "inode".
•Node number range managed by this head node – For large clusters there can be several head nodes, sometimes configured on a per rack basis. This entry specifies the nodes to be managed by this head node. For clusters with one head node, the entry is for the entire cluster, for example
•Node number range of the entire cluster – Range of node numbers that describe the entire cluster, for example
