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

function start_command
{
cmmodpkg -d -n 'hostname' pkg02 &
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 pkg01 from
adopting pkg02. 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 calling the cmmodpkg -d command through external script, host sage can adopt
both pkg01 and pkg02 if their primary nodes fail.
Package Configuration File for pkg02
This section shows the package configuration file (nfs2.conf) for the package pkg02 in this
sample configuration. The comments available in the generated configuration file are not displayed
in this sample.
package_name pkg02
package_type failover
failover_policy configured_node
failback_policy manual
node_name basil
node_name sage
auto_run yes
local_lan_failover_allowed yes
node_fail_fast_enabled no
service_name nfs2.monitor
service_fail_fast_enabled no
service_halt_timeout 300
vgchange_cmd "vgchange -a e" # Default
cvm_activation_cmd "vxdg -g \$DiskGroup set activation=exclusivewrite"
vg nfsu02
fs_name /dev/nfsu02/lvol1
fs_directory /hanfs/nfsu021
vxvol_cmd "vxvol -g \$DiskGroup startall" #Default
fs_umount_retry_count 1
fs_mount_retry_count 0
ip_address 15.13.114.244
ip_subnet 15.13.112.0
Example Two - One Adoptive Node for Two Packages with File Lock Migration 101