HP Serviceguard manual Verifying the Package Configuration, Distributing the Configuration

Verifying the Package Configuration

Serviceguard checks the configuration you create and reports any errors.

For legacy packages, you can do this in Serviceguard Manager: click Check to verify the package configuration you have done under any package configuration tab, or to check changes you have made to the control script. Click Apply to verify the package as a whole. See the local Help for more details.

If you are using the command line, use the following command to verify the content of the package configuration you have created:

cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1.conf

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

The following items are checked (whether you use Serviceguard Manager or cmcheckconf command):

•Package name is valid, and at least one NODE_NAME entry is included.

•There are no duplicate parameter entries.

•Values for parameters are within permitted ranges.

•Run and halt scripts exist on all nodes in the cluster and are executable.

•Run and halt script timeouts are less than 4294 seconds.

•Configured resources are available on cluster nodes.

•If a dependency is configured, the dependency package must already be configured in the cluster.

Distributing the Configuration

You can use Serviceguard Manager or HP-UX commands to distribute the binary cluster configuration file among the nodes of the cluster.

DSAU (Distributed Systems Administration Utilities) can help you streamline your distribution; see “What are the Distributed Systems Administration Utilities?” (page 25).

Distributing the Configuration And Control Script with Serviceguard Manager

When you have finished creating a legacy package in Serviceguard Manager, click Apply Configuration. If the package control script has no errors, it is converted to a binary file and distributed to the cluster nodes.

Copying Package Control Scripts with HP-UX commands

IMPORTANT: In a cross-subnet configuration, you cannot use the same package control script on all nodes if the package uses relocatable IP addresses. See “Configuring Cross-Subnet Failover” (page 309).

Use HP-UX commands to copy legacy package control scripts from the node where you created the files, to the same pathname on all nodes which can possibly run the package. Use your favorite method of file transfer (e. g., rcp or ftp). For example, from ftsys9, you can run the rcp command to copy the package control script to ftsys10 (all on one line):

rcp /etc/cmcluster/pkg1/control.sh ftsys10:/etc/cmcluster/pkg1/control.sh

308 Cluster and Package Maintenance