Managing HP Serviceguard A.12.00.00 for Linux, June 2014

5. Apply the changes to the configuration and distribute the new binary configuration file to all
cluster nodes:
cmapplyconf -C clconfig.conf
7.6.5 Updating the Cluster Lock LUN Configuration Online
Proceed as follows.
IMPORTANT: See “What Happens when You Change the Quorum Configuration Online”
(page 41) for important information.
1. In the cluster configuration file, modify the value of CLUSTER_LOCK_LUN for each node.
2. Run cmcheckconf to check the configuration.
3. Run cmapplyconf to apply the configuration.
If you need to replace the physical device, see “Replacing a Lock LUN” (page 271).
7.6.6 Changing MAX_CONFIGURED_PACKAGES
As of Serviceguard A.11.18, 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 the cmgetconf command to obtain a current copy of the cluster's existing configuration, for
example:
cmgetconf -C <cluster_name> clconfig.conf
Edit the clconfig.conf 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 the cmapplyconf command 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.
7.6.7 Changing the VxVM Storage Configuration
You can add VxVM disk groups to the cluster configuration while the cluster is running. Similarly,
you can delete VxVM disk groups provided they are not being used by a cluster node at that time.
NOTE: If you are removing a disk group from the cluster configuration, ensure that you also
modify or delete any package configuration file that imports and deports this disk group. Be sure
to remove the disk group from the configuration of any package that used it, and the corresponding
dependency_ parameters.
7.7 Reconfiguring a Package
You reconfigure a package in much the same way as you originally configured it; for modular
packages, see Chapter 6: “Configuring Packages and Their Services ” (page 179).
The cluster can be either halted or running during package reconfiguration, and in some cases
the package itself can be running; the types of change you can make and the times when they
take effect depend on whether the package is running or not.
If you reconfigure a package while it is running, it is possible that the package could fail later,
even if the cmapplyconf succeeded.
For example, consider a package with two volume groups. When this package started, it activated
both volume groups. While the package is running, you could change its configuration to list only
one of the volume groups, and cmapplyconf would succeed. If you issue cmhaltpkg command,
however, the halt would fail. The modified package would not deactivate both of the volume groups
244 Cluster and Package Maintenance