Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.05 Administrator's Guide HP-UX 11i v1, v2, and v3

XFS "/hanfs/nfsu021"
FILE_LOCK_MIGRATION 1
FLM_HOLDING_DIR "/hanfs/nfsu021/sm"
PROPAGATE_INTERVAL 5
The external script file for this package can be created in any package specific location using the
external script template file.
cp /etc/cmcluster/examples/external_script.template /pkg02_location/pkg02_ext
Also, specify the external script file location in the package configuration file (nfs2.conf) as
external_script /pkg02_location/pkg02_ext
In the external script file, add the following lines to the start_command function.
function start_command
{
cmmodpkg -d -n 'hostname' pkg01 &
return 0
}
The function start_command in the external script calls the cmmodpkg command with the
package control option (-d). This command prevents the host that is running pkg02 from
adopting pkg01. The ampersand (&) causes the cmmodpkg command to run in the background.
It must run in the background to allow the control script to complete.
There is a short time, after one primary node has failed but before the cmmodpkg command has
executed, when the other primary node can fail and the adoptive node will adopt its package.
In other words, if both thyme and basil fail at approximately the same time, host sage may
adopt two packages, even though the package control option is specified.
If you omit the cmmodpkg -d command from the NFS control script, host sage can adopt both
pkg01 and pkg02 if their primary nodes fail.
Example Three - Three-Server Cascading Failover
This configuration has two packages and three servers. One server is the primary node for both
packages. The other servers are adoptive nodes for the two packages. Figure 6-5 illustrates this
configuration. Dotted lines indicate which servers are adoptive nodes for the packages.
102 Sample Configurations for Modular Package