Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7326
•If you are replacing, rather than removing, the interface, you do not
need to bring down the cluster, and you may be able to do the
replacement online; see “Replacing LAN or Fibre Channel Cards” on
page 354.
Reconfiguring a Halted Cluster
You can make a permanent change in cluster configuration when the
cluster is halted. This procedure must be used for changes to the quorum
server or lock disk configuration, changes in timing parameters, and
changes to the Maximum Number of Packages parameter, but it can be
used for any other cluster configuration changes as well.
Use the following steps:
1. Halt the cluster on all nodes, using Serviceguard Manager’s Halt
Cluster command, or cmhaltcl on the command line.
2. On one node, reconfigure the cluster as described in the chapter
“Building an HA Cluster Configuration.” You can do this by using
Serviceguard Manager, or by entering cmquerycl on the command
line to generate an ASCII file, which you then edit.
3. Make sure that all nodes listed in the cluster configuration file are
powered up and accessible. To copy the binary cluster configuration
file to all nodes, use Serviceguard Manager’s Apply button, or enter
cmapplyconf on the command line. This file overwrites any previous
version of the binary cluster configuration file.
4. Start the cluster on all nodes or on a subset of nodes. Use
Serviceguard Manager’s Run Cluster command, or cmruncl on the
command line.
Changing MAX_CONFIGURED_ PACKAGES
As of Serviceguard A.11.17, you can change MAX_CONFIGURED_PACKAGES
while the cluster is running. The default for MAX_CONFIGURED_PACKAGES
as of A.11.17 is the maximum number allowed in the cluster. You can use
Serviceguard Manager to change MAX_CONFIGURED_PACKAGES, or use
Serviceguard commands as shown below.