1.Run the following command to create an XPCA modular package configuration file:

# cmmakepkg –m dts/ccxpca temp.config

2.Edit the following attributes in the temp.config file:

•dts/dts/dts_pkg_dir

This is the package directory for this modular package. The Metrocluster environment file is generated for this package in this directory. This value must be unique for all packages.

For example:

dts/dts/dts_pkg_dir=/etc/cmcluster/<package_name>

•DEVICE_GROUP

Specify the XPCA device group name managed by this package, as specified in the RAID Manager configuration file.

•HORCMINST

Specify the name of the RAID manager instance that manages the XPCA device group used by this package.

•FENCE

Specify the fence level configured for the XPCA device group that is managed by this package.

•AUTO_RUN

Set the value of this parameter to no.

There are additional 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 parameters, see Appendix A (page 475).

3.Halt the package.

#cmhaltpkg <package_name>

4.Validate the package configuration file.

#cmcheckconf -P temp.config

5.Apply the package configuration file.

#cmapplyconf -P temp.config

6.Run the package on a node in the Serviceguard cluster.

#cmrunpkg -n <node_name> <package_name>

7.Enable global switching for the package.

#cmmodpkg -e <package_name>

Once the package is created, if the value of any parameter needs to be changed, then edit this package configuration file and re-apply it.

Migrating legacy style primary and recovery packages to modular packages when using Continuous Access P9000 or XP

Primary and recovery packages configured as legacy packages in an existing Continentalclusters environment using Continuous Access P9000 or XP, can be migrated to modular packages using the procedure described 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 are created. Only the final package configuration file that is created at the end of the procedure must be applied.

68 Designing Continentalclusters