Security Solutions

<path_to_env_file> <modular_sg_ecm_cc.conf>
4. Halt the package.
# cmhaltpkg <package_name>
5. Validate the new modular package configuration file.
# cmcheckconf -P <modular_sg_ecm_cc.conf>
6. Apply the package configuration with the modular configuration file created in step 3.
# cmapplyconf -P <modular_sg_ecm_cc.conf>
7. Run the package on a node in the Serviceguard cluster.
# cmrunpkg -n <node_name> <package_name>
8. Enable global switching for the package.
# cmmodpkg -e <package_name>
Migrating legacy style primary and recovery packages to modular packages using Continuous
access EVA
Legacy packages 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.
To migrate Continuous Access EVA legacy packages to modular packages using Continentalclusters
A.08.00:
1. Create a modular package configuration file for the Continentalclusters legacy package.
# cmmigratepkg -p <package_name> [-s] -o <modular_sg_conf>
IMPORTANT: This command generates a package configuration file. Do not apply this
configuration file until you complete the migration procedure. For more information on the
cmmigratepkg command, see the Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard.
2. If the Continentalclusters legacy package uses ECM Toolkit, then generate a new modular
package configuration file using the package configuration file generated in the step 1.
For Example, if the legacy package uses the ECM Oracle toolkit, generate a new modular
package configuration file with the following command:
# cmmakepkg –i modular_sg.conf -m ecmt/oracle/oracle –t\
haoracle.conf modular_sg_ecm.conf
3. Create a modular package configuration file using the package configuration file created in
step 1.
When using HP Serviceguard A.11.18, complete the following steps to include
Continentalclusters modules in the new modular package configuration file:
a. Include the Continentalclusters module in the new configuration file.
# cmmakepkg –i <modular_sg_ecm.conf> -m dts/cccaeva\
<modular_sg_ecm_cc.conf>
b. Copy the environment variable values from the Metrocluster environment file present in
the package directory, to the variables present in the newly created modular package
configuration file.
When using HP Serviceguard A.11.19 or later versions, run the following command to include
the Continentalclusters modules in the new modular package configuration file:
# cmmakepkg –i <modular_sg_ecm.conf> -m dts/cccaeva -t\
<path_to_env_file> <modular_sg_ecm_cc.conf>
102 Legacy packages