Installing Serviceguard NFS for Linux

The following descibes the Serviceguard NFS for Linux installation process.




	NOTE: The following procedures assume you are working in a RedHat environment. If your environment is SLES, replace all occurrences of `/usr/local` with `/opt`.

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.
Erase older versions of the NFS Toolkit, if needed:
# rpm -e nfstoolkit<release_version>
Use the Redhat and SuSE Package Management rpm command to install the Serviceguard NFS file set. Change to your RPM file directory, then issue the following commands:
RedHat:
Proliant Servers:
# rpm -i nfs-toolkit-A.01.04-0.product.redhat.i386.rpm
Integrity Servers:
# rpm -i nfs-toolkit-A.01.04-0.product.redhat.ia64.rpm
SUSE LINUX Enterprise Server:
Proliant Servers:
# rpm -i nfs-toolkit-A.01.04-0.product.suse.i386.rpm
Integrity Servers:
# rpm -i nfs-toolkit-A.01.04-0.product.suse.ia64.rpm
The files will be installed in the /usr/local/cmcluster/nfstoolkit and /usr/bin directories. The following files are part of the toolkit:
NOTE: The following procedures assume your environment is RedHat. If your environment is SLES, replace all occurences of “/usr/local” with “/opt”.
- /usr/local/cmcluster/nfstoolkit/README. Description of the toolkit contents.
- /usr/local/cmcluster/nfstoolkit/hanfs.conf. The NFS configuration file which allows the option to monitor the quotad daemon. If QUOTA_MON is set to YES, the toolkit will start rpc.quotad (if not already running) and will monitor this daemon. If it is set to NO, the toolkit will not start or monitor rpc.quotad. The default value for the QUOTA_MON variable is YES.
- /usr/local/cmcluster/nfstoolkit/hanfs.sh. The NFS control script template that starts and stops NFS daemons and exports and unexports file systems.
- /usr/local/cmcluster/nfstoolkit/nfs.mon. The NFS monitor script.
- /usr/bin/sync_rmtab. Remote mount table synchronization binary code.
- /usr/local/cmcluster/nfstoolkit/toolkit.sh. The interface script between the package control script and hanfs.sh.
Run cmmakepkg command to generate a package co nfiguration file and package control script template to the /usr/local/cmcluster/nfstoolkit directory with the following command:
# cd /usr/local/cmcluster/nfstoolkit
# cmmakepkg -p pkg.conf
# cmmakepkg -s pkg.cntl
Create a directory for your package files, for example:
# mkdir /usr/local/cmcluster/<pkg_name>
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/<pkg_name>

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. Though, it is recommended that you keep your template file in its original form for future use. If you will run multiple Serviceguard NFS packages, each package must have its own package directory, package configuration file and control scripts.

For each Serviceguard NFS package you plan to run, make a copy of all the package files including the package configuration file (pkg.conf), package control script (pkg.cntl), toolkit interface script (toolkit.sh), NFS Control Script (hanfs.sh), NFS configuration file (hanfs.conf), and NFS monitor script (nfs.mon). You can rename the package control script with a package specific identification, such as pkg1.conf and pkg1.cntl.




	NOTE: `pkg.cntl`, `toolkit.sh` , `hanfs.conf, nfs.mon`, and `hanfs.sh` should be in the same directory. Do not rename `hanfs.conf, hanfs.sh,` `toolkit.sh`, and `nfs.mon`. These files are hard coded in the control scripts.

Installing Serviceguard NFS for Linux

Technical documentation

» Table of Contents

» Index

Copying the Template Files