Table of Contents
Advertisement
Section 6.1:Setting Up an NFS Service
6 Network File Sharing Services
This chapter contains instructions for configuring Red Hat Linux Advanced Server to make network
file sharing services through NFS and Samba highly available.
6.1 Setting Up an NFS Service
A highly available network filesystem (NFS) are one of the key strengths of the clustering infrastruc-
ture. Advantages of clustered NFS services include:
•
Ensures that NFS clients maintain uninterrupted access to key data in the event of server failure.
•
Facilitates planned maintenance by allowing transparent relocation of NFS services to one cluster
member, allowing an administrator to fix or upgrade the other cluster member.
•
Allows setup of an active-active configuration to maximize equipment utilization. More details on
active-active configurations appear later in this chapter.
6.1.1 NFS Server Requirements
In order to create highly available NFS services, there are a few requirements which must be met by
each cluster server. (Note: these requirements do not pertain to NFS client systems.) These require-
ments are as follows:
•
Kernel support for the NFS server must be enabled. NFS can be either configured statically or as
a module. Both NFS V2 and NFS V3 are supported.
•
The kernel support for NFS provided with Red Hat Linux Advanced Server 2.1 incorporates en-
hancements (initially developed by Mission Critical Linux Inc.) which allow for transparent relo-
cation of NFS services. These kernel enhancements prevent NFS clients from receiving Stale file
handle errors after an NFS service has been relocated. If using kernel sources that do not include
these NFS enhancements, then NFS can still be configured and run within the cluster; but warn-
ing messages will appear during service start and stop pointing out the absence of these kernel
enhancements.
•
The NFS daemons must be running on all cluster servers. This is accomplished by enabling the
NFS init.d run level script. For example:
/sbin/chkconfig --level 345 nfs on
•
The RPC portmap daemon must be enabled. For example:
/sbin/chkconfig --level 345 portmap on
103
Advertisement
Table of Contents
