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.conf
  Defines the cluster nodes, shared networks, and max # of packages.
Files that apply to each NFS package (<pkg>):
- Package configuration file, <pkg>.conf
  The master package configuration file. It defines the package’s nodes and failover behavior, and points to the package’s control script, pkg.cntl.
- Package control script, <pkg>.cntl
  This defines the start and stop behavior, especially the activation and de-activation of the HA storage, and calls the toolkit.sh file. Applies only to Legacy packages.
- Toolkit configuration script, hanfs.conf
- NFS control script, hanfs.sh
  This exports the HA file system managed by this package. If specified, it also starts monitoring the NFS services.
- <pkg.cntl>.log and hanfs.sh.log files
  These are generated automatically.
- NFS monitoring script, nfs.mon
- NFS file lock migration script, nfs.flm
- Toolkit interface script, toolkit.sh
  This script is invoked by <pkg>.cntl which invokes the hanfs.sh.
- Lock migration script lock_migration.sh
  This script starts lock migration process in Modular packages
- Toolkit module script tkit_module.sh
  Script used in Modular packages to invoke toolkit.sh
- Toolkit configuration generation script. tkit_gen.sh
  The script which generates toolkit configuration file on cmapplyconf
- Attribute Definition File (ADF) nfs.1 and it’s softlink named nfs
  This file is used to generate package configuration file by Serviceguard.

Understanding the Serviceguard NFS Files

Technical documentation

» Table of Contents

» Index