NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Discussions

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

tduran12165
7,073 Views

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'.

 

 

 

 

1 ACCEPTED SOLUTION

tduran12165
6,992 Views

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

View solution in original post

1 REPLY 1

tduran12165
6,993 Views

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

Public