Managing HP Serviceguard A.11.20.20 for Linux, May 2013

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 43) 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 251).
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.7 Configuring a Legacy Package
IMPORTANT: You can still create a new legacy package. If you are using a Serviceguard Toolkit
such as Serviceguard NFS Toolkit, consult the documentation for that product.
Otherwise, use this section to maintain and re-work existing legacy packages rather than to create
new ones. The method described in Chapter 6: “Configuring Packages and Their Services ”
(page 169), is simpler and more efficient for creating new packages, allowing packages to be built
from smaller modules, and eliminating the separate package control script and the need to distribute
it manually.
If you decide to convert a legacy package to a modular package, see “Migrating a Legacy Package
to a Modular Package” (page 240).
Creating or modifying a legacy package requires the following broad steps:
1. Generate the package configuration file
2. Edit the package configuration file
3. Generate the package control script
4. Edit the package control script
5. Distribute the control script to the cluster nodes
6. Apply the package configuration file
Each of these tasks is described in the sub-sections that follow.
7.7.1 Creating the Legacy Package Configuration
The package configuration process defines a set of application services that are run by the package
manager when a package starts up on a node in the cluster. The configuration also includes a
7.7 Configuring a Legacy Package 233