Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 343
In Serviceguard A.11.17, you can change MAX_CONFIGURED_PACKAGES
while the cluster is running. The default in A.11.17 is that
MAX_CONFIGURED_PACKAGES is the maximum number allowed in the
cluster.
Using Serviceguard Commands to Change MAX_CONFIGURED_
PACKAGES
In Serviceguard A.11.17, you can change MAX_CONFIGURED_PACKAGES
while the cluster is running. The default in A.11.17 is that
MAX_CONFIGURED_PACKAGES 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.