Information for NFS version 3 and version 4 protocols with
proto=tcp can
be found on the mount man page on a UNIX client.
The NFS client automatically selects the
proto=tcp option,
unless the end-user overrides the option. For example, you can enter
this command:
unix$ mount -o vers=2,proto=udp mvshost1:smith /mnt
This
example shows a specification of NFS version 2 with
udp protocol,
even though the client platform can handle the NFS version 4 and
tcp protocol.
Users can issue the
rpcinfo -p <hostname> to
show all the RPC programs available on the server. For example:
$ rpcinfo -p mvshost1
Table 1 shows the information
from this command.
Table 1. View of NFS server
capabilityprogram |
vers |
proto |
port |
service |
---|
100000 |
4 |
tcp |
111 |
portmapper |
100000 |
3 |
tcp |
111 |
portmapper |
100000 |
2 |
tcp |
111 |
portmapper |
100000 |
4 |
udp |
111 |
portmapper |
100000 |
3 |
udp |
111 |
portmapper |
100000 |
2 |
udp |
111 |
portmapper |
150001 |
1 |
udp |
4954 |
pcnfsd |
150001 |
2 |
udp |
4954 |
pcnfsd |
100024 |
1 |
udp |
4955 |
status |
100024 |
1 |
tcp |
4944 |
status |
100021 |
1 |
udp |
4956 |
nlockmgr |
100021 |
1 |
tcp |
4945 |
nlockmgr |
100021 |
3 |
tcp |
4945 |
nlockmgr |
100021 |
3 |
udp |
4956 |
nlockmgr |
100021 |
4 |
tcp |
4945 |
nlockmgr |
100021 |
4 |
udp |
4956 |
nlockmgr |
100003 |
2 |
tcp |
2049 |
nfs |
100003 |
2 |
udp |
2049 |
nfs |
100003 |
3 |
tcp |
2049 |
nfs |
100003 |
3 |
udp |
2049 |
nfs |
100003 |
4 |
tcp |
2049 |
nfs |
100059 |
2 |
udp |
4953 |
|
100059 |
2 |
tcp |
4943 |
|
100044 |
1 |
udp |
4952 |
|
100044 |
1 |
tcp |
4942 |
|
100005 |
1 |
udp |
4951 |
mountd |
100005 |
1 |
tcp |
4941 |
mountd |
100005 |
3 |
tcp |
4941 |
mountd |
100005 |
3 |
udp |
4951 |
mountd |
Users can issue rpcinfo -s <hostname> from
Solaris clients to show a concise list of all the RPC programs available
on the server.
Here is an example of output from
rpcinfo -s <hostname> in
an IPv4 environment:
program version(s) netid(s) service owner
100000 4,3,2 udp,tcp rpcbind superuser
150001 2,1 udp pcnfsd unknown
100024 1 tcp,udp status unknown
100021 4,3,1 tcp,udp nlockmgr unknown
100003 4,3,2 udp,tcp nfs unknown
100059 2 tcp,udp showattr unknown
100044 1 tcp,udp mvsmount unknown
100005 3,1 tcp,udp mountd unknown
Here is an example of output from
rpcinfo -s <hostname> in
an IPv4/IPv6 environment:
program version(s) netid(s) service owner
100000 4,3,2 udp,udp6,tcp,tcp6 rpcbind superuser
150001 2,1 udp6,udp pcnfsd unknown
100024 1 tcp6,tcp,udp6,udp status unknown
100021 4,3,1 tcp6,tcp,udp,udp6 nlockmgr unknown
100003 4,3,2 udp6,udp,tcp6,tcp nfs unknown
100059 2 tcp6,tcp,udp6,udp showattr unknown
100044 1 tcp6,tcp,udp6,udp mvsmount unknown
100005 3,1 tcp6,tcp,udp6,udp mountd unknown