HP Serviceguard Toolkit for NFS on Linux User Guide Version A.12.00.00 Abstract This guide describes instructions to start, stop, and monitor a Network File System in a Serviceguard cluster environment.
© Copyright 2014 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 Overview..................................................................................................4 Advantages.............................................................................................................................4 Dependencies..........................................................................................................................4 Prerequisites...........................................................................................................
1 Overview The HP Serviceguard Toolkit for NFS on Linux allows you to start, stop, and monitor a Network File System in a Serviceguard cluster environment. This toolkit consists of a set of shell scripts used by the toolkit framework to start, stop, and monitor NFS daemons. The toolkit simplifies making NFS exports highly available by integrating NFS with Serviceguard for Linux (SG/LX). The latest version of the HP Serviceguard Toolkit for NFS on Linux is available for free download at: http://software.hp.
• ◦ system-config-nfs-x.y.z-a.b..arch.rpm ◦ procmail-a.b-x.y..arch.rpm The following RPMs must be available for the NFS toolkit to function properly in the SLES11 environment. The version of these RPMs must be the latest supported version from the SLES11 OS. ◦ yast2-nfs-common-a.b.c-x.y.z..rpm ◦ nfs-kernel-server-a.b.c-x.y.z..rpm ◦ yast2-nfs-server-x.y.z-a.b.c..rpm ◦ quota-nfs-a.b-x.y.z..rpm ◦ limal-nfs-server-a.b.c-x.y.z..
2 Supported configuration This section explains the supported configurations for NFS toolkit packages. The following are the supported configurations: • Failover of an NFS toolkit package from an NFS server node to an alternative node in a cluster. • Configuring two NFS toolkit packages using NFSv4 protocol. • Coexistence of NFS toolkit package configured to use NFSv3 and NFSv4 package on the same node.
Configuring two NFS toolkit packages using NFSv4 protocol Figure 2 Configuring two NFSv4 toolkit packages Figure 2 (page 7) shows a scenario where two NFS toolkit packages are using NFSv4 protocol. This configuration supports two NFSv4 packages. In this configuration, Node_A is the primary node for NFS server packages, Pkg1_v4 and NFS server package Pkg2_v4, which is configured to use NFSv4 protocol.
Coexistence of NFS toolkit packages configured to use NFSv3 and NFSv4 protocols on the same node Figure 3 Coexistence of NFS package configured to use NFSv3 and NFSv4 protocols on the same node Figure 3 (page 8) illustrates a co-existence scenario where NFS toolkit packages are configured to use NFSv3 and NFSv4 protocols on the same node.
3 Installing and uninstalling HP Serviceguard toolkit for NFS Perform one of the following to install or to upgrade the NFS toolkit. This RPM must be installed on all the nodes of the cluster that are configured to run the NFS toolkit package. • For a fresh installation of the toolkit, run the following command: rpm -ivh serviceguard--toolkit-..noarch.rpm For example: rpm -ivh serviceguard-nfs-toolkit-A.12.00.00.sles.noarch.
Table 2 Files for creating modular packages 10 File Name Description nfs.1 This is the attribute definition file used $SGCONF/modules/tkit/nfs for the NFS toolkit packages created by previous toolkit versions. nfs.2 This is the attribute definition file used $SGCONF/scripts/tkit/nfs to generate the package ASCII template file. tkit_module.
4 Using HP Serviceguard toolkit for NFS After installing the HP Serviceguard Toolkit for NFS on Linux, you can use this toolkit to: • Deploy NFS as a toolkit package in a Serviceguard environment on Linux. • Manage the NFS toolkit packages. Deploying NFS toolkit packages You can deploy NFS toolkit packages by using only modular style of packaging. Configuring a modular NFS package To configure a NFS package using the modular style of packaging: 1.
Table 3 Modular NFS Package (continued) Attributes Description XFS This attribute refers to the exported NFS directories with export options. The commands exportfs -i and exportfs -u use these variables to export the file systems, and to unexport the file systems respectively. NOTE: HP recommends that you specify the fsid for the directory on the file system that must be exported. This ensures that permanent device minor number is retained during the failover to the adoptive node.
Table 3 Modular NFS Package (continued) Attributes Description package, NFS_FLM_HOLDING_DIR is set to /export/ sm and for NFSv4 package, NFS_FLM_HOLDING_DIR is set to /export/v4recovery. NOTE: The status monitor directory /var/lib/nfs/ statd/sm is applicable for NFSv3 and /var/lib/ nfs/v4recovery is applicable for NFSv4 protocol. 5. NFS_FLM_MONITOR This variable indicates whether the file lock migration script, nfs.flm must be monitored by the monitoring script.
• Starts NFS service processes (including nfs.mon). • Starts NFS file lock migration process if the lock migration feature is enabled. To start the package, use either of the following commands: • # cmrunpkg • # cmrunpkg -n Stopping the package The Serviceguard package manager invokes the NFS toolkit script with stop as an input paramenter. This in turn does the following: • Unexports directory on the file system.
• To achieve complete validation of cluster and application toolkit using single command execution. • To build a steady cluster for high available solution. You can use either the cmcheckconf –v or cmcheckconf –P commands to initiate the cluster verification. Run the cmcheckconf –v command to perform cluster wide verification of resources. This command also verifies the packages that are presently deployed in the system.
• Verify the presence of the NFS binaries that are required to start the following daemons for specific OS distribution: ◦ rpcbind ◦ rpc.statd ◦ rpc.mountd ◦ rpc.nfsd ◦ portmap ◦ rpc.idmapd if NFSv4 is used If the verification fails for the respective commands, the console displays the following error message: Error: does not exist. Solution: Install all the binaries specific to distributions, which provides the binaries required for the NFS server daemons to start.
• Use cmcheckconf command to verify the package configuration file. #cmcheckconf –P <>. NOTE: If you modify the unsupported attribute values, then appropriate error message is displayed when you run the execution of cmcheckconf -P command. • Use cmapplyconf command to add the new changes in the package configuration to the Serviceguard cluster environment. For example: #cmapplyconf –P <>.
Table 4 Modules affected during online addition (continued) Adding an IP sg/package_ip to the package (package_ip.sh) If an IP address which is added to the package configuration failed to add or not attempted, use the cmmodnet command to add the IP address. To add the IP to the package 10.149.2.5: #cmmodnet -a -I 10.149.2.5 10.149.2.0 For more information, see cmmodnet (1m) manpage. sg/external_script Adding an external script (external.
Toolkit sends an alert email with failure messages in the following scenarios when: • NFS daemon is not running on the node. Message: process is not running. NFS toolkit package failed on node . • RPC daemons fails to ping after specified number of retries. Message: Unable to ping process. NFS toolkit package failed on node . • rmtab synchronization process is not running.
NOTE: For rolling upgrade of HP Serviceguard Toolkit for NFS on SLES11 from version A.03.03.01 (or previous version) to current toolkit version, lock_migration.sh script must be available in the newly upgraded node. Before you start the older version of HP Serviceguard Toolkit for NFS on Linux package on the newly upgraded node, you must copy the lock_migration.sh script from non upgraded node to all the other packaged nodes where new version of toolkit is installed.
5 File lock migration HP Serviceguard Toolkit for NFS on Linux provides file lock migration feature for the NFS directories that are exported to the client. You must provide a unique holding directory as part of the NFS package located on a shared file system. This implies that an empty directory is created on a shared filesystem that moves between servers as part of the package failover. The NFS_FLM_HOLDING_DIR parameter in the hanfs.
6 Troubleshooting This section explains some of the problem scenarios that you might encounter while working with the HP Serviceguard Toolkit for NFS on Linux in a Serviceguard cluster. Problem scenario Possible cause Recommended action The package log contains the following message: The parameter LOCK_MIGRATION is not set. NFS client locks will not be migrated. Lock migration feature is not enabled for the NFS package.
Problem scenario Possible cause Recommended action up any rpc.idmapd process. The /var/log/syslog log file indicates /var/lib/nfs/rpc_pipefs directory is not found. to start. When all the required NFS command rpc.idmapd as root. For RPM's are installed on the system, this example: #rpc.idmapd directory must be created. If for some reason this directory is not created, the rpc.idmapd does not start.
7 Support and other resources Information to collect before contacting HP Ensure that the following information is available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact HP Un
Ctrl+x or Ctrl-x A key sequence that indicates you must hold down the keyboard key labeled Ctrl while you press the letter x. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. Key The name of a keyboard key. Return and Enter both refer to the same key. Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown.
A Sample configuration file for modular style of packaging package_name package_description package_type node_name auto_run node_fail_fast_enabled run_script_timeout halt_script_timeout successor_halt_timeout script_log_file failover_policy failback_policy tkit/nfs/nfs/XFS tkit/nfs/nfs/QUOTA_MON tkit/nfs/nfs/LOCK_MIGRATION tkit/nfs/nfs/NFS_FLM_HOLDING_DIR tkit/nfs/nfs/PROPAGATE_INTERVAL tkit/nfs/nfs/NFS_FLM_MONITOR tkit/nfs/nfs/NFS_FLM_RESTART tkit/nfs/nfs/MONITOR_INTERVAL tkit/nfs/nfs/RETRY_INTERVAL tkit/n
Glossary $SGCONF /usr/local/cmcluster/conf for RHEL. /opt/cmcluster/conf for SLES11. $SGROOT /usr/local/cmcluster for RHEL. /opt/cmcluster for SLES11. ADF Attribute definition file. ASCII American Standard Code for Information Interchange. NFS Network File System. NFSv4 way of exporting The directory on the file system is bounded with the virtual route directory and it will be exported. Package A grouping of application services (individual Linux processes) under Serviceguard .
Index C Cluster verification of NFS Toolkit, 14 D Deploying NFS toolkit packages, 11 Configuring a modular NFS package, 11 F File lock migration, 21 I Installation uninstallation, 9 M Managing the NFS toolkit package, 13 Maintaining the package, 14 Mounting NFS shares at client node, 19 Starting the package, 13 Stopping the package, 14 N NFS Toolkit Advantages, 4 Dependecies, 4 Overview, 4 Prerequisites, 4 NFS toolkit troubleshooting, 22 NFS toolkit after Installation files and directories, 9 S Storag
