Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Serviceguard NFS Toolkit for Linux Version A.01.04 Release Notes > Chapter 1 Serviceguard NFS for Linux Version A.01.04 Release Notes

Compatibility Information and Installation Requirements

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

In addition to the instructions provided below, see Managing Serviceguard NFS on Linux for more detailed installing and configuring instructions.

IMPORTANT: You cannot use Serviceguard NFS Toolkit without NFS Services. The NFS server programs must be installed on your Linux sytem before you install, configure, and test your NFS package. (When installing the Linux distribution, you select the “NFS Server” option. The installation program will install both NFS kernel and utility.)

Installing Serviceguard NFS for Linux

  1. Before you start, use the following steps to remove any previous version of Serviceguard NFS for Linux:

    To query the NFS Toolkit from the rpm database use:

    # rpm -qa |grep nfstoolkit

    If any part of the NFS Toolkit is installed, erase it using:

    # rpm -e nfstoolkit-<release>

  2. To install the NFS Toolkit use 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

    The files will be installed in the /usr/local/cmcluster/nfstoolkit and /usr/lib directories.

    SLES Distributions:

    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 /opt/cmcluster/nfstoolkit and /usr/lib directories.

    The following files are part of the toolkit:

    • README. Description of the toolkit contents.

    • hanfs.sh. The NFS control script template that starts and stops NFS daemons and exports and unexports file systems.

    • nfs.mon. The NFS monitor script.

    • /usr/bin/sync_rmtab. Remote mount table synchronization binary code.

    • toolkit.sh: The interface script between the Package Control Script and hanfs.sh.

    • hanfs.conf: The nfs configuration file that specifies whether to monitor quotad daemon.

    NOTE: In the following steps, <dir> refers to the directory /usr/local for RedHat environments, and /opt for SLES environments.
  3. Run cmmakepkg command to generate a package configuration file and package control script template to the <dir>/cmcluster/nfstoolkit directory with the following :

    # cd <dir>/cmcluster/nfstoolkit

    # cmmakepkg -p pkg.conf

    # cmmakepkg -s pkg.cntl

  4. Create a directory for your package files called <dir>/cmcluster/<pkg_name>

  5. Issue the following command to copy the Serviceguard NFS template files to the newly created package directory:

    # cp <dir>/cmcluster/nfstoolkit/* \

       <dir>/cmcluster/<pkg_name>

Copying the Template Files

If you run only one Serviceguard NFS package in your Serviceguard cluster, you do not have to copy the template files. However, 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 run, make a copy of all the package files including package configuration file (pkg.conf), package control script (pkg.cntl), interface script (toolkit.sh), NFS Control Script (hanfs.sh), NFS configuration file (hanfs.conf) and NFS monitor script (nfs.mon). Use package specific file names for the scripts, such as pkg1.conf and pkg1.cntl.

NOTE: pkg.cntl, toolkit.sh, hanfs.sh, nfs.mon, and hanfs.conf should be in the same directory. Do not rename the toolkit.sh, hanfs.sh hanfs.conf and nfs.mon. These files are hard coded in the two control scripts.
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.