I noticed that when I set the lockd ports to specific port that the statd
port is set to the same port.
Should I also set statd to a specific unique port different from lockd ?
Is there any problem with statd using the same port as lockd ?
Any assistance is greatly appreciated.
My current NFS Server and client:
linux01:/ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 2 udp 2050 mountd
100005 2 tcp 2050 mountd
100005 3 udp 2050 mountd
100005 3 tcp 2050 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 3 udp 2049 nfs_acl
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100024 1 udp 2051 status
100021 1 udp 2051 nlockmgr
100021 3 udp 2051 nlockmgr
100021 4 udp 2051 nlockmgr
100024 1 tcp 2051 status
100021 1 tcp 2051 nlockmgr
100021 3 tcp 2051 nlockmgr
100021 4 tcp 2051 nlockmgr
100005 1 udp 2050 mountd
linux01:/ #
NFS Client:
linux02:~ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 2051 status
100021 1 udp 2051 nlockmgr
100021 3 udp 2051 nlockmgr
100021 4 udp 2051 nlockmgr
100024 1 tcp 2051 status
100021 1 tcp 2051 nlockmgr
100021 3 tcp 2051 nlockmgr
100021 4 tcp 2051 nlockmgr
linux02:~ #
Thanks ...............
Regards,
Terry L. Spaulding
[email protected]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs