Managing HP Serviceguard A.11.20.10 for Linux, December 2012

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.
7.7.1.2.2 Editing the Package Configuration File
Edit the file you generated in step 2 of “Using Serviceguard Commands to Configure a Package
” (page 225). 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 164) and “package_type” (page 169).
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 168) for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the failover_policy (page 172).
• FAILBACK_POLICY. For failover packages, enter the failback_policy (page 173).
• NODE_NAME. Enter the node or nodes on which the package can run; as described under
node_name (page 170).
• AUTO_RUN. Configure the package to start up automatically or manually; as described under
auto_run (page 170).
• NODE_FAIL_FAST_ENABLED. Enter the policy as described under
node_fail_fast_enabled (page 171).
• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the package control script
(described in the next section). No default is provided. Permissions on the file and directory
should be set to rwxr-xr-x or r-xr-xr-x (755 or 555).
(Script timeouts): Enter the run_script_timeout (page 171) and halt_script_timeout
(page 171).
SCRIPT_LOG_FILE. (optional). Specify the full pathname of the file where the RUN_SCRIPT
and HALT_SCRIPT will log messages. If you do not specify a path, Serviceguard will create
a file with “.log” appended to each script path, and put the messages in that file.
• If your package has relocatable IP addresses, enter the SUBNET if you want it to be monitored
(this means the package will stop if the subnet fails).
This must be a subnet that is already specified in the cluster configuration, and it can be either
an IPv4 or an IPv6 subnet. It must not be a link-local subnet (link-local package IPs are not
allowed). See monitored_subnet (page 175).
226 Cluster and Package Maintenance