Managing Serviceguard Eighteenth Edition, September 2010
1. Use the following command to store a current copy of the existing cluster
configuration in a temporary file:
cmgetconf -c cluster1 temp.ascii
2. Specify a new set of nodes to be configured and generate a template of the new
configuration. Specify the node name (39 bytes or less) without its full domain
name; for example, ftsys8 rather than ftsys8.cup.hp.com. Enter a command
such as the following (all on one line):
cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9
-n ftsys10
3. Open clconfig.ascii in an editor and check that the information about the
new node is what you want.
4. Verify the new configuration:
cmcheckconf -C clconfig.ascii
5. Apply the changes to the configuration and distribute the new binary configuration
file to all cluster nodes:
cmapplyconf -C clconfig.ascii
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, 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” (page 343).
• 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.
366 Cluster and Package Maintenance