Network and Storage Protocols
I am getting the following message in the messages file on one filer every hour:
"Network lock manager version 4 (for UDP) not registered with portmapper daemon on the client <client ip>"
There doesn't seem to be any issue with the client using the volumes it has mounted, so this doesn't seem to be a serious issue, however, I would like to stop it spamming the messages file.
I've tried restarting the lock manager service on the client as well as port mapper (rpcbind) and even gave it a reboot. But the error message is still being generated.
NFSv4 is enabled on the filer, but the client is mounting using NFSv3.
It looks like the process has registered ok from the cilent side:
rpcinfo -pprogram vers proto port service100000 4 tcp 111 portmapper100000 3 tcp 111 portmapper100000 2 tcp 111 portmapper100000 4 udp 111 portmapper100000 3 udp 111 portmapper100000 2 udp 111 portmapper100024 1 udp 25086 status100024 1 tcp 35999 status100021 1 udp 51494 nlockmgr100021 3 udp 51494 nlockmgr100021 4 udp 51494 nlockmgr100021 1 tcp 52961 nlockmgr100021 3 tcp 52961 nlockmgr100021 4 tcp 52961 nlockmgr
Anyone seen this before? Any suggestions? Thanks!
I am getting the following messages in the messages file on one filer every hour:
Network lock manager version 4 (for UDP) not registered with portmapper daemon on the client <client ip>
There doesn't seem to be any issues with the client using the volume it has mounted, so this doesn't seem to be a serious issue, however, I would like to stop it spamming the messgaes file.
How to check the same from Filer end. Pls. help.
Is there any command to check?
NetApp Release 8.1.3P3 7-Mode is the version.
NetApp Wins One Silver and One Bronze Stevie® Award in 2022 Stevie Awards for Sales and Customer Service
Live Chat, Watch Parties, and More!
Engage digitally throughout the sales process, from product discovery to conﬁguration, and handle all your post-purchase needs.