Skip to main content
NetApp Knowledge Base

Fails to create the initial MetroCluster configuration while NetApp Aggregate Encryption (NAE) and Onboard Key Manager (OKM) is configured on both partner sites

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

Applies to

  • MetroCluster IP
  • NetApp Aggregate Encryption (NAE)
  • Onboard Key Manager (OKM)

Issue

Fails to create the initial MetroCluster configuration with the following error messages:
 
ClusterA::*> metrocluster configure -node-name nodeA01

Error: command failed: MetroCluster cannot be configured while keymanager is configured on both partner sites. Disable  keymanager on one of the partner sites and then proceed with MetroCluster configuration. After successfully configuring MetroCluster, configure key manager on the partner site where it was disabled. If using onboard key manager, run the "security key-manager onboard sync" command on the partner site. Otherwise, if using external key manager, run the "security key-manager external enable" command on the partner site.

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.