This configuration has two NFS servers and one NFS package,
One server is the primary node and the other server is the adoptive
node for the NFS package. As shown in Figure 3-7 “One
Adoptive Node for an NFS Package” this sample configuration enables the File Lock
Migration Feature.
Figure 3-8 “NFS
Package on Adoptive Node After One Server Fails” shows the same
configuration after one primary server has failed. Figure 3-6 “Cascading
Failover with Three Servers After One Server Fails” shows this sample configuration after
host basil has failed. Host sage has adopted pkg02.
Cluster
Configuration File for Adoptive Node for NFS package with File Lock
Migration |
 |
This section shows an example of the cluster configuration
file (cluster.conf) for NFS package with File Lock Migration. The comments
are not shown.
CLUSTER_NAME PkgCtrlQS_HOST qsQS_POLLING_INTERVAL 300000000NODE_NAME thyme NETWORK_INTERFACE eth0 HEARTBEAT_IP 192.100.112.146 NETWORK_INTERFACE eth1NODE_NAME sage NETWORK_INTERFACE eth0 HEARTBEAT_IP 192.100.112.184 NETWORK_INTERFACE eth1 NETWORK_INTERFACE eth2HEARTBEAT_INTERVAL 1000000NODE_TIMEOUT 5000000AUTO_START_TIMEOUT 600000000NETWORK_POLLING_INTERVAL 2000000MAX_CONFIGURED_PACKAGES 4 |
Package
Configuration File for pkg01 |
|
This section shows an example of the package configuration
file (pkg1.conf) for the package pkg01 in this sample configuration. The comments are not shown.
PACKAGE_NAME pkg01PACKAGE_TYPE FAILOVERFAILOVER_POLICY CONFIGURED_NODEFAILBACK_POLICY MANUALNODE_NAME thymeNODE_NAME sageAUTO_RUN YESNODE_FAIL_FAST_ENABLED NORUN_SCRIPT /usr/local/cmcluster/pkg1/pkg1.cntlRUN_SCRIPT_TIMEOUT NO_TIMEOUTHALT_SCRIPT /usr/local/cmcluster/pgk1/pkg1.cntlHALT_SCRIPT_TIMEOUT NO_TIMEOUTSERVICE_NAME nfs1.monitorSERVICE_FAIL_FAST_ENABLED YESSERVICE_HALT_TIMEOUT 300SUBNET 192.100.112.0 |
Package
Control Script for pkg01 |
|
This section shows the package control script (pkg1.cntl) for the package pkg01 in this sample configuration. Only the user-configured part
of the script is shown; the executable part of the script and most
of the comments have been omitted.
PATH=/sbin:/usr/bin:/usr/sbin:/etc:/bin:usr/local/cmcluster/binVGCHANGE="vgchange -a y" # DefaultVG[0]="nfsu01"LV[0]=/dev/nfsu01/lvol1; FS[0]=/hanfs/nfsu011; FS_TYPE[0]="ext2"; FS_MOUNT_OPT[0]="-o rw"# FS_UMOUNT_COUNT=""# FS_MOUNT_RETRY_COUNT=""IP[0]="192.100.112.243"SUBNET[0]="192.100.112.0"HA_APP_SERVER="pre-IP"#SERVICE_NAME[0]=""#SERVICE_CMD[0]=""#SERVICE_RESTART[0]="" function customer_defined_run_cmds{ $HA_APP_SCRIPT lock_migration:${IP[0]} test_return 51} |
The function customer_defined_run_cmds calls the toolkit.sh script with lock_migration:<IP_address> parameter for file lock migration.The argument to be
passed to the HA_APP_SCRIPT for lock migration should contain the same name or IP
address used by the clients while mounting the exported file system.
NFS
Toolkit Configuration File for pkg01(hanfs.conf) |
|
This section shows the NFS toolkit configuration file (hanfs.conf) for the package pkg01 on this sample configuration. This example enables the
File Lock Migration feature.
XFS[0]="-o rw *:/hanfs/nfsu011"NFS_SERVICE_NAME[0]="nfs1.monitor"NFS_SERVICE_CMD[0]="/usr/local/cmcluster/pkg1/nfs.mon"NFS_SERVICE_RESTART[0]="-r 0"LOCK_MIGRATION=YESNFS_FLM_HOLDING_DIR="/hanfs/nfsu011/sm"PROPAGATE_INTERVAL=5NFS_FLM_MONITOR=YESNFS_FLM_RESTART=4 |
Printable version
