Setting up the Continentalclusters Configuration

The steps below are the basic procedure for setting up the Continentalclusters configuration file and the monitoring packages on the two clusters. For complete details on creating and editing the configuration file, refer to Chapter 2: “Designing Continentalclusters”.

1.Generate the Continentalclusters configuration using the following command:

#cmqueryconcl -C cmconcl.config

2.Edit the configuration file cmconcl.config with the names of the two clusters, the nodes in each cluster, the recovery groups and the monitoring definitions. The recovery groups define the primary and recovery packages. When data replication is done using Continuous Access EVA, there are no data sender and receiver packages.

Define the monitoring parameters, the notification mechanism (ITO, email, console, SNMP, syslog or tcp) and notification type (alert or alarm) based on the cluster status (unknown, down, up or error). Descriptions for these can be found in the configuration file generated in the previous step.

3.Edit the Continentalclusters security file /etc/opt/cmom/cmomhosts to allow or deny hosts read access by the monitor software.

4.On all nodes in both clusters copy the monitor package files from /opt/cmconcl/scripts to/etc/cmcluster/ccmonpkg. Edit the monitor package configuration as needed in the file /etc/cmcluster/ccmonpkg/ccmonpkg.config. Set the AUTO_RUN flag to YES.

This is in contrast to the flag setting for the application packages. The monitor package should start automatically when the cluster is formed.

5.Apply the monitor package to both cluster configurations.

#cmapplyconf -P /etc/cmcluster/ccmonpkg/ccmonpkg.config

6.Apply the Continentalclusters configuration file using cmapplyconcl. Files are placed in

/etc/cmconcl/instances. There is no change to /etc/cmcluster/cmclconfig nor is there an equivalent file for Continentalclusters. Example:

#cmapplyconcl -C cmconcl.config

7.Start the monitor package on both clusters.

NOTE: The monitor package for a cluster checks the status of the other cluster and issues alerts and alarms, as defined in the Continentalclusters configuration file, based on the other cluster’s status.

8.Check /var/adm/syslog/syslog.log for messages. Also check the ccmonpkg package log file.

9.Start the primary packages on the source disk site using cmrunpkg. Test local failover within the source disk site.

10.View the status of the Continentalclusters primary and target disk sites, including configured event data.

#cmviewconcl -v

The Continentalclusters is now ready for testing. See “Testing the Continentalclusters” (page 92).

Completing and Running Continentalclusters Solution with Continuous Access EVA 251