Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • Does the SMB3 witness protocol provide automatic session revert feature?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Does_the_SMB3_witness_protocol_provide_automatic_session_revert_feature
      Applies to ONTAP 9 SMB3 Continuous Availability(CA) SMB Witness Indirect I/O Answer There is no such concept Additional Information What are SMB Continuous Availability (CA) Shares SMB Witness Trouble...Applies to ONTAP 9 SMB3 Continuous Availability(CA) SMB Witness Indirect I/O Answer There is no such concept Additional Information What are SMB Continuous Availability (CA) Shares SMB Witness Troubleshooting Workflow
    • Can Continuous Availability be enabled on CIFS shares in System Manager
      https://kb.netapp.com/on-prem/ontap/DM/System_Manager/SM-KBs/Can_Continuous_Availability_be_enabled_on_CIFS_shares_in_System_Manager
      Applies to ONTAP System Manager (OSM) CIFS Hyper-V MSSQL Answer Continuous Availability (CA) can be enabled on CIFS shares in OSM, starting in ONTAP 9.10.1 In earlier ONTAP releases, CA can be enabled...Applies to ONTAP System Manager (OSM) CIFS Hyper-V MSSQL Answer Continuous Availability (CA) can be enabled on CIFS shares in OSM, starting in ONTAP 9.10.1 In earlier ONTAP releases, CA can be enabled using cli command cifs share properties add -vserver SVM -share-name SHARE -share-properties continuously-available Additional Information What are SMB Continuously Available (CA) Shares
    • Windows SMB client takes long to report that cifs share does not exist
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Windows_SMB_client_takes_long_to_report_that_cifs_share_does_not_exist
      Applies to Windows SMB client ONTAP 9 CIFS Continuous Availability (CA) Issue Windows client connects to share, but the share does not exist (or does not exist anymore) Message reported: System error ...Applies to Windows SMB client ONTAP 9 CIFS Continuous Availability (CA) Issue Windows client connects to share, but the share does not exist (or does not exist anymore) Message reported: System error 53 has occured. The network path was not found. It takes around 30 seconds before the error message is reported When the Windows client has a(nother) share already connected to the same cifs server, the response is immediate