Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 327
Using Serviceguard Commands to Change MAX_CONFIGURED_
PACKAGES
As of Serviceguard A.11.17, you can change MAX_CONFIGURED_PACKAGES
while the cluster is running. The default is the maximum number
allowed in the cluster.
Use the cmgetconf command to obtain a current copy of the cluster's
existing configuration. Example:
# cmgetconf -c cluster_name clconfig.ascii
Edit the clconfig.ascii file to include the desired value for
MAX_CONFIGURED_PACKAGES. Then use the cmcheckconf command to
verify the new configuration. Using -k or -K option with the
cmcheckconf command, can significantly reduce the response time.
Use the cmapplyconf command to apply the changes to the configuration
and send the new configuration file to all cluster nodes. Using -k or -K
option with the cmcheckconf command can significantly reduce the
response time.
Reconfiguring a Running Cluster
You can add new nodes to the cluster configuration or delete nodes from
the cluster configuration while the cluster is up and running. Note the
following, however:
• You cannot change the quorum server or lock disk configuration
while the cluster is running.
• You cannot remove an active node from the cluster. You must halt the
node first.
• You cannot delete an active volume group from the cluster
configuration. You must halt any package that uses the volume
group and ensure that the volume is inactive before deleting it.
• You cannot change cluster timing parameters.
• The only configuration change allowed while a node is unreachable
(for example, completely disconnected from the network) is to delete
the unreachable node from the cluster configuration. If there are also
packages that depend upon that node, the package configuration
must also be modified to delete the node. This all must be done in one
configuration request (cmapplyconf command).