Managing Serviceguard NFS for Linux, September 2006

Installing and Configuring Serviceguard NFS for Linux
Configuring a Serviceguard NFS Package
Chapter 2 31
happens if the server is an adoptive node for a file system, and the
file system is available on the server only after failover of the
primary node.
2. If you want to run the NFS monitor script:
• Set the NFS_SERVICE_NAME variable to the value of the
SERVICE_NAME variable in the package configuration file. Each
package must have a unique service name. For example:
NFS_SERVICE_NAME[0]=nfs1.monitor
• Set the NFS_SERVICE_CMD variable to the full path name of the
NFS monitor script. For example:
NFS_SERVICE_CMD[0]=/usr/local/cmcluster/pkg1/nfs.\
mon
Multiple instances of the monitor script can run on the same
node without any problems, and if a package fails over, only the
instance associated with that package is killed.
3. If you do not want to run the NFS monitor script:
Comment out the NFS_SERVICE_NAME and NFS_SERVICE_CMD
variables. For example:
# NFS_SERVICE_NAME[0]=nfs1.monitor
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables
are commented out, and the NFS monitor script is not run.
Creating the Serviceguard Binary Configuration File
1. Use the cmapplyconf command to verify the content of your cluster
and package configuration and to copy the binary configuration file
to all the nodes in the cluster. In the following example, the cluster
configuration file is /usr/local/cmcluster/cluster.conf. On
your system, use the names of your own cluster configuration and
package configuration files.
# cmapplyconf -v -C /usr/local/cmcluster/cluster.conf \
-P /usr/local/cmcluster/pkg1/pkg1.conf