Managing Serviceguard NFS for Linux Manufacturing Part Number : T1442-90015 July 2007
Legal Notices © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents 1. Serviceguard NFS for LINUX Introduction Overview of Serviceguard NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Limitations of Serviceguard NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview of the NFS File Lock Migration Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Limitations of the NFS File Lock Migration Feature . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Package Control Script for pkg02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NFS Toolkit Configuration File for pkg02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Package Configuration File for pkg03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Package Control Script for pkg03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NFS Toolkit Configuration File for pkg03 . . . . . . . .
Serviceguard NFS for LINUX Introduction 1 Serviceguard NFS for LINUX Introduction This manual describes how to install and configure an Serviceguard NFS toolkit on a Linux system. Serviceguard NFS® is a toolkit that allows you to use Serviceguard to set up highly available NFS servers. The information presented in this manual assumes you are familiar with Serviceguard and NFS operations. Refer to your Serviceguard and/or NFS documentation for additional information.
Serviceguard NFS for LINUX Introduction Overview of Serviceguard NFS Overview of Serviceguard NFS An NFS server is a host that “exports” its local directories (makes them available for client hosts to mount using NFS). On the NFS client, these mounted directories look to users like part of the client’s local file system. Serviceguard allows you to create high availability clusters of HP Linux computers (nodes).
Serviceguard NFS for LINUX Introduction Limitations of Serviceguard NFS Limitations of Serviceguard NFS The following limitations apply to Serviceguard NFS: NOTE Chapter 1 • File locks are not maintained when an NFS server package moves to an adoptive node. Any applications that use file locking must reclaim their locks after an NFS server package fails over. An application that loses its file lock as a result of an NFS package failover will not be notified.
Serviceguard NFS for LINUX Introduction Overview of the NFS File Lock Migration Feature Overview of the NFS File Lock Migration Feature The following describes the File Lock Migration feature, which is part of the NFS toolkit starting with version A.02.00: 8 • Designate a unique holding directory as part of the NFS package located on a shared filesystem. In other words, an empty directory is created on a shared filesystem that moves between servers as part of the package.
Serviceguard NFS for LINUX Introduction Overview of the NFS File Lock Migration Feature • Chapter 1 After sm-notify/rpc.statd sends the crash recovery notification messages, the SM entries in the package holding directory are removed, and the nfs.flm script is started on the adoptive node. The script once again copies each file in sm directory (/var/lib/nfs/sm on SLES and /var/lib/nfs/statd/sm on RedHat) of the NFS server into the holding directory periodically.
Serviceguard NFS for LINUX Introduction Limitations of the NFS File Lock Migration Feature Limitations of the NFS File Lock Migration Feature The following describes limitations of the NFS File Lock Migration feature: • Multiple NFS packages are not supported on the same node The file lock migration feature will not work for multiple NFS packages running on the same node.
Serviceguard NFS for LINUX Introduction Limitations of the NFS File Lock Migration Feature SERVICE_FAIL_FAST_ENABLED should be set to “YES” for the NFS monitoring service in order to have lock migration feature work consistently.
Serviceguard NFS for LINUX Introduction Supported Configurations Supported Configurations Serviceguard NFS supports the following configurations and are illustrated in the following sections: 12 • Simple failover from an active NFS server node to an idle NFS server node. • Failover from one active NFS server node to another active NFS server node, where the adoptive node supports more than one NFS package after the failover. • A host configured as an adoptive node for more than one NFS package.
Serviceguard NFS for LINUX Introduction Supported Configurations Failover to an Idle Node Figure 1-1 shows a simple failover from an active NFS server node to an idle NFS server node. Figure 1-1 Simple Failover to an Idle NFS Server Node_A is the primary node for NFS server package Pkg_1. When Node_A fails, Node_B adopts Pkg_1. This means that Node_B locally mounts the file systems associated with Pkg_1 and exports them.
Serviceguard NFS for LINUX Introduction Supported Configurations Failover between Active Nodes Figure 1-2 shows a failover from one active NFS server node to another active NFS server node. In Figure 1-2, Node_A is the primary node for Pkg_1, and Node_B is the primary node for Pkg_2. When Node_A fails, Node_B adopts Pkg_1 and becomes the server for both Pkg_1 and Pkg_2.
Serviceguard NFS for LINUX Introduction Supported Configurations Failover with an Adoptive Node for Multiple Packages Figure 1-3 shows a three-node configuration where one node is the adoptive node for packages on both of the other nodes. If either Node_A or Node_C fails, Node_B adopts the NFS server package from that node. When Node_A fails, Node_B becomes the server for Pkg_1. If Node_C fails, Node_B will become the server for Pkg_2.
Serviceguard NFS for LINUX Introduction Supported Configurations Cascading Failover with Multiple Adoptive Nodes Consider a package that is configured up to three adoptive nodes. Figure 1-4 shows this configuration. If Node_A fails, Pkg_1 is adopted by Node_B. However, if Node_B is down, Pkg_1 is adopted by Node_C, and if Node_C is down, Pkg_1 is adopted by Node_D.
Serviceguard NFS for LINUX Introduction Understanding the Serviceguard NFS Files Understanding the Serviceguard NFS Files Serviceguard NFS uses files similar and typical to Serviceguard. These include configuration files, control scripts, monitoring scripts, and templates. As is true for all Serviceguard packages, you configure and view a small number of files. The following is a brief description of the files: • Files that apply to the whole cluster: — cluster configuration file, cluster.
Serviceguard NFS for LINUX Introduction How the Control and Monitor Scripts Work How the Control and Monitor Scripts Work As with all Serviceguard packages, the package control scripts start and stop the NFS package and determine how the package will operate once it becomes available on a particular node. Each control script contains two sets of code that operate depending on whether the script is called with the start parameter or the stop parameter. A template package control script pkg.
Serviceguard NFS for LINUX Introduction How the Control and Monitor Scripts Work Starting File Lock Migration If you call the NFS control script with the lock_migration: parameter after enabling the File Lock Migration feature, the control script does the following: • Populates the /var/lib/nfs/sm directory on SLES and /var/lib/nfs/statd/sm directory on RedHat with the Status Monitor entries from the configured holding directory of the package, and subsequently removes the entries from the hol
Serviceguard NFS for LINUX Introduction How the Control and Monitor Scripts Work After this sequence, the NFS package is inactive on the current node and may start up on an alternate node or be restarted later on the same node. Monitoring the NFS Services The monitor script nfs.mon, located in the file /usr/local/cmcluster/nfstoolkit for RedHat environments, and /opt/cmcluster/nfstoolkit for SLES environments), works by periodically checking the status of NFS services using the rpcinfo command.
Serviceguard NFS for LINUX Introduction How the Control and Monitor Scripts Work Whenever the monitor script detects an event, it logs information to a file using the same name as your NFS control script adding a .log extension. Each NFS package has its own log file. For example, if your control script is called pkg1.cntl, the package log file is called pkg1.cntl.log. The NFS monitor log file, which is on the same directory as the NFS control script, is always called hanfs.sh.log.
Serviceguard NFS for LINUX Introduction How the Control and Monitor Scripts Work 22 Chapter 1
Installing and Configuring Serviceguard NFS for Linux 2 Installing and Configuring Serviceguard NFS for Linux This chapter explains how to configure Serviceguard NFS. NOTE You must set up your Serviceguard cluster and make sure NFS server is installed before configuring Serviceguard NFS. For instructions on setting up an Serviceguard cluster, see Chapters 5 and 6 of the Managing Serviceguard for Linux user’s guide.
Installing and Configuring Serviceguard NFS for Linux Installing Serviceguard NFS for Linux Installing Serviceguard NFS for Linux The following describes the Serviceguard NFS Toolkit for Linux installation process. 1. Check for and remove any previous version of Serviceguard NFS for Linux: Query the rpm database for the NFS Toolkit: # rpm -qa |grep nfstoolkit If any part of the NFS Toolkit is installed, the grep returns the version number.
Installing and Configuring Serviceguard NFS for Linux Installing Serviceguard NFS for Linux The files will be installed in the following directories: /usr/bin and /usr/local/cmcluster/nfstoolkit for RedHat and /opt/cmcluster/nfstoolkit for SLES. The following files are part of the toolkit: NOTE The following procedures assume your environment is RedHat. If your environment is SLES, replace all occurrences of “/usr/local” with “/opt”. • /usr/local/cmcluster/nfstoolkit/README.
Installing and Configuring Serviceguard NFS for Linux Installing Serviceguard NFS for Linux 5. Issue the following command to copy the Serviceguard NFS template files to the newly created package directory: # cp /usr/local/cmcluster/nfstoolkit/* \ /usr/local/cmcluster/ Copying the Template Files If you will run only one Serviceguard NFS package in your Serviceguard cluster, technically you do not have to copy the template files.
Installing and Configuring Serviceguard NFS for Linux Before Creating an Serviceguard NFS Package Before Creating an Serviceguard NFS Package Before creating a Serviceguard NFS package, perform the following tasks: NOTE The following procedures assume your environment is RedHat. If your environment is SLES, replace all occurrences of “/usr/local” with “/opt”. 1. Select the NFS Server package during Red Hat Linux installation and verify that the NFS is properly installed.
Installing and Configuring Serviceguard NFS for Linux Before Creating an Serviceguard NFS Package 3. Configure the disk hardware for high availability. Data disks associated with Serviceguard NFS must be external disks. All the nodes that support the Serviceguard NFS package must have access to the external disks. For most disks this means they must be attached to a shared bus that is connected to all nodes which support the package.
Installing and Configuring Serviceguard NFS for Linux Before Creating an Serviceguard NFS Package 7. Decide whether to place executables locally on each client or on the NFS server. There are a number of trade-offs to be aware of regarding the location of executables with Serviceguard NFS. The advantages of keeping executables local to each client are as follows: • No failover time. If the executables are local to the client, there is no delay if the NFS server fails.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package Configuring a Serviceguard NFS Package To configure a Serviceguard NFS package, complete the following tasks, described in this section: NOTE • Editing the Package Configuration File (pkg.conf) • Editing the Package Control Scripts (pkg.cntl) • Editing the NFS Configuration File (hanfs.conf) • Creating the Serviceguard Binary Configuration File Repeat the configuration process for each NFS package.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package NODE_NAME thyme NODE_NAME basil NODE_NAME sage 4. Set the RUN_SCRIPT and HALT_SCRIPT variables to the full path name of the control script. You do not have to specify a timeout for either script. For example: RUN_SCRIPT /usr/local/cmcluster/pkg1/pkg1.cntl RUN_SCRIPT_TIMEOUT NO_TIMEOUT HALT_SCRIPT /usr/local/cmcluster/pkg1/pkg1.cntl HALT_SCRIPT_TIMEOUT NO_TIMEOUT 5.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package Editing the Package Control Scripts (pkg.cntl) The following steps describe the required modifications to the Package Control Scripts. Make one Package Control Script for each package. NOTE The following procedures assume your environment is RedHat. If your environment is SLES, replace all occurrences of “/usr/local” with “/opt”. 1. Create a separate VG[n] variable for each volume group.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package HA_APP_SERVER=”pre-IP” 5. If two packages have the same adoptive node, and you want to prevent a shared adoptive node from adopting both packages at once, specify the cmmodpkg command with the package control option (-d) in the customer_defined_run_cmds.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package 6. Use the default values for the rest of the variables in the control script, or change them as needed. For instructions on modifying the default values, see the Managing Serviceguard for Linux manual, or read the comments in the /usr/local/cmcluster/nfstoolkit/pkg.cntl template file. Editing the NFS Configuration File (hanfs.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package NFS_SERVICE_CMD[0]=/usr/local/cmcluster/pkg1/nfs.mon Multiple instances of the monitor script can run on the same node without any problems, and if a package fails over, only the instance associated with that package is terminated. If you do not want to run the NFS monitor script: Comment out the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables. For example: # NFS_SERVICE_NAME[0]=nfs1.monitor 3.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package NFS fails to create sm directory entries. After a fail back, if the client attempts to reclaim his locks, fresh entries for the clients will not be made in the /var/lib/nfs/sm directory of the server. For SLES, it is mandatory to set SERVICE_FAIL_FAST_ENABLED to “YES”, so the server reboots in order to have lock migration feature work consistently.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package test_return 51 NOTE A Serviceguard package can support multiple relocatable IP addresses associated with it. However, if lock migration feature is enabled then only one IP is allowed to be specified in the NFS package control script since the NFS limits server reboot/failover notification is sent using only a single IP.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package Number of seconds between the attempts of the script to copy files from the /var/lib/nfs/sm directory on SLES and /var/lib/nfs/statd/sm on RedHat into the holding directory, specified by NFS_FLM_HOLDING_DIR. The default value of this parameter is five seconds.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package NOTE To use the lock migration feature, the user has to do all the configurations specified above and also consider all the limitations of the lock migration feature mentioned in the section on See “Limitations of the NFS File Lock Migration Feature” on page 10. Creating the Serviceguard Binary Configuration File 1.
Installing and Configuring Serviceguard NFS for Linux Configuring a Serviceguard NFS Package 40 Chapter 2
Sample Configurations 3 Sample Configurations This chapter gives sample cluster configuration files, package configuration files, package control script, and NFS control script for configurations supporting the following failover options: NOTE • Failover between multiple active nodes. The sample configuration has three servers and three Serviceguard NFS packages and supports a three-server mutual takeover. Each server is the primary node for one package and an adoptive node for the other two packages.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Configuring Multiple Nodes to Support Failover of Multiple Packages This configuration has three servers and three Serviceguard NFS packages. Each server is the primary node for one package and an adoptive node for the other two packages. Figure 3-1 illustrates this configuration. Dotted lines indicate which servers are adoptive nodes for the packages. Figure 3-2 illustrates the configuration after host basil fails.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Figure 3-2 shows the three-server mutual takeover configuration after host basil has failed and host sage has adopted pkg02. Dotted lines indicate which servers are adoptive nodes for the packages.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Cluster Configuration File for Three-Server Mutual Takeover This section shows the cluster configuration file (cluster.conf) for this configuration example. The comments are not shown. 44 CLUSTER_NAME MutTakOvr QS_HOST QS_POLLING_INTERVAL qs 300000000 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP NETWORK_INTERFACE thyme eth0 192.100.112.146 eth1 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP basil eth0 192.100.112.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Package Configuration File for pkg01 This section shows the package configuration file (pkg1.conf) for the package pkg01 in this sample configuration. The comments are not shown.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages 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.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Package Configuration File for pkg02 This section shows the package configuration file (pkg2.conf) for the package pkg02 in this sample configuration. The comments are not shown.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Package Control Script for pkg02 This section shows the package control script (pkg2.cntl) for the package pkg02 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.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Package Configuration File for pkg03 This section shows the package configuration file (pkg3.conf) for the package pkg03 in this sample configuration. The comments are not shown.
Sample Configurations Configuring Multiple Nodes to Support Failover of Multiple Packages Package Control Script for pkg03 This section shows the NFS control script (pkg3.cntl) for the package pkg03 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.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages 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.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages Figure 3-4 shows this sample configuration after host basil has failed. Host sage has adopted pkg02. NOTE Setting the package control option (-d) of the cmmodpkg command, prevents host sage from adopting another package, so host sage is no longer an adoptive node for pkg01. This prevent the adoptive node (sage) from becoming overloaded when multiple packages failover.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages Cluster Configuration File for Adoptive Node for Two Packages This section shows the cluster configuration file (cluster.conf) for this configuration example. The comments are not shown. Chapter 3 CLUSTER_NAME PkgCtrl QS_HOST QS_POLLING_INTERVAL qs 300000000 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP NETWORK_INTERFACE thyme eth0 192.100.112.146 eth1 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP basil eth0 192.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages Package Configuration File for pkg01 This section shows the package configuration file (pkg1.conf) for the package pkg01 in this sample configuration. The comments are not shown.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages 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.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages NFS Toolkit Configuration File for pkg01 This section shows the NFS Toolkit configuration file (hanfs.conf) for the package pkg01 on this sample configuration: XFS[0]="-o rw *:/hanfs/nfsu011" NFS_SERVICE_NAME[0]="nfs1.monitor" NFS_SERVICE_CMD[0]="/usr/local/cmcluster/pkg1/nfs.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages Package Configuration File for pkg02 This section shows the package configuration file (pkg2.conf) for the package pkg02 in this sample configuration. The comments are not shown.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages Package Control Script for pkg02 This section shows the package control script (pkg2.cntl) for the package pkg02 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.
Sample Configurations Configuring One Adoptive Node to Support Failover of Multiple Packages NFS Toolkit Configuration File for pkg02 This section shows the NFS Toolkit configuration file (hanfs.conf) for the package pkg02 on this sample configuration: XFS[0]="-o rw *:/hanfs/nfsu021" NFS_SERVICE_NAME[0]="nfs2.monitor" NFS_SERVICE_CMD[0]="/usr/local/cmcluster/pkg2/nfs.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Configuring Multiple Adoptive Nodes for 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 3-5 illustrates this configuration. Dotted lines indicate which servers are adoptive nodes for the packages. Figure 3-6 illustrates the configuration after host thyme fails.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Figure 3-6 shows the cascading failover configuration after host thyme has failed. Host basil is the first adoptive node configured for pkg01, and host sage is the first adoptive node configured for pkg02.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Cluster Configuration File for Three-Server Cascading Failover This section shows the cluster configuration file (cluster.conf) for this configuration example. The comments are not shown. CLUSTER_NAME Cascading QS_HOST QS_POLLING_INTERVAL qs 300000000 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP NETWORK_INTERFACE thyme eth0 192.100.112.146 eth1 NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP basil eth0 192.100.112.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Package Configuration File for pkg01 This section shows the package configuration file (pkg1.conf) for the package pkg01 in this sample configuration. The comments are not shown.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover 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.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Package Configuration File for pkg02 This section shows the package configuration file (pkg2.conf) for the package pkg02 in this sample configuration. The comments are not shown.
Sample Configurations Configuring Multiple Adoptive Nodes for Cascading Failover Package Control Script for pkg02 This section shows the package control script (pkg2.cntl) for the package pkg02 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.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration Configuring One Adoptive Node for an NFS package with File Lock Migration 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 this sample configuration enables the File Lock Migration Feature.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration Figure 3-7 68 One Adoptive Node for an NFS Package Chapter 3
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration Figure 3-8 shows the same configuration after one primary server has failed. Figure 3-6 shows this sample configuration after host basil has failed. Host sage has adopted pkg02.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration 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.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration 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.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration 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.
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration NFS_FLM_HOLDING_DIR="/hanfs/nfsu011/sm" PROPAGATE_INTERVAL=5 NFS_FLM_MONITOR=YES NFS_FLM_RESTART=4 Chapter 3 73
Sample Configurations Configuring One Adoptive Node for an NFS package with File Lock Migration 74 Chapter 3
Index A adoptive nodes, 12 configuring, 30 example of cascading failover, 60 example of package control option, 51 for multiple packages, 12, 15, 33, 51 illustration of cascading failover, 16 AUTO_RUN, 31 automounter timeout, 21 B binary configuration files, creating, 39 C cascading failover, 12 example configuration, 60 illustration of, 16 client behavior, 6, 21 cluster configuration file (cluster.
Index mapping to logical name, 28 IP variable, in nfs.cntl script, 32 L lockd monitoring, 20 locked files, during package failover, 7 logging, NFS monitor script, 21 logical volumes configuration, 28 specifying in nfs.cntl, 32 LV variable, in nfs.cntl script, 32 M MC/ServiceGuard documentation, 27 monitor script (nfs.mon), 20 logging, 21 specified in nfs.
Index T timeout, automounter, 21 U unexporting file systems, 19 unmounting file systems, 19 user IDs, 28 V VG variable, in nfs.cntl script, 32 volume groups activating, 18 configuring, 28 deactivating, 19 major and minor numbers, 28 specifying in nfs.cntl, 32 X XFS variable, in nfs.
