Skip to main content
NetApp Knowledge Base

Hyper-V environment loses access to volumes after cluster switch restart

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

Applies to

  • ONTAP 9
  • Hyper-V

Issue

  • After restarting one side of the Cluster Switch, the Hyper-V environment loses access to volumes.
  • Other environments, such as vSphere and user PCs, do not encounter this issue.
  • The Hyper-V environment uses SMB3 Continuous Availability (CA) shares.
  • Observations include:
    • Hyper-V connections show increased IdleTime in `cifs session show`.
    • IdleTime exceeds 10 minutes and continues to increase until the Hyper-V servers are restarted.
    • CIFS session from Hyper-V shows increased idle time and does not reconnect automatically until Hyper-V is rebooted.
  • Log Output:

Thu Mar 13 13:39:49+0900 [XXX:kernel:csm.createSessionFailed:debug]: ClusterSessionManager(CSM) failed to create session with transport type CT, session tag DEFAULT, record state ACTIVE, CSM error CSM_CONNABORTED, low-level error, socket error 0, and TLS error 0.
Thu Mar 13 13:39:49+0900 [XXX:wafl_exempt15:lmgr.session.failed:info]: Dropped session-scoped locks from session due to failed session.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.