HP XC System Software Installation Guide Version 3.2.1

# shownode config hostgroups
hostgroups:
headnode: n16
serviceguard:avail1: n14
n16
In this example, one availability set, avail1, has been configured.
2. On one node in each availability set, view the status of the Serviceguard cluster:
# pdsh -w n14 /usr/local/cmcluster/bin/cmviewcl
NOTE: The /usr/local/cmcluster/bin directory is the default location of the
cmviewcl command. If you installed Serviceguard in a location other than the default, look
in the /etc/cmcluster.conf file for the location of the Serviceguard bin directory.
Successful command output is similar to the following:
CLUSTER STATUS
avail1 up
NODE STATUS STATE
n14 up running
PACKAGE STATUS STATE AUTO_RUN NODE
nat.n14 up running enabled n14
NODE STATUS STATE
n16 up running
PACKAGE STATUS STATE AUTO_RUN NODE
nat.n16 up running enabled n16
lvs.n16 up running enabled n16
nagios.n16 up running enabled n16
dbserver.n16 up running enabled n16
4.3 Task 3: Run the OVP to Verify Software and Hardware Components
The operation verification program (OVP) verifies the major HP XC software and hardware
components to provide a level of confidence that the system has been installed and configured
correctly.
The OVP performs various tests to verify the following:
• The interconnect is functional.
• Network connectivity has been established.
• The administration network is operational.
• A valid license key file is installed and the license manager servers are up.
• All compute nodes are responding and are available to run applications.
• SLURM control daemons are responding and partitioning is valid if LSF-HPC with SLURM
is configured.
• LSF is up and running, if LSF is configured.
• An MPI job can be compiled, launched, and executed (through the xring test)
• Serial and parallel applications can be submitted and executed through LSF from all compute
nodes, if LSF is configured.
• CPU usage on all nodes except the head node (by default).
• Memory usage on all compute nodes but not the head node (by default).
4.3 Task 3: Run the OVP to Verify Software and Hardware Components 115