Thanks for your time and explanation.
Actually I did used NFSv4 earlier. Do not know I miss something here.
unmounted nfsv3 share on a client.
Just now, I've modified the "/etc/exports" with vers=4 and exported it again on server. Stopped and restarted all the nfs daemons.
restarted nfs daemons on test client machine.
Tried mounting on client,
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
mount: 1831-010 server nfsserver not responding: RPC: 1832-015 Remote system error - A remote host refused an attempted connect operation.
mount: backgrounding
nfserver:/nfsv4share/test
---------- Post updated at 03:28 PM ---------- Previous update was at 02:56 PM ----------
Never mind. Its working now for NFSv3. Actually I restarted only 2 daemons(nfsd, nfsrgyd) on server.
Now I've restarted all the NFS daemons. Good with NFSv3.
I cleaned /etc/rmtab and /etc/xtab.
Now the share is exported with NFSv4 only.
domain has set on NFS server and client.
tried mounting, received below error.
COMMAND STATUS
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
mount: 1831-011 access denied for nfsserver:/admclaim/sandrt
mount: 1831-008 giving up on:
nfsserver:/nfsv4share/test
The file access permissions do not allow the specified action.
Found a IBM link, looking in to it.
IBM How to troubleshoot NFS mounting problems
---------- Post updated at 03:45 PM ---------- Previous update was at 03:28 PM ----------
Tried checking IP and hostname etc as shown in the link. I believe this is something different, that only occurs on NFSv4 ?
Please suggest. Thank you.
---------- Post updated at 05:56 PM ---------- Previous update was at 03:45 PM ----------
I've tried mounting using smitty (just like NFSv3). It did not work.
then I ran below command on client, it worked. As per the Redook, I should be able to use same smitty mount options for NFSv4 as well. Correct me If am wrong.
mount -o vers=4 nfsserver:/nfsshare/test /mnt
How do I verify whether my client is using NFSv4.
because I still see mountd and lockd daemons.
>rpcinfo -p
program vers proto port service
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
200006 1 udp 2049
200006 4 udp 2049
200006 1 tcp 2049
200006 4 tcp 2049
100005 1 tcp 36732 mountd
100005 2 tcp 36732 mountd
100005 3 tcp 36732 mountd
100005 1 udp 61488 mountd
100005 2 udp 61488 mountd
100005 3 udp 61488 mountd
400005 1 udp 61489
100024 1 tcp 36733 status
100024 1 udp 61493 status
100133 1 tcp 36733
100133 1 udp 61493
200001 1 tcp 36733
200001 1 udp 61493
200001 2 tcp 36733
200001 2 udp 61493
100021 1 udp 61571 nlockmgr
100021 2 udp 61571 nlockmgr
100021 3 udp 61571 nlockmgr
100021 4 udp 61571 nlockmgr
100021 1 tcp 36755 nlockmgr
100021 2 tcp 36755 nlockmgr
100021 3 tcp 36755 nlockmgr
100021 4 tcp 36755 nlockmgr
400003 1 udp 62548
Please let me know If there's a way to find out running NFS share version.
Thank you