Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILED: Onboard Key Manager is already configured

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

Applies to

  • MetroCluster
  • ONTAP 9
  • Onboard Key Manager (OKM)

Issue

The output of metrocluster vserver show is degraded:
 
Example:
 
                              Cluster  : ClusterA
                              Vserver  : SVM1
                      Partner Vserver  : SVM1-mc
                  Configuration State  : syncing
                        Stream Status  : processing-task
                           Failed Row  : Table Name: volume, Operation: get, Fields: SVM1-mc vol_test aggr
                                         Failed Reason : Apply failed for Object: volume Method: baseline. Reason: The 
                                         Onboard Key Manager is already configured. To sync any nodes with the Onboard 
                                         Key Manager configuration, run the "security key-manager onboard sync" 
                                         command. Provide the cluster-wide passphrase initially configured for the 
                                         cluster
                 Last apply fail time  : 3/29/2020 12:25:41
 

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.