IMPORTANT: Restrictions on dependency names in previous Serviceguard releases were less stringent. Packages that specify dependency_names that do not conform to the above rules will continue to run, but if you reconfigure them, you will need to change the dependency_name; cmcheckconf and cmapplyconf will enforce the new rules.

Configure this parameter, along with dependency_condition and dependency_location, if this package depends on another package; for example, if this package depends on a package named pkg2 to be running on the same node:

dependency_name pkg2dep dependency_condition pkg2 = UP dependency_location same_node

For more information about package dependencies, see the parameter descriptions that follow, the cmmakepkg (1m) manpage, and the discussion in this manual “About Package Dependencies” (page 137).

dependency_condition

The condition that must be met for this dependency to be satisfied.

The syntax is: <package_name> = <package_status>. <package_name> is the name of the package depended on. Valid values for <package_status> are UP, or DOWN.

UP means that this package requires the package identified by <package_name> to be up (that is, the status reported by cmviewcl is UP).

If you specify UP, the type and characteristics of the current package (the one you are configuring) impose the following restrictions on the type of package it can depend on:

If the current package is a multi-node package, <package_name> must identify a multi-node or system multi-node package.

If the current package is a failover package and its failover_policy (page 237) is min_package_node, <package_name> must identify a multi-node or system multi-node package.

If the current package is a failover package and its failover_policy (page 237) is configured_node , <package_name> must identify a multi-node or system multi-node package, or a failover package whose failover_policy is configured_node.

DOWN means that this package requires the package identified by <package_name> to be down (that is, the status reported by cmviewcl is UP). This is known as an exclusionary dependency (or exclusion dependency).

If you specify DOWN:

The exclusionary dependency must be mutual: only one of the packages can be running at any given time. For example, if pkgA depends on pkgB to be down, pkgB must also depend on pkgA to be down.

You must apply both packages to the cluster configuration at the same time.

Both packages must be failover packages whose failover_policy is configured_node.

At least one of the packages must specify a priority (page 238).

For more information, see “About Package Dependencies” (page 137).

Choosing Package Modules 239

Page 239
Image 239
HP Serviceguard manual Dependencycondition, For more information, see About Package Dependencies