Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 365
Use cmrunnode to start the new node, and, if you so decide, set the
AUTOSTART_CMCLD parameter to 1 in the /etc/rc.config.d/cmcluster
file to enable the new node to join the cluster automatically each time it
reboots.
NOTE Before you can add a node to a running cluster that uses Veritas CVM
(on systems that support it), the node must already be connected to the
disk devices for all CVM disk groups. The disk groups will be available
for import when the node joins the cluster.
Removing Nodes from the Cluster while the Cluster Is Running
You can use Serviceguard Manager to delete nodes, or Serviceguard
commands as shown below. The following restrictions apply:
• The node must be halted. See “Removing Nodes from Participation in
a Running Cluster” on page 351.
• If the node you want to delete is unreachable (disconnected from the
LAN, for example), you can delete the node only if there are no
packages which specify the unreachable node. If there are packages
that depend on the unreachable node, halt the cluster or use
Serviceguard commands as described in the next section.
Use the following procedure to delete a node with HP-UX commands. In
this example, nodes ftsys8, ftsys9 and ftsys10 are already configured
in a running cluster named cluster1, and you are deleting node
ftsys10.
NOTE If you want to remove a node from the cluster, run the cmapplyconf
command from another node in the same cluster. If you try to issue the
command on the node you want removed, you will get an error message.
Step 1. Use the following command to store a current copy of the existing cluster
configuration in a temporary file:
cmgetconf -c cluster1 temp.ascii
Step 2. Specify the new set of nodes to be configured (omitting ftsys10) and
generate a template of the new configuration: