Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Cluster and Package Maintenance
Managing the Cluster and Nodes
Chapter 7292
Managing the Cluster and Nodes
Managing the cluster involves the following tasks:
• Starting the Cluster When All Nodes are Down
• Adding Previously Configured Nodes to a Running Cluster
• Removing Nodes from Operation in a Running Cluster
• Halting the Entire Cluster
In Serviceguard 11.16 and later, these Package Admin and Cluster
Admin commands can be done by non-root users, according to access
policies in the cluster’s configuration files. See Editing Security Files, in
Chapter 5, for more information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to
start or stop the cluster, or to add or halt nodes. Starting the cluster
means running the cluster daemon on one or more of the nodes in a
cluster. You use different Serviceguard commands to start the cluster
depending on whether all nodes are currently down (that is, no cluster
daemons are running), or whether you are starting the cluster daemon
on an individual node.
Note the distinction that is made in this chapter between adding an
already configured node to the cluster and adding a new node to the
cluster configuration. An already configured node is one that is already
entered in the cluster configuration file; a new node is added to the
cluster by modifying the cluster configuration file.
NOTE Manually starting or halting the cluster or individual nodes does not
require access to the quorum server, if one is configured. The quorum
server is only used when tie-breaking is needed following a cluster
partition.
Starting the Cluster When all Nodes are Down
You can use Serviceguard Manager or Serviceguard commands to start
the cluster.