HP Serviceguard manual Configuring a Legacy Package, Creating the Legacy Package Configuration

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 -kor -Koption 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 -kor -Kcan significantly reduce the response time.

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 rework existing legacy packages rather than to create new ones. The method described in “Configuring Packages and Their Services ” (page 227), 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 311). Do not attempt to convert Serviceguard Toolkit packages.

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 subsections that follow.

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

302 Cluster and Package Maintenance