Managing HP Serviceguard A.11.20.20 for Linux, May 2013

• 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 177).
• successor_halt_timeout. Used if other packages depend on this package; see “About
Package Dependencies” (page 112).
• script_log_file (page 178).
• log_level (page 178).
• failover_policy (page 178). Enter configured_node or min_package_node.
(This parameter can be set for failover packages only.)
• failback_policy (page 179) . Enter automatic or manual.
(This parameter can be set for failover packages only.)
• If this package will depend on another package or packages, enter values for
dependency_name, dependency_condition, dependency_location, and optionally
priority.
See “About Package Dependencies” (page 112) for more information.
NOTE: The package(s) this package depends on must already be part of the cluster
configuration by the time you validate this package (via cmcheckconf; see “Verifying and
Applying the Package Configuration” (page 196)); otherwise validation will fail.
• To configure package weights, use the weight_name and weight_value parameters
(page 181). See “About Package Weights” (page 120) for more information.
• Use monitored_subnet to specify a subnet to be monitored for this package. If there are
multiple subnets, repeat the parameter as many times as needed, on a new line each time.
In a cross-subnet configuration, configure the additional monitored_subnet_access
parameter for each monitored_subnet as necessary; see “About Cross-Subnet Failover”
(page 130) for more information.
• If your package will use relocatable IP addresses, enter the ip_subnet and ip_address
addresses. See the parameter descriptions (page 182) for rules and restrictions.
In a cross-subnet configuration, configure the additional ip_subnet_node parameter for
each ip_subnet as necessary; see “About Cross-Subnet Failover” (page 130) for more
information.
• For each service the package will run:
◦ enter the service_name (for example, a daemon or long-running process)
◦ enter the service_cmd (for example, the command that starts the process)
194 Configuring Packages and Their Services