Figure 14. NFS Cross Mounts

When Node A fails, Node B uses the cl_nfskill utility to close open files in Node A:/afs, unmounts it, mounts it locally, and re-exports it to waiting clients.

After takeover, Node B has:

/bfs locally mounted /bfs nfs-exported /afs locally mounted /afs nfs-exported

Ensure that the shared volume groups have the same major number on the server nodes. This allows the clients to re-establish the NFS-mount transparently after the takeover.

Caveats about Node Names and NFS

In the configuration described above, the node name is used as the NFS hostname for the mount. This can fail if the node name is not a legitimate TCP/IP adapter label.

To avoid this problem do one of the following:

Cluster Customization 127

Page 145
Image 145
IBM SG24-5131-00 manual Caveats about Node Names and NFS, NFS Cross Mounts