Managing Serviceguard Nineteenth Edition, Reprinted June 2011
6. Runolrad -d to remove the NIC.
See also “Replacing LAN or Fibre Channel Cards” (page 314).
Changing the LVM Configuration while the Cluster is Running
You can do this in Serviceguard Manager, or use HP-UX commands as in the example that follows.
NOTE: If you are removing a volume group from the cluster configuration, make sure that you
also modify any package that activates and deactivates this volume group. In addition, you should
use the LVM vgexport command on the removed volume group; do this on each node that will
no longer be using the volume group.
From the LVM’s cluster, follow these steps:
1. Use the cmgetconf command to store a copy of the cluster's existing cluster configuration
in a temporary file. For example: cmgetconf clconfig.ascii
2. Edit the file clconfig.ascii to add or delete volume groups.
3. Use the cmcheckconf command to verify the new configuration.
4. Use the cmapplyconf command to apply the changes to the configuration and distribute
the new binary configuration file to all cluster nodes.
NOTE: If the volume group that you are deleting from the cluster is currently activated by a
package, the configuration will be changed but the deletion will not take effect until the package
is halted; thereafter, the package will no longer be able to run without further modification, such
as removing the volume group from the package configuration file or control script.
Changing the VxVM or CVM Storage Configuration
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.hp.com/go/hpux-serviceguard-docs.
You can add VxVM and CVM disk groups to the cluster configuration while the cluster is running.
The cluster must be running before you can add new CVM disk groups; for instructions, see “Adding
Disk Groups to the Package Configuration ” (page 210).
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:
288 Cluster and Package Maintenance