Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent session.)

tduran12165 — Wed, 04 Jun 2025 12:10:15 GMT

All,

Had some sort of network issue recently and rendered a handful of snapmirrors "unhealthy" and not able to successfully replicate. Everything from a cluster peer standpoint looks ok, pings are successful between nodes, and no issue with authentication. I am seeing some destination volumes with busy snaps as a result. Was wondering if anyone has seen the snapmirror errors such as the below:

Failed to start transfer for Snapshot copy "snapmirror.e36...". (CSM: Operation referred to a non-existent session.)

cpeer.xcm.update.warn: Periodic update of peer network information failed. The following operations are incomplete: discovery failure.

cpeer.xcm.addr.disc.warn: Address discovery failed for peer cluster 0df39b.... Reason: Failed to discover remote addresses: RPC: Timed out [from mgwd on node "NODE" (VSID: -3) to Unknown Program:0 at Not available].

smc.snapmir.schd.trans.overrun: Scheduled transfer from source volume '_volume' to destination volume 'volume_dst' is taking longer than the schedule window. Relationship UUID '6b80exxxx'.

Re: Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent sessio

tduran12165 — Tue, 29 Oct 2019 13:35:42 GMT

You can disregard. The messages were as a result of a rogue Riverbed. 🙂

topic Re: Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent sessio in ONTAP Discussions

Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent session.)

Re: Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent sessio