Skip to main content
NetApp Knowledge Base

SnapMirror to CVO is failing with network error CSM: Operation referred to a non-existent session

Views:
58
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • Cloud Volumes ONTAP (CVO)
  • AWS ST1 disks

Issue

  • SnapMirror initialization failed continuously at 49.3 of 50 TB complete with network error
  • Aborted transfer and re-initalized resulted with same error
  • The following errors are observed in snapmirror-error-log.txt:
Tue May  9 20:32:59 UTC 2023 Initialize[Apr 24 20:48:35]:60f3d91a-e2e1-11ed-963a-43d646b09c04 Operation-Uuid=61ff896d-e2e1-11ed-963a-43d646b09c04 Group=none Operation-Cookie=0 action=Defer source=vserver:volume destination=svm:destination status=Failure message=Transfer failed. (Replication operation request failed from Cluster Id: source_cluster Node Id: node # to Cluster Id: dest_cluster Node Id: node # due to a network error(CSM: Operation referred to a non-existent session.)

af1r00napcvoh01::*> event show -event device*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
5/11/2023 22:18:06  cluster-01
                                     NOTICE        device.latency.threshold: The device latency in microseconds exceeded the threshold value for device "nvd#" and the associated target device "n/a". The threshold is "25000", execution latency is "57914", total latency is "57951", and the number of operations for this period is "16257".
5/11/2023 22:06:03  cluster-01
                                     NOTICE        device.latency.threshold: The device latency in microseconds exceeded the threshold value for device "is#" and the associated target device "/dev/nvd#". The threshold is "25000", execution latency is "71475", total latency is "71492", and the number of operations for this period is "469".
5/11/2023 22:03:04  cluster-01
                                     NOTICE        device.latency.threshold: The device latency in microseconds exceeded the threshold value for device "nv#5" and the associated target device "n/a". The threshold is "25000", execution latency is "57305", total latency is "57393", and the number of operations for this period is "16129".
5/11/2023 21:51:02  cluster-01
                                     NOTICE        device.latency.threshold: The device latency in microseconds exceeded the threshold value for device "is#" and the associated target device "/dev/nvd##". The threshold is "25000", execution latency is "80184", total latency is "80200", and the number of operations for this period is "344".

 

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.