Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7 277
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
in step 2 of “Using Serviceguard Commands to Configure a Package” on
page 276. Use the bullet points that follow as a checklist.
• PACKAGE_TYPE. Enter the package type; see “Types of Package:
Failover, Multi-Node, System Multi-Node” on page 201 and
package_type on page 210.
NOTE For modular packages, the default form for parameter names and
literal values 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
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” on
page 209 for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the
failover_policy (see page 214).