Managing Serviceguard NFS for Linux, March 2009

vg vg02
17. Create a separate fs_name, fs_directory, fs_type, and fs_mount_opt variable for
each volume group and file system that will be mounted on the server. For example:
fs_name /dev/vg01/lvol1
fs_directory /ha_root
fs_type "ext3"
fs_mount_opt "-o rw"
fs_umount_opt ""
fs_fsck_opt ""
fs_name /dev/vg01/lvol2
fs_directory /users/scaf/ha_data
fs_type "reiserfsext3"
fs_mount_opt "-o rw"
fs_umount_opt ""
fs_fsck_opt ""
fs_name /dev/vg02/lvol1
fs_directory /ha_data
fs_type "ext3"
fs_mount_opt "-o ro"
fs_umount_opt ""
fs_fsck_opt ""
This example defines the variable for three NFS mounted file systems, ha_root, /users/scaf
and ha_data.
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/pkg01/pkg01.conf
2. Use your favorite copy utility (for example, scp) to copy the package control, NFS control,
and monitor scripts to the same path names on all the nodes in the cluster. For example, to
copy the files from host thyme to host basil, issue the following command from host
thyme:
# scp /usr/local/cmcluster/cluster/pkg01/* \
basil:/usr/local/cmcluster/cluster/pkg01
Housekeeping Suggestions
After the shell scripts are installed they are located in /usr/local/cmcluster/nfstoolkit
and the binary file is located in /usr/bin on your Linux platforms. It is recommended that you
set up directories to keep your various package and script files grouped for organization. Set up
one directory for each package and keep the associated control and monitoring scripts in that
directory.
Configuring a Modular Serviceguard NFS Package 31