Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Managing the Cluster and Nodes
Chapter 7338
Using Serviceguard Commands to Add Previously Configured
Nodes to a Running Cluster
Use the cmrunnode command to join one or more nodes to an already
running cluster. Any node you add must already be a part of the cluster
configuration. The following example adds node ftsys8 to the cluster
that was just started with only nodes ftsys9 and ftsys10. The -v
(verbose) option prints out all the messages:
cmrunnode -v ftsys8
By default, cmrunnode will do network validation, making sure the
actual network setup matches the configured network setup. This is the
recommended method. If you have recently checked the network and find
the check takes a very long time, you can use the -w none option to
bypass the validation.
Since the node's cluster is already running, the node joins the cluster.
Packages may be started. If the node does not find its cluster running, or
the node is not part of the cluster configuration, the command fails.
Removing Nodes from Participation in a Running
Cluster
You can use Serviceguard Manager, or Serviceguard commands as shown
below, to remove nodes from active participation in a cluster. This
operation halts the cluster daemon, but it does not modify the cluster
configuration. To remove a node from the cluster configuration
permanently, you must recreate the cluster configuration file. See the
next section.
Halting a node is a convenient way of bringing it down for system
maintenance while keeping its packages available on other nodes. After
maintenance, the package can be returned to its primary node. See
“Moving a Failover Package” on page 343.
To return a node to the cluster, use cmrunnode.