NFS Services Administrator Guide for 11i v3 (5900-2572, September 2012)

• “Unmounting (Removing) a Mounted Directory” (page 39) (Optional)
• “Disabling NFS Client Capability” (page 39) (Optional)
Configuring the NFSv4 Client Protocol Version
IMPORTANT: The nfsmapid daemon must be running on both the NFS server and the client to
use NFSv4. For more information on how to configure the NFSv4 server protocol version, see
“Configuring the NFSv4 Server Protocol Version ” (page 20).
By default, the version of the NFS protocol used between the client and the server is the highest
one available on both systems. On HP-UX 11i v3, the default maximum protocol version of the
NFS server and client is 3. The default minimum protocol version of the NFS server and client is
2.
To configure the NFS client to enable it to mount filesystems using protocol version 4 (NFSv4),
follow this step:
Set the value of the NFS_CLIENT_VERSMAX variable to 4 in the /etc/default/nfs file, as
follows:
NFS_CLIENT_VERSMAX = 4
The NFS_CLIENT_VERSMAX variable specifies the maximum version of the NFS protocol for
communication.
You can also configure the client protocol version to NFSv4 by specifying vers=4 while mounting
the directory. For example, to set the client protocol version to NFSv4 while mounting the /usr/
kc directory, enter the following command:
mount -o vers=4 serv:/usr/kc /usr/kc
For more information on NFSv4, see nfsd(1m), mount_nfs(1m), nfsmapid(1m), and nfs4cbd(1m).
Deciding Between Standard-Mounted Directories and Automounted Directories
Before you mount any remote directories on a local system, decide whether you want each directory
to be standard-mounted or automounted. You can automount directories using AutoFS. For more
information on AutoFS, see Chapter 3: “Configuring and Administering AutoFS” (page 47).
Table 8 lists the differences between the Standard-Mounted and the Automounted directories.
Table 8 Standard-Mounted Versus Automounted Directories
Automounted Directory (Using AutoFS)Standard-Mounted Directory
Automounted directories stay mounted until they are left idle for
10 minutes. The 10 minute time interval is the default value and
is configurable.
The directory stays mounted. You do not have to wait
for it to be mounted after you issue a read or write
request.
A directory automounted with AutoFS is not mounted until a
user or a process requests access to it. As a result, both your
If a directory is configured to be standard-mounted
when your system boots, and the NFS server for the
system and the NFS server are able to complete the boot process
before attempting to mount the directory.
directory is not booted yet, system startup is delayed
until the NFS server becomes available. If your system
and the server are configured to mount directories
from each other at boot time, standard mounts can
cause both systems to hang indefinitely.
You can manage AutoFS configuration files (maps) centrally
through NIS and LDAP.
You must maintain the configuration file for standard
mounts (/etc/fstab) separately on each NFS client.
AutoFS allows you to use wildcard characters and environment
variables in configuration files (maps) as shortcuts, when you
are configuring many similar automounts.
If you have to configure many similar standard mounts,
you must configure them individually, because you
cannot use wildcard characters or environment
variables when you configure standard NFS mounts.
AutoFS allows you to configure a special “built-in” map known
as the -hosts map. This built-in map automounts all the
Standard NFS mounts provide no shortcut for
configuring all available remote directories. You must
34 Configuring and Administering NFS Services