NFS Services Administrator Guide (5900-3045, March 2013)

Where:
port_number
The port number on which the daemon runs. It can be set to any unique value between
1024 and 65536 for rpc.statd, rpc.mountd and nsf4cbd daemons.
STATD_PORT
The port on which the rpc.statd daemon runs.
MOUNTD_PORT
The port on which the rpc.mountd daemon runs.
NFS4CBD_PORT
The port on which nfs4cbd callback daemon runs.
2. Activate the changes made to the/etc/default/nfs file by restarting the lock manager
and NFS server daemons as follows:
/sbin/init.d/nfs.server stop
/sbin/init.d/lockmgr stop
/sbin/init.d/nfs.client stop
/sbin/init.d/lockmgr start
/sbin/init.d/nfs.server start
/sbin/init.d/nfs.client start
NOTE: In order to configure a fixed port for nfs4cbd daemon, add
the below entry to /etc/default/nfs file before restarting the NFS
client NFS4CBD_PORT= port_number port_number could be set to any
unique value between 1024 and 65536.
3. Configure the firewall based on the port numbers configured.
Sharing directories across a firewall using the NFSv4 protocol
NFSv4 is a single protocol that handles mounting, and locking operations for NFS clients and
servers. The NFSv4 protocol runs on port 2049, by default.
To override the default port number (2049) for the NFSv4 protocol, modify the port number for
the nfsd entry in the/etc/services file.
Configure the firewall based on the port number set.
Sharing directories across a firewall using the WebNFS Feature
The WebNFS service makes files in a directory available to clients using a public file handle. The
ability to use this predefined file handle reduces network traffic, by avoiding the MOUNT protocol.
How WebNFS works
This section compares the process of communication between an NFS client and an NFS server
across LANs and WANs. Table 5 compares the NFS session across a LAN with a WebNFS session
across a WAN.
Table 5 NFS Session Versus WebNFS Session
How WebNFS works across WANsHow NFS works across LANs
NFS servers register on port 2049. WebNFS clients contact
the WebNFS server on port 2049.
NFS servers must register their port assignments with the
portmapper service that is registered on port 111,
although the NFS server uses 2049 as the destination
port.
A WebNFS client can use the PUBLIC file handle as an initial
file handle, rather than using the MOUNT protocol.
The MOUNT service is not registered on a specific port.
The NFS client must use the portmapper service to
locate the MOUNT port. Once the port is located, the
30 Configuring and Administering NFS Services