Building Disaster Recovery Serviceguard Solutions Using Continentalclusters A.08.00

Configuring the Site Controller Package in the primary cluster
The procedure on a node in the primary cluster to configure the Site Controller Package as follows:
1. Create a Site Controller Package configuration file using the dts/sc and array-specific
module.
For example, when using Continuous Access P9000 and XP, the command is:
# cmmakepkg -m dts/sc –m dts/ccxpca cw_sc.config
When using Continuous Access EVA, the command is:
# cmmakepkg -m dts/sc –m dts/cccaeva cw_sc.config
When using EMC SRDF, the command is:
# cmmakepkg -m dts/sc –m dts/ccsrdf cw_sc.config
When using 3PAR Remote Copy, the command is:
# cmmakepkg -m dts/sc –m dts/cc3parrc cw_sc.config
2. Edit the cw_sc.config file by specifying the following:
• Name for the package_name attribute.
package_name <site_controller_package_name>
• Names of the nodes explicitly using the node_name attribute.
• The Site Controller Package directory for the dts/dts/dts_pkg_dir attribute.
dts/dts/dts_pkg_dir /etc/cmcluster/<site_controller_package_name>
This is the package directory for this Site Controller Package. The Metrocluster environment
file is automatically generated for this package in this directory.
• Specify a name for the log file.
script_log_file <log_file_name>
• Specify the site without any packages.
Do not specify any packages using the critical_package or managed_package
attributes.
site <site name>
• Edit the array specific parameters. For configuring these parameters, see the following
sections based on the type of the array used in your environment.
3. Apply the Site Controller Package configuration file in the cluster.
# cmapplyconf -P cw_sc.config
IMPORTANT: Ensure packages are not configured with the critical_package or
managed_package attributes in the Site Controller Package configuration file. These attributes
must be configured only after configuring the Site Safety Latch dependencies. For information about
configuring these dependencies, see “Configuring the Site Safety Latch dependencies in the primary
cluster” (page 49).
Configuring the Site Safety Latch dependencies in the primary cluster
After the Site Controller Package configuration is applied, the corresponding Site Safety Latch is
automatically configured in the cluster. This section describes the procedure to configure Site Safety
Latch dependencies.
The procedure to configure the Site Safety Latch dependencies:
Configuring the Site Controller Package in the primary cluster 49