Managing HP Serviceguard A.11.20.00 for Linux, June 2012

1. Create a subdirectory for each package you are configuring in the $SGCONF directory:
mkdir $SGCONF/pkg1
You can use any directory names you like. (See “Understanding the Location of Serviceguard
Files” (page 121) for the name of Serviceguard directories on your version of Linux.)
2. Generate a package configuration file for each package, for example:
cmmakepkg -p $SGCONF/pkg1/pkg1.conf
You can use any file name you like for the configuration file.
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 in step 2 of “Using Serviceguard Commands to Configure a Package
” (page 210). 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” (page 154) and “package_type” (page 159).
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” (page 158) for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the failover_policy (page 162).
• FAILBACK_POLICY. For failover packages, enter the failback_policy (page 162).
• NODE_NAME. Enter the node or nodes on which the package can run; as described under
node_name (page 159).
• AUTO_RUN. Configure the package to start up automatically or manually; as described under
auto_run (page 160).
• NODE_FAIL_FAST_ENABLED. Enter the policy as described under
node_fail_fast_enabled (page 160).
Configuring a Legacy Package 211