There are always 2 parts to an NFS share: the client and the server. For shares that have been working in the past, the remote server and the path between is usually the problem. To see that if rpcbind is running and NFS transactions are getting through the network, use:
rpcinfo -p
You should see something like:
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100024 1 udp 49153 status
100024 1 tcp 49152 status
100133 1 udp 49153
100133 1 tcp 49152
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
1073741824 1 tcp 49153
100005 1 udp 49194 mountd
100005 1 tcp 49342 mountd
100005 2 udp 49194 mountd
100005 2 tcp 49342 mountd
100005 3 udp 49194 mountd
100005 3 tcp 49342 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 2 udp 2049
100227 3 udp 2049
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 2 tcp 2049
100227 3 tcp 2049
If a timeout error occurs, rpcbind is not running on this client, or some network filter such as IPFilter is blocking port 111 traffic.
Then, to check a remote server:
rpcinfo -p yoda
where yoda is the name of the remote NFS server:
# rpcinfo -p yoda
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100005 1 udp 49162 mountd
100005 3 udp 49162 mountd
100005 1 tcp 49295 mountd
100005 3 tcp 49295 mountd
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100024 1 tcp 49296 status
100024 1 udp 49163 status
100021 1 tcp 49300 nlockmgr
100021 1 udp 49164 nlockmgr
100021 3 tcp 49301 nlockmgr
100021 3 udp 49165 nlockmgr
100021 4 tcp 49302 nlockmgr
100021 4 udp 49166 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 49303 nlockmgr
Without a similar response (ie, a timeout), the client cannot communicate with the server’s rpcinfo process. rpcinfo uses port 111 and knows about the other rpc services such as rpc.lockd, rpc.statd and rpc.mountd. These services are required on the server for NFS to function. A timeout usually means that the port is blocked, whereas rpcinfo: can’t contact portmapper usually means that the service(s) are not running on the server. The error: rpcinfo: atldhcp3: n2a: hostname not found means that the hostname (or IP-addr) is invalid.
– See more at: http://serviceitdirect.com/blog/troubleshooting-failed-nfs#sthash.TYdLDxr5.dpuf
Tags: HP-UX