Managing NFS and KRPC Kernel Configurations in HP-UX 11i v2 (Oct 2008)

2.3 KRPC Client Tunables
Table 2.3-1 lists the KRPC client tunables. The last column specifies which NFS patch first introduced
the tunable.
Table 2.3-1 KRPC Client Tunables
Kctune Tunable Name Range Default Value Units Patch ID
rpc_clnt_idle_timeout
0 to 2
31
-1
300000 Milliseconds PHNE_33981
rpc_clnt_max_conns
1 to 2
31
-1
1 Connections PHNE_33981
2.3.1 rpc_clnt_idle_timeout
Description
The rpc_clnt_idle_timeout tunable controls the time interval, in milliseconds, that a TCP connection
between the server and client can remain idle before it is forcibly closed by the client system.
Tested Values
Default: 300000 (5 minutes)
Min: 1000 (1 second)
Max: 600000 (10 minutes)
Note: If the tunable is set to a value less than 1000
milliseconds or greater than 600000 milliseconds, an
informational warning is issued at runtime. These values are
outside the tested limits.
Restrictions on Changing
The rpc_clnt_idle_timeout tunable is dynamic. System reboot is not required to activate changes made
to this tunable. Changes made to this tunable are applicable only for TCP connections that are
created after the value of the tunable is modified.
Modifying the Value
If you prefer to have idle TCP connections cleaned up in less than 5 minutes, decrease the value. If
you prefer that idle TCP connections remain available for longer than 5 minutes, increase the value.
However, this tunable only controls the client behavior.
To change the server-side behavior with respect to idle TCP connections, modify the
rpc_svc_idle_timeout parameter. For more information, see rpc_svc_idle_timeout
.
2.3.2 rpc_clnt_max_conns
Description
The rpc_clnt_max_conns tunable controls the number of TCP connections between NFS clients and
NFS servers. By default, the NFS client opens a single TCP connection to each server it mounts
filesystems from, regardless of the number of filesystems mounted from the server. The client
multiplexes all of the requests for these filesystems across the single connection. In most situations, this
single connection paradigm works well. However, in certain cases, the client can perform better if
26