Managing Serviceguard NFS for Linux, March 2009

node_name thyme
node_name basil
auto_run yes
node_fail_fast_enabled no
script_log_file /usr/local/cmcluster/pkg03/log
TKIT_DIR /usr/local/cmcluster/pkg03
XFS[0] "-o rw *:/hanfs/nfsu031"
QUOTA_MON YES
LOCK_MIGRATION NO
monitored_subnet 192.100.112.0
monitored_subnet_access full
service_name nfs3.monitor
service_cmd "$SGCONF/scripts/tkit/nfs/tkit_module.sh nfs_monitor"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
external_script $SGCONF/scripts/tkit/nfs/lock_migration.sh
ip_subnet 192.100.112.0
#ip_subnet_node
ip_address 192.100.112.245
vgchange_cmd "vgchange -a y"
vg nfsu03
fs_name /dev/nfsu03/lvol1
fs_directory /hanfs/nfsu031
fs_type ext3
fs_mount_opt "-o rw"
# fs_umount_opt
# fs_fsck_opt
Configuring One Adoptive Node to Support Failover of Multiple Packages
This configuration has two packages, each owned by a different server. The adoptive node for
both packages is the same host. This sample configuration uses the package control option, which
prevents the adoptive node from adopting another package if it has already adopted one.
Figure 3-3 illustrates this configuration. Figure 3-4 shows the same configuration after one primary
server has failed.
Figure 3-3 One Adoptive Node for Two Packages
Figure 3-4 shows this sample configuration after host basil has failed. Host sage has adopted
pkg02.
40 Sample Configurations