HP-UX System Administrator's Guide: Routine Management Tasks

server, try starting more nfsds; see “Increasing the Number of nfsd Daemons”
(page 197).
Checking for Network Overload with netstat -i
If you have followed all the “Guidelines” (page 192) and are still seeing poor response
time, the problem may be with the network itself - either with a particular piece of
hardware or with the configuration of the network.
To see cumulative statistics on a server, run
netstat -i
If your system has been running for a long time, the numbers will be large and may
not reliably reflect the present state of things. You can run netstat iteratively; for
example
netstat -I lan0 -i 5
In this case (after the first line), netstat reports activity every five seconds.
Input and output errors should be very low in relation to input and output packets -
much less than 1%. A higher rate of output errors on only one server may indicate a
hardware problem affecting the server’s connection to the network.
Collisions (colls) should be less than 5%; a higher rate indicates heavy network use
which your users are probably experiencing as poor performance. Network traffic and
configuration may be beyond your control, but you can at least raise a flag with your
network administrator.
Making Changes
• “Increasing the Number of nfsd Daemons” (page 197)
• “Defragmenting an HFS File System” (page 198)
• “Defragmenting a JFS File System” (page 199)
• “Configurable Kernel Parameters” (page 199)
Increasing the Number of nfsd Daemons
To increase the number of nfsds running on a server, do the following steps:
1. Edit /etc/rc.config.d/nfsconf, raising the value of NUM_NFSD; for example:
NUM_NFSD=8
2. Stop and restart the nfs.server script:
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.server start
Making Changes 197