Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Managing the Cluster and Nodes
Chapter 7332
Adding Previously Configured Nodes to a Running
Cluster
You can use Serviceguard Manager or the Serviceguard command line to
bring a configured node up within a running cluster.
Using Serviceguard Manager to Add a Configured Node to the
Running Cluster
Select the node icon, then right-click to display the action menu. Select
“Run node
<hostname> .” The progress window shows messages as the
action takes place. This will also start any packages that are eligible to
run on the node. Click OK on the progress window when the operation is
complete.
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, cmruncl 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 Operation in a Running
Cluster
You can use Serviceguard Manager or HP-UX commands to stop nodes
from running 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.