Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/CA
Configuring Packages for Automatic Disaster Recovery
Chapter 3110
If any messages are returned, you should correct the syntax errors.
9. Check the configuration using the cmcheckconf -P
pkgname.config, then apply the MC/ServiceGuard configuration
using the cmapplyconf -P pkgname.config command or SAM.
10. Distribute MetroCluster/CA configuration, environment and control
script files to other nodes in the cluster by using ftp or rcp:
# rcp -p /etc/cmcluster/pkgname/* \
other_node:/etc/cmcluster/pkgname
See the example script Samples/ftpit to see how to semi-automate
the copy using ftp. This script assumes the package directories
already exist on all nodes.
Using ftp may be preferable at your organization, since it does not
require the use of a.rhosts file for root. Root access via .rhosts may
create a security issue.
11. Verify that each node in the MC/ServiceGuard cluster has the
following files in the directory /etc/cmcluster/pkgname:
pkgname.cntl SeviceGuard package control script
pkgname_xpca.env MetroCluster/CA environment file
pkgname.config ServiceGuard package ASCII configuration file
pkgname.sh Package monitor shell script, if applicable
other files Any other scripts you use to manage
MC/ServiceGuard packages
The MC/ServiceGuard cluster is ready to automatically switch packages
to nodes in remote data centers using MetroCluster/CA.