Managing HP Serviceguard A.12.00.00 for Linux, June 2014

# Warning: Neither a quorum server nor a lock lun was specificed.
# A Quorum Server or a lock lun is required for clusters of only two nodes.
If you attempt to configure both a quorum server and a lock LUN, the following message appears
on standard output when issuing the cmcheckconf or cmapplyconf command:
Duplicate cluster lock, line 55. Quorum Server already specified.
5.2.11 Distributing the Binary Configuration File
After specifying all cluster parameters, use the cmapplyconf command to apply the configuration.
This action distributes the binary configuration file to all the nodes in the cluster. HP recommends
doing this separately before you configure packages (described in the next chapter). In this way,
you can verify the quorum server, heartbeat networks, and other cluster-level operations by using
the cmviewcl command on the running cluster. Before distributing the configuration, ensure that
your security files permit copying among the cluster nodes. See “Configuring Root-Level Access”
(page 144).
The following command distributes the binary configuration file:
cmapplyconf -v -C $SGCONF/clust1.conf
5.3 Managing the Running Cluster
This section describes some approaches to routine management of the cluster. For more information,
see Chapter 7: “Cluster and Package Maintenance” (page 211). You can manage the cluster from
Serviceguard Manager, or by means of Serviceguard commands as described below.
NOTE: You can use the cmdeploycl (1m) command to create and start the cluster automatically
after its creation. The cmdeploycl (1m) command internally calls the cmquerystg (1m)
command — to configure cluster Lock LUN, cmpreparecl (1m) — to perform all the prerequisites,
cmquerycl, cmapplyconf, and cmruncl. If you use cmdeploycl (1m) command, you
do not need to perform the procedures that follow, but it is good idea to read them so that you
understand what cmdeploycl (1m) command does for you.
5.3.1 Checking Cluster Operation with Serviceguard Commands
• cmviewcl checks the status of the cluster and many of its components. A non-root user with
the role of Monitor can run this command from a cluster node or see status information in
Serviceguard Manager.
• cmrunnode is used to start a node. A non-root user with the role of Full Admin, can run this
command from a cluster node or through Serviceguard Manager.
• cmhaltnode is used to manually stop a running node. (This command is also used by
shutdown(1m)). A non-root user with the role of Full Admin can run this command from a
cluster node or through Serviceguard Manager.
• cmruncl is used to manually start a stopped cluster. A non-root user with Full Admin access
can run this command from a cluster node, or through Serviceguard Manager.
• cmhaltcl is used to manually stop a cluster. A non-root user with Full Admin access, can
run this command from a cluster node or through Serviceguard Manager.
You can use these commands to test cluster operation, as in the following:
1. If the cluster is not already running, start it:
cmruncl -v
5.3 Managing the Running Cluster 175