HP Serviceguard manual Before the Control Script Starts

NOTE: This diagram applies specifically to legacy packages. Differences for modular scripts are called out below.

Figure 22 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.When a service, subnet, or monitored resource fails, or a dependency is not met.

5.During halt script execution. (For modular packages, during control script execution to halt the package.)

6.When the package or the node is halted with a command

7.When the node fails

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 a monitored external resource or on a special-purpose package. If monitoring shows a value for a configured resource that is outside the permitted range, the package cannot start.

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.

How Packages Run 61