Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILED: MCC CRS doesn't replicate vdiskTable entries

  1. Last updated
  2. Save as PDF
Views:
80
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP 9
  • Degraded SVMs reported

Issue

  • The configurations state of a Vserver in a MetroCluster is marked as degraded or syncing due to failed entries in vdiskTable_view
  • Output of advanced command metrocluster vserver show -fields failed-row,failed-reason shows:
                       Cluster  : cluster1                            
                       Vserver  : vserver1
               Partner Vserver  : vserver1-mc
           Configuration State  : syncing
                 Stream Status  : processing-task
                     Failed Row : Table Name: vdiskTable_view, Operation: get, 
                     Fields: 9acf6ec3-c8de-11e5-bb58-00a0912963441 1234567890 8120042e0000000000000000000000655d9d3fc4 
                  Failed Reason : Apply failed for Object: vdiskTable_view Method: baseline. Reason: entry doesn't exist

 

 

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.