Managing Serviceguard NFS for Linux, March 2009

Extended Distance Cluster which uses the linux software RAID as the basic building block.
For information on setting up the Extended Distance Cluster, see the HP Serviceguard
Extended Distance Cluster for Linux Deployment Guide.
4. Create a directory for each NFS package. For example:
/usr/local/cmcluster/nfs1
5. The names of the volume groups must be unique within the cluster, and the major and minor
numbers associated with the volume groups must be the same on all nodes. In addition, the
mounting points and exported file system names must be the same on all nodes.
The preceding requirements exist because NFS uses the major number, minor number, inode
number, and exported directory as part of a file handle to uniquely identify each NFS file.
If differences exist between the primary and adoptive nodes, the client’s file handle would
no longer point to the correct file location after movement of the package to a different node.
6. Use LVM commands to set up volume groups, logical volumes, and file systems as needed
for the data that will be exported to clients. Refer to the Managing HP Serviceguard for Linux
manual.
7. Make sure the user IDs and group IDs of those who access the Serviceguard NFS file system
are the same on all nodes that can run the package.
Make sure the user IDs and group IDs in the /etc/passwd and /etc/group files are the
same on the primary node and all adoptive nodes, or use NIS to manage the passwd and
group databases.
8. Create an entry for the name of the package in the DNS or NIS name resolution files, or in
/etc/hosts, so that users will mount the exported file systems from the correct node. This
entry maps the package name to the package’s relocatable IP address.
9. Decide whether to place executables locally on each client or on the NFS server. There are
a number of trade-offs to be aware of regarding the location of executables with Serviceguard
NFS.
The advantages of keeping executables local to each client are as follows:
• No failover time. If the executables are local to the client, there is no delay if the NFS
server fails.
• Faster access to the executables than accessing them through the network.
The advantage of putting the executables on the NFS server is as follows:
• Ease of management. If the executables are located in one centralized location, the
administrator must update only one copy when changes are made.
Configuring a Legacy Serviceguard NFS Package
To configure a Legacy Serviceguard NFS package, complete the following tasks, described in
this section:
• “Editing the Package Configuration File (pkg.conf)”
• “Editing the Package Control Scripts (pkg.cntl)”
• Editing the NFS Configuration File (hanfs.conf)
• “Creating the Serviceguard Binary Configuration File”
NOTE: Repeat the configuration process for each NFS package.
Editing the Package Configuration File (pkg.conf)
The following steps describe the required modifications to the Package Configuration File. Make
one Package Configuration file for each package.
22 Installing and Configuring Serviceguard NFS for Linux