HP Serviceguard Metrocluster manual Eva

This script assumes the package directories already exist on all the nodes.

Using ftp might be preferable at your organization, because it does not require the use of a

.rhosts file for root. Root access via .rhosts might create a security issue.

8.Verify that every node in the Serviceguard cluster has the following files in the directory /etc/cmcluster/pkgname:

pkgname.cntl Metrocluster/Continuous Access package control script pkgname_xpca.env Metrocluster/Continuous Access environment file pkgname.ascii Serviceguard package ASCII configuration file pkgname.sh Package monitor shell script, if applicable

other files Any other scripts you use to manage Serviceguard packages.

9.Check the configuration using the cmcheckconf -P <pkgname>.config command, then apply the Serviceguard package configuration using the cmapplyconf -P <pkgname>.config ommand or SAM.

Configuring primary and recovery packages as legacy packages when using Continuous Access

EVA

To configure Primary or Recovery Package on the Source Disk Site or Target Disk Site in legacy style:

1.Create a directory /etc/cmcluster/<pkgname> for the package.

#mkdir /etc/cmcluster/<pkgname>

2.Create a package configuration file.

#cd /etc/cmcluster/<pkgname>

#cmmakepkg -p <pkgname>.ascii

Customize the package configuration file as appropriate to your application. Be sure to include the pathname of the control script (/etc/cmcluster/<pkgname>/<pkgname>.cntl) for the RUN_SCRIPT and HALT_SCRIPT parameters.

Set the AUTO_RUN flag to NO. This is to ensure the package will not start when the cluster starts. Only after primary packages start, use cmmodpkg to enable package switching on all primary packages. Enabling package switching in the package configuration must automatically start the primary package when the cluster starts. However, if there is a source disk site disaster, resulting in the recovery package starting and running on the target disk site, the primary package must not be started until after first stopping the recovery package.

Do not use cmmodpkg to enable package switching on any recovery package. Package switching on a recovery package automatically set by the cmrecovercl command on the target disk site when it successfully starts the recovery package.

3.Create a package control script.

# cmmakepkg -s pkgname.cntl

Customize the control script as appropriate to your application using the guidelines in the Managing Serviceguard user’s guide. Standard Serviceguard package customizations include modifying the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD, and SERVICE_RESTART parameters. Set LV_UMOUNT_COUNT to 1 or greater.

NOTE: Some of the control script variables, such as VG and LV, on the target disk site must be the same as on the source disk site. Some of the control script variables, such as, FS, SERVICE_NAME, SERVICE_CMD and SERVICE_RESTART are probably the same as on the source disk site. Some of the control script variables, such as IP and SUBNET, on the target disk site are probably different from those on the source disk site. Ensure that you review all the variables accordingly.

4.Add customer-defined run and halt commands in the appropriate places according to the needs of the application. Refer to the latest version of the Managing Serviceguard manual

Configuring legacy packages 107