Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

package configuration file automatically based on the type of disks used by the supported toolkit
application.
If the disks used are HP StorageWorks Continuous Access P9500 or XP disks and are replicated,
then the dts/mcxpca module is automatically inserted into the package configuration file.
The following dts/mcxpca parameters are auto-discovered.
• DEVICE_GROUP
• FENCE
• HORCMISNT
• dts/dts/dts_pkg_dir is automatically set to /etc/cmcluster/<package_name>
The default values are used for rest of the dts/mcxpca module attributes.
The following prerequisites and limitations apply in package easy deployment for Metrocluster
with Continuous Access for P9000 and XP:
Prerequisite
The device group pair must have been already created.
Limitations
1. A device group configuration with a HORCMPERM file is not supported.
2. All physical devices must belong to exactly one DEVICE GROUP.
3. The Device Group Monitor is not configured as a part of Easy Deployment.
4. Three data center configurations is not supported.
5. If enclosure based naming scheme is used by Veritas Volume manager, package easy
deployment of Metrocluster packages is not supported.
Adding a Node to a Metrocluster
To add a node to Metrocluster with Continuous Access for P9000 and XP, use the following
procedure:
1. Add the node in a cluster by editing the Serviceguard cluster configuration file and applying
the configuration:
# cmapplyconf -C cluster.config
2. Create the RAID Manager configuration on the newly added node. For more information, see
“Creating the RAID Manager Configuration” (page 164)
3. Update the HORCM_INST section in the RAID Manager instance file on nodes in the other
site with the information about the RAID Manager instance on the newly added node. Restart
the RAID Manager instance on nodes in the other site so that the new information in the
configuration file is read.
4. If you are using Metrocluster legacy packages, follow the steps mentioned below:
a. Create the Metrocluster package directory on the newly added node.
b. Copy the package control script and Metrocluster environment file from one of the existing
nodes to the same pathname on the newly added node:
# rcp <package_directory>/<package_control_Script>
<new_node_name>:<package_directory>
# rcp <package_directory>/<Metrocluster_environment_file>
<new_node_name>:<package_directory>
5. If you are using Metrocluster modular package and if node_name is set to “*” in Metrocluster
package configuration, follow the steps mentioned below:
a. Create the Metrocluster package directory on the newly added node.
b. Copy Metrocluster environment file from one of the existing nodes to the same pathname
on the newly added node:
Adding a Node to a Metrocluster 191