Managing Serviceguard Sixteenth Edition, March 2009

NOTE: Check the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility
and Feature Matrix and the latest Release Notes for your version of Serviceguard for
up-to-date information about support for CVM and CFS: http://www.docs.hp.com
-> High Availability -> Serviceguard.
Create CVM disk groups from the CVM Master Node:
• For CVM 3.5, and for CVM 4.1 and later without CFS, edit the configuration file of
the package that uses CVM storage. Add the CVM storage group by means of the
cvm_dg parameter (or STORAGE_GROUP in a legacy package). Then run the
cmapplyconf command.
• For CVM 4.1 and later with CFS, edit the configuration file of the package that uses
CFS. Configure the three dependency_ parameters. Then run the cmapplyconf
command.
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. If you are removing a disk group
managed by CVM without CFS, be sure to remove the corresponding entries for the
disk group from the package configuration file. If you are removing a disk group
managed by CVM with CFS, be sure to remove 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
Reconfiguring a Cluster 337