Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7342
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 (Serviceguard version A.11.16 or later), or by
issuing 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
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.
Using Serviceguard Manager to Change MAX_CONFIGURED_
PACKAGES
Select the cluster on the map or tree. From the Actions menu, select
Configuration. MAX_CONFIGURED _PACKAGES is in the Parameters tab.
Failover Optimization to enable
or disable Faster Failover
product
Cluster must not be running.
Table 7-1 Types of Changes to Permanent Cluster Configuration
Change to the Cluster
Configuration Required Cluster State