Managing Serviceguard Eighteenth Edition, September 2010

3. Edit each configuration file to specify package name, prioritized list of nodes (with
39 bytes or less in the name), the location of the control script, and failover
parameters for each package. Include the data you recorded on the Package
Configuration Worksheet.
Configuring a Package in Stages
It is a good idea to configure failover packages in stages, as follows:
1. Configure volume groups and mount points only.
2. Distribute the control script to all nodes.
3. Apply the configuration.
4. Run the package and ensure that it can be moved from node to node.
5. Halt the package.
6. Configure package IP addresses and application services in the control script.
7. Distribute the control script to all nodes.
8. Run the package and ensure that applications run as expected and that the package
fails over correctly when services are disrupted.
Editing the Package Configuration File
Edit the file you generated with cmmakepkg. Use the bullet points that follow as a
checklist.
NOTE: HP strongly recommends that you never edit the package configuration file
of a CVM/CFS multi-node or system multi-node package, although Serviceguard does
not prohibit it. Create SG-CFS-pkg by issuing the cmapplyconf command. Create
and modify SG-CFS-DG-id# and SG-CFS-MP-id# using cfs commands.
• PACKAGE_TYPE. Enter the package type; see “Types of Package: Failover,
Multi-Node, System Multi-Node” (page 280) and package_type (page 289).
NOTE: For modular packages, the default form for parameter names in the
package configuration file is lower case; for legacy packages the default is upper
case. There are no compatibility issues; Serviceguard is case-insensitive as far as
the parameter names are concerned.
Because this section is intended to be used primarily when you are reconfiguring
an existing legacy package, we are using the legacy parameter names (in upper
case) for sake of continuity. But if you generate the configuration file using
cmmakepkg or cmgetconf, you will see the parameter names as they appear in
modular packages; see the notes below and the “Package Parameter Explanations”
(page 287) for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the failover_policy (page 292).
376 Cluster and Package Maintenance