Skip to main content
NetApp Knowledge Base

CONTAP-737786: SnapMirror relationship creation fails with SVM peering error when SVMs are in a custom IPspace and the cluster peer is in the Default IPspace

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

Issue

When a SnapMirror relationship is created with create_destination (REST API {}POST /api/snapmirror/relationships{}) and the source and destination SVMs are in a custom IPspace while the cluster peer relationship was created in the Default IPspace, the operation fails with:
SVM peering failed between "<source_svm>" and "<destination_svm>".
Reason: Cannot create the SVM peer permission because the cluster peer relationship with peer cluster "<peer_cluster>" was created using the IPspace "Default", but the specified SVM "<source_svm>" was created using the IPspace "<custom_ipspace>". To create SVM peer permission, both IPspaces must be the same.

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.