Skip to main content
NetApp Knowledge Base

CONTAP-756913: SnapMirror Abort REST API returns HTTP 200 but transfer remains in transferring state when intercluster LIFs are down

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

Issue

  • SnapMirror Abort REST API returns HTTP 200 after an abort request on an Async CG relationship
  • SnapMirror Break and other dependent operations can fail because the transfer is still active
  • Occurs during workflows such as SRA Unplanned Failover when intercluster LIFs are unavailable

 

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.