HP Serviceguard manual Verifying and Applying the Package Configuration

•To coordinate the startup and shutdown of database software with cluster node startup and shutdown, you can use the database template files provided with the separately purchasable Enterprise Cluster Master Toolkit product.

These files are in /opt/cmcluster/toolkit/DB/. Separate toolkits are available for Oracle, Informix, and Sybase.

In addition to the standard package script, you use the special script that is provided for the database. To set up these scripts, follow the instructions in the README file provided with each toolkit.

•Configure the Access Control Policy for up to eight specific users or any_user.

The only user role you can configure in the package configuration file is package_admin for the package in question. Cluster-wide roles are defined in the cluster configuration file. See “Setting up Access-Control Policies” (page 194) for more information.

Verifying and Applying the Package Configuration

Serviceguard checks the configuration you enter and reports any errors.

Use a command such as the following to verify the content of the package configuration file you have created, for example:

cmcheckconf -v -P $SGCONF/pkg1/pkg1.conf

Errors are displayed on the standard output. If necessary, re-edit the file to correct any errors, then run cmcheckconf again until it completes without errors.

The following items are checked:

•The package name is valid, and at least one node_name entry is included.

•There are no duplicate parameter entries (except as permitted for multiple volume groups, etc.)

•Values for all parameters are within permitted ranges.

•Configured resources are available on cluster nodes.

•File systems and volume groups are valid (for a modular package, cmcheckconf checks that volume groups are already configured into the cluster).

•Services are executable.

•Any package that this package depends on is already part of the cluster configuration.

For more information, see the manpage for cmcheckconf (1m) and “Checking Cluster Components” (page 274).

When cmcheckconf has completed without errors, apply the package configuration, for example:

cmapplyconf -P $SGCONF/pkg1/pkg1.conf

This adds the package configuration information to the binary cluster configuration file in the $SGCONF directory (normally /etc/cmcluster) and distributes it to all the cluster nodes.

Verifying and Applying the Package Configuration 259