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
Managing Serviceguard NFS for Linux > Chapter 2 Installing and Configuring Serviceguard NFS for Linux

Installing Serviceguard NFS for Linux

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

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.

    Remove older versions of the NFS Toolkit, if needed:

    # rpm -e nfstoolkit<release_version>

  2. 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 (running the 32 bit version of the distribution):

    # rpm -i nfs-toolkit-A.02.00-0.product.redhat.i386.rpm

    Proliant Servers (running the x86_64 bit version of the distribution):

    # rpm -i nfs-toolkit-A.02.00-0.product.redhat.x86_64.rpm

    Integrity Servers:

    # rpm -i nfs-toolkit-A.02.00-0.product.redhat.ia64.rpm

    SUSE LINUX Enterprise Server:

    Proliant Servers (running the 32 bit version of the distribution):

    # rpm -i nfs-toolkit-A.02.00-0.product.suse.i386.rpm

    Proliant Servers (running the x86_64 bit version of the distribution):

    # rpm -i nfs-toolkit-A.02.00-0.product.suse.x86_64.rpm

    Integrity Servers:

    # rpm -i nfs-toolkit-A.02.00-0.product.suse.ia64.rpm

    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. Description of the toolkit contents.

    • /usr/local/cmcluster/nfstoolkit/hanfs.conf. The NFS configuration file to set user configuration parameters.

    • /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/local/cmcluster/nfstoolkit/nfs.flm. The NFS File Lock Migration synchronization 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.

  3. Run cmmakepkg command to generate a package configuration 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

  4. Create a directory for your package files, for example:

    # mkdir /usr/local/cmcluster/<pkg_name>

  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/<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), NFS monitor script (nfs.mon) and NFS file lock migration synchronization script (nfs.flm). 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, nfs.flm, and hanfs.sh should be in the same directory. Do not rename hanfs.conf, hanfs.sh, toolkit.sh, nfs.flm, and nfs.mon. These files are hard coded in the control scripts.
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.