Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Managing the Running Cluster
Chapter 5262
• cmviewcl checks 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.
• cfscluster status gives information about a cluster configured
with CFS, the VERITAS Cluster File System; cfsdgadm display
gives information about the cluster’s disk groups.
• cmrunnode is used to start Serviceguard on 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 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 online, start it. From the Serviceguard
Manager menu, choose Run Cluster. From the command line, use
cmruncl -v.
By default, cmruncl will check the networks. Serviceguard will probe
the actual network configuration with the network information in
the cluster configuration. If you do not need this validation, use
cmruncl -v - w none instead, to turn off validation and save time
2. When the cluster has started, make sure that cluster components are
operating correctly. In Serviceguard Manager, open the cluster on
the map or tree, and perhaps check its Properties. On the command
line, use the cmviewcl -v command.
Make sure that all nodes and networks are functioning as expected.
For more information, refer to Chapter 7, “Cluster and Package
Maintenance,” on page 309.
3. Verify that nodes leave and enter the cluster as expected using the
following steps: