Managing HP Serviceguard A.12.00.00 for Linux, June 2014
Figure 32 Failover of a Package
pkg1 (wt=4) fails over
to Node 2
pkg3 (wt=7)
pkg2 (wt=3)
Cap=11
Remaining Cap=1
Node 1
pkg4 (wt=10)
Cap=14
Remaining Cap=0
Node 2
pkg5 (wt=6)
Cap=8
Remaining Cap=2
Node 3 Node 4
When finite capacity is configured in a cluster, the package fails over to the node that has
the highest remaining capacity. Since the Node 2 has the highest remaining capacity of 4,
the pkg1 with weight of 4 fails over to Node 2.
Figure 33 (page 135) shows that pkg2 and pkg3 running on Node 1, pkg4 and pkg1 running
on Node 2, and pkg5 running on Node 3.
Figure 33 Load Distributed across the Nodes after Failover
pkg3 (wt=7)
pkg2 (wt=3)
Cap=11
Remaining Cap=1
Node 1
pkg4 (wt=10)
pkg1 (wt=4)
Cap=14
Remaining Cap=0
Node 2
pkg5 (wt=6)
Cap=8
Remaining Cap=2
Node 3
4.9.11 About External Scripts
As of Serviceguard A.11.18, the package configuration template for modular packages explicitly
provides for external scripts. It can be run either:
4.9 Package Configuration Planning 135