Table of Contents
Advertisement
v "Mounting a volume from an AIX client" on page 136
v "Displaying remotely mounted filesystems" on page 136
v "Starting PC NFS" on page 136
v "Stopping PC NFS" on page 137
Starting Network File System
NFS is started during the NAS Gateway 500 boot process. Therefore, you only
need to issue the Start NFS command if the Stop NFS command has been
previously issued. In a clustered environment, issue the Start NFS command on the
same node from which the Stop NFS command was issued.
NFS serves files as defined by the administrator (refer to the mknasnfsexp,
lsnasnfsexp, rmnasnfsexp, or chnasnfsexp commands in the IBM TotalStorage
NAS Gateway 500 Command Reference).
To start NFS:
1. SMIT menu fastpath: smit nfs
2. Select Start NFS.
Select one of the following options.
both
now
restart
Stopping Network File System
To stop serving all NFS files:
1. Go to the SMIT menu fastpath: smit nfs
2. Select Stop NFS
Select one of the following options.
both
now
restart
Changing Network File System characteristics
You can change the number of NFS daemons that run on the system using the
chnfs command.
CLI command
Use the chnfs command.
In most situations the default values are appropriate. In configurations with very
heavy NFS loads, performance gains may be seen by increasing the number of
NFS daemons.
This is the most common selection. It starts the NFS server
immediately and every time the system reboots.
Starts the NFS server immediately, but does not start the NFS
server after reboot.
Starts the NFS server only after the system has been rebooted.
This is the most common selection. It stops the NFS server
immediately and does not start the NFS server after the system
reboots.
Stops the NFS server immediately. The system can be configured
during setup to restart the NFS server automatically after the now
command completes.
Restarts the NFS server only after the system has been rebooted.
Chapter 25. Managing file serving
131
Advertisement
Table of Contents
