Unsolved
39 Posts
0
1387
September 3rd, 2020 00:00
NFS client connection issues
Hi to all:
About a subnet currently we have a smartconnect pool that sometimes the Linux teams report us a resource connection issue. It happen during short time , the nfs clients cannnot connecting but after a short time again they can do it.
We use a pool with round-robin like ip failover policy and dynamic like allocation method. The nfs client side it's a 4 nodes cluster.
The linux teams provide us the mount parammetres from one of the export:
rw,relatime
vers=3
rsize=131072
wsize=524288
namlen=255
hard,proto=tcp
timeo=600
retrans=2
sec=sys
mountaddr=172.31.96.18
mountvers=3
mountport=300
mountproto=udp
local_lock=none
addr=172.31.96.18
Does it exist some optimal configuration for the NFS clients when we are using dynamic allocation?
At DNS level we had seem that works fine because the resource keep mounted and they have their ip address allocated.
Many thanks and regards.
OneFS 8.0.0.7
Isilon NL400



Phil.Lam
3 Apprentice
•
625 Posts
0
September 3rd, 2020 10:00
@InfraMED,
Please create SR to investigate. Is there a certain time when this issue happens?
InfraMED
39 Posts
0
September 4th, 2020 00:00
Hi!
This occurs (not always) each certain time. The last time concurred with a tomcat reboot.
I'll create a SR too.
Phil.Lam
3 Apprentice
•
625 Posts
0
September 18th, 2020 09:00
@InfraMED,
Just curious if you got the issue resolved or not. You should upgrade to OneFS 8.1.2 also since 8.0.0.7 is EOSL.
https://support.emc.com/docu45445_PowerScale-Product-Availability-Guide.pdf page 5
https://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/storage-5/docu45445.pdf page 5
InfraMED
39 Posts
0
October 7th, 2020 01:00
Thanks @PhilLam
I already had in account.
We hope at the end of this year migrate to a new model from Isilon.
Many thanks.