HP XC System Software Administration Guide Version 3.2

8. Find additional information about InfiniBand in the /sys/class/infiniband* directory.
Use the find command to locate the information:
# find /sys/class/infiniband* -type f -print -exec cat {} \;
9. Consult the documentation for the available OFED commands located in the
/usr/local/ofed directory tree; there are manpages for the commands and other online
OFED documentation in the /usr/local/ofed/docs and
/usr/local/ofed/src/openib-1.1/Documentation/infiniband directories.
The InfiniBand vendors also have OFED documentation available from their web addresses.
If these tests pass but you are still experiencing difficulty, see “InfiniBand System Interconnect
Troubleshooting” (page 255).
21.5 Improved Availability Issues
This section contains notes that apply when improved availability of services has been configured.
The HP XC System Software Installation Guide describes how to configure services for improved
availability.
21.5.1 How To Start HP Serviceguard When Only the Head Node is Running
Serviceguard does not automatically start up the Serviceguard cluster when only one node is up
and running and the quorum server or lock LUN is not accessible. Serviceguard was designed
that way to prevent a split brain scenario. A split brain scenario could occur if two nodes of a
Serviceguard cluster cannot communicate with each other and each determine that the other
node is down. If both nodes are allowed to start up their own one-node cluster, both nodes could
attempt to start up packages and utilize the same resources. This could lead to a variety of
problems including data loss.
Run the following command if you want to start up Serviceguard when only the head node is
up and running. If you did not install Serviceguard in its default location, you must specify the
full path to the command.
# cmruncl -n {nodename}
You are prompted to verify that starting Serviceguard on this node is correct. At some later time,
when the other configured node of the Serviceguard cluster is booted, it joins the running cluster.
All packages are running on the head node. You must manually relocate any packages that are
required to be running on the other node of the Serviceguard cluster.
21.5.2 Restart Serviceguard Quorum Server if Quorum Server Node is Re-imaged
You must restart the Serviceguard quorum server if the quorum server node is re-imaged while
improved availability is running. Issue the following command on the quorum server node to
restart the quorum server and update the /etc/inittab file:
# /opt/hptc/availability/serviceguard/startquorum
21.5.3 Known Limitation if Nagios is Configured for Improved Availability
When Nagios is configured for improved availability, by default, the head node acts as the Nagios
master and the other node in the availability set acts as a Nagios monitor.
The known limitation is that you cannot use the /sbin/service command to restart the Nagios
monitor on the non-head node in the availability set because of new functionality provided by
the /sbin/service script.
Issue the following command to restart the Nagios monitor service on the non-headnode of the
availability set:
# /etc/init.d/nagios restart
260 Troubleshooting