HP Serviceguard Metrocluster Deleting the Site Controller Package, Starting a Complex Workload

3.Halt the Site Controller package.

#cmhaltpkg <site_controller_package_name>

4.Log in to the other node in the local cluster, and start the Site Controller package.

#cmrunpkg <site_controller_package_name>

Deleting the Site Controller Package

To remove a site controller package from the Continentalclusters configuration, you must first remove the associated recovery group from the Continentalclusters configuration file.

Removing the site controller package does not require you to bring down either cluster. However, in order to implement the new configuration, the following steps are required:

1.Edit the Continentalclusters configuration file, deleting the recovery group for the site controller package.

2.Halt the monitor packages that are running on the clusters.

3.Use the cmapplyconcl command to apply the new Continentalclusters configuration.

4.Restart the monitor packages on both clusters.

5.Halt the Site Controller Package.

6.Remove all the Site Safety Latch dependencies configured for the packages managed by the Site Controller Package.

Also remove the Site Controller EMS resource dependency from packages managed by the Site Controller Packages on both clusters.

For example, if you have CVM or CFS configured in your environment, run the following commands from a node on both clusters.

#cfsdgadm delete_ems pkg1dg /dts/mcsc/cw_sc

7.Delete Site Controller package.

Use the Serviceguard cmdeleteconf command in both the clusters to delete the Site Controller package configuration on all the nodes.

8.View the status of the Continentalclusters.

#cmviewconcl

Starting a Complex Workload

The complex workload in SADTA can be started in a Continentalclusters by starting the Site Controller package.

The procedure to start the complex workload as follows:

1.Ensure that the Site Controller package is enabled on all the nodes in the cluster where the complex workload must be started.

#cmmodpkg –e –n <Primary_Cluster node 1> –n <Primary_Cluster node 2> <site_controller_package_name>

2.Start the Site Controller package by enabling it.

#cmmodpkg –e <site_controller_package_name>

The Site Controller Package starts on the preferred node in the cluster. At startup, the Site Controller package starts the corresponding complex-workload packages that are configured in that cluster. After the complex-workload packages are up, verify the package log files for any errors that will have occurred at startup.

Administering Continentalclusters using SADTA configuration 69