User's Guide

f. DC1_HOST_LIST— This is a parameter used to define a list of clustered nodes that reside
in Data Center 1.
g. DC2_STORAGE_WORLD_WIDE_NAME— This is the World Wide Name of the EVA
storage system that resides in Data Center 2.
h. DC2_SMIS_LIST— This is a list of management servers that reside in Data Center 2.
i. DC2_HOST_LIST— This is a parameter used to define a list of clustered nodes that reside
in Data Center 2.
There are additional Metrocluster parameters available in the package configuration file. It
is recommended that the default values of these variables are retained unless there is a specific
business requirement to change them. For more information on the additional Metrocluster
parameters, see Appendix B (page 487).
For the failover_policy parameter, Metrocluster failover packages can be configured to
use any of the Serviceguard defined failover policies. The site_preferred and
site_preferred_manual failover policies are introduced in Serviceguard specifically for
Metrocluster configurations. The site_preferred value implies that when a Metrocluster
package has to fail over, it will necessarily failover to a node within the same site of the node
it last ran on. Only when there is no other configured node available within the same site, the
package fails over to a node at the other site. The site_preferred_manual failover policy
provides automatic failover of packages within a site and manual failover across sites. To use
either of these policies the underlying cluster must be configured with sites and each cluster
nodes should be associated to a site. For information on configuring the failover policy to
site_preferred or site_preferred_manual, see “Site Aware Failover Configuration”
(page 26).
3. Validate the package configuration file.
# cmcheckconf -P temp.config
4. Apply the package configuration file.
# cmapplyconf -P temp.config
NOTE: If external_pre_script is specified in a Metrocluster package configuration,
the external_pre_script will be executed after the execution of Metrocluster module
scripts in package startup. Metrocluster module scripts are always executed first during package
startup.
5. Run the package on a node in the Serviceguard cluster.
# cmrunpkg -n <node_name> <package_name>
6. Enable global switching for the package.
# cmmodpkg -e <package_name>
Once the package is created, if the value of any Metrocluster parameter needs to be changed,
then edit this package configuration file and re-apply it.
Migrating Legacy Packages to Modular Packages using Metrocluster with Continuous Access EVA
A.05.00 or Later
Metrocluster Legacy packages can be migrated to Modular packages using the procedure listed
in this section. However, the migration steps vary based on the HP Serviceguard version and the
Legacy package configuration. While completing the migration procedure, multiple package
configuration files created. Only the final package configuration file that is created at the end of
the procedure must be applied.
Complete the following procedure to migrate Legacy packages to Modular packages using
Metrocluster with Continuous Access EVA A.05.00 or later:
Building a Metrocluster Solution with Continuous Access EVA 239