Managing HP Serviceguard A.11.20.10 for Linux, December 2012

Figure 19 Legacy Package Time Line Showing Important Events
The following are the most important moments in a package’s life:
1. Before the control script starts. (For modular packages, this is the master control script.)
2. During run script execution. (For modular packages, during control script execution to start
the package.)
3. While services are running
4. If there is a generic resource configured and it fails, then the package will be halted.
5. When a service or subnet fails, or a dependency is not met.
6. During halt script execution. (For modular packages, during control script execution to halt
the package.)
7. When the package or the node is halted with a command
8. When the node fails
3.4.2 Before the Control Script Starts
First, a node is selected. This node must be in the package’s node list, it must conform to the
package’s failover policy, and any resources required by the package must be available on the
chosen node. One resource is the subnet that is monitored for the package. If the subnet is not
available, the package cannot start on this node. Another type of resource is a dependency on
another package. If monitoring shows a value for a configured resource that is outside the permitted
range, the package cannot start.
If a generic resource of type BPS is configured, it must be up; if not, the package cannot start on
this node.
Once a node is selected, a check is then done to make sure the node allows the package to start
on it. Then services are started up for a package by the control script on the selected node. Strictly
speaking, the run script on the selected node is used to start a legacy package; the master control
script starts a modular package.
3.4 How Packages Run 53