Managing HP Serviceguard A.12.00.00 for Linux, June 2014

NOTE: cmcheckconf and cmapplyconf check for missing mount points, volume groups,
etc.
4. Halt the package.
5. Configure package IP addresses and application services.
6. Run the package and ensure that applications run as expected and that the package fails over
correctly when services are disrupted. See “Testing the Package Manager ” (page 269).
Use the following bullet points as a checklist, referring to the “Package Parameter Explanations”
(page 184), and the comments in the configuration file itself, for detailed specifications for each
parameter.
NOTE: Optional parameters are commented out in the configuration file (with a # at the beginning
of the line). In some cases these parameters have default values that will take effect unless you
uncomment the parameter (remove the #) and enter a valid value different from the default. Read
the surrounding comments in the file, and the explanations in this chapter, to make sure you
understand the implications both of accepting and of changing a given default.
In all cases, be careful to uncomment each parameter you intend to use and assign it the value
you want it to have.
• package_name. Enter a unique name for this package. Note that there are stricter formal
requirements for the name as of A.11.18.
• package_type. Enter failover or multi_node. ( system_multi_node is reserved
for special-purpose packages supplied by HP.) Note that there are restrictions
if another package depends on this package; see “About Package Dependencies” (page 111).
See “Types of Package: Failover, Multi-Node, System Multi-Node” (page 179) for more
information.
• node_name. Enter the name of each cluster node on which this package can run, with a
separate entry on a separate line for each node.
• auto_run. For failover packages, enter yes to allow Serviceguard to start the package on
the first available node specified by node_name, and to automatically restart it later if it fails.
Enter no to keep Serviceguard from automatically starting the package.
• node_fail_fast_enabled. Enter yes to cause the node to be halted (system halt) if the
package fails; otherwise enter no.
• run_script_timeout and halt_script_timeout. Enter the number of seconds
Serviceguard should wait for package startup or shutdown, respectively, to complete; or leave
the default, no_timeout. See (page 187).
• successor_halt_timeout. Used if other packages depend on this package; see “About
Package Dependencies” (page 111).
• script_log_file (page 188).
• log_level (page 188).
• failover_policy (page 188). Enter configured_node or min_package_node.
(This parameter can be set for failover packages only.)
• failback_policy (page 189) . Enter automatic or manual.
(This parameter can be set for failover packages only.)
6.3 Editing the Configuration File 203