Managing Serviceguard Eighteenth Edition, September 2010

Similarly, you can delete VxVM or CVM disk groups provided they are not being used
by a cluster node at the time.
CAUTION: Serviceguard manages the Veritas processes, specifically gab and LLT.
This means that you should never use administration commands such as gabconfig,
llthosts, and lltconfig to administer a cluster. It is safe to use the read-only
variants of these commands, such as gabconfig -a. But a Veritas administrative
command could potentially crash nodes or the entire cluster.
NOTE: If you are removing a disk group from the cluster configuration, make sure
that you also modify or delete any package configuration file (or legacy package control
script) that imports and deports this disk group. Be sure to remove the disk group from
the configuration of any package that used it, as well as the corresponding dependency_
parameters.
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 is the maximum
number allowed in the cluster. You can use Serviceguard Manager to change
MAX_CONFIGURED_PACKAGES, or Serviceguard commands as shown below.
Use cmgetconf to obtain a current copy of the cluster's existing configuration; for
example:
cmgetconf -c <cluster_name> clconfig.ascii
Edit the clconfig.ascii file to include the new value for
MAX_CONFIGURED_PACKAGES. Then use the cmcheckconf command to verify
the new configuration. Using the -k or -K option can significantly reduce the response
time.
Use cmapplyconf to apply the changes to the configuration and send the new
configuration file to all cluster nodes. Using -k or -K can significantly reduce the
response time.
374 Cluster and Package Maintenance