Skip to main content
NetApp Knowledge Base

What is idle timeout value for CIFS and NFS protocols

  1. Last updated
  2. Save as PDF
Views:
2,715
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • CIFS\SMB
  • NFS

Answer

  • CIFS\SMB Protocol:
    • As a result of the fix for Bug 1274307, ONTAP will force client sessions to idle out after the timeout period once all files are closed
    • The default timeout value is 900 seconds

::*> vserver cifs options show -fields client-session-timeout
vserver client-session-timeout
------------- ----------------------
svm1_ontap912 900
svm2_ontap912 900

  • Use the following command to modify

::*> vserver cifs options modify -vserver SVM -client-session-timeout <time(s)>
Node: Shortening the time-out value may cause the client side to frequently interrupt the session due to time-outs.

  • NFS Protocol:

Default timeout is 360 seconds.

  • To show nfs idle connection timeout configuration:

::*> nfs show -fields idle-connection-timeout,allow-idle-connection
vserver       idle-connection-timeout allow-idle-connection
------------- ----------------------- ---------------------
svm1_ontap912 360                     enabled
svm2_ontap912 360                     enabled

 

Note: Since ONTAP 9.12.1+ the option and field is named -allow-idle-connection-timeout 

 

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.