Understanding Serviceguard Package Dependencies, April 2009

Configuration examples

Same node dependency example:

Pkg1 requires pkg2 to be up on the same node before it can start and in order to continue running.

Include the following in the configuration file for pkg1:

Dependency_name pkg2dep

Dependency_condtion pkg2=up

Dependency_location same_node

Different node dependency example

Pkg1 requires pkg2 to be up on a different node before it can start and in order to continue running.

Include the following in the configuration file for pkg1:

Dependency_name pkg2dep

Dependency_condtion pkg2=up

Dependency_location different_node

Any node dependency example

Pkg1 requires pkg2 to be up on any node in the same cluster before it can start and in order to

continue running.

Include the following in the configuration file for pkg1:

Dependency_name pkg2dep

Dependency_condtion pkg2=up

Dependency_location any_node

Same node exclusionary (down) dependency example:

Pkg1 requires pkg2 to be down on same node before it can start and in order to continue running.

However pkg2 can be up on another node in the cluster. This dependency is mutual. Pkg1 needs to

define a same node “down” dependency on pkg2 and pkg2 needs to define a same node “down”

dependency on pkg1. Both configuration files must be applied at the same time. Note that at least

one of these packages must be assigned a numerical priority; the priority of both packages cannot be

“no_priority”.

Include the following in the configuration file for pkg1:

Dependency_name pkg2dep

Dependency_condtion pkg2=down

Dependency_location same_node

Include the following in the configuration file for pkg2:

Dependency_name pkg1dep

Dependency_condtion pkg1=down

Dependency_location same_node