Skip to main content
NetApp Knowledge Base

Fail to sync onboard key management keys on partner cluster of MetroCluster IP

Views:
340
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster IP
  • Onboard Key Manager (OKM)

Issue

  • After setting up Onboard Key Manager in siteA of MetroCluster IP, fails to  sync the keys on siteB of MetroCluster IP via the command security key-manager onboard sync  with the following error messages:

Error: command failed: This command is available only when the Onboard Key Manager is enabled. Use the "security key-manager onboard enable" command to enable the Onboard Key Manager and then try again.

  • But as instructed, when trying to run security key-manager onboard enable on siteB, it shows a contradictory error :

Error: command failed: This cluster is part of a MetroCluster configuration. The Onboard Key Manager has already been configured at the partner site. Run the "security key-manager onboard sync" with the same passphrase before proceeding with any key manager operations.  Failure to do so could lead to switchover or switchback failure.

  • metrocluster check show :

    Component           Result
    ------------------- ---------
    nodes               ok
    lifs                ok
    config-replication  warning
    aggregates          ok
    clusters            warning
    connections         ok
    volumes             ok

  • metrocluster check config-replication show:

Vserver Streams Recovery Steps: Run the "metrocluster vserver show" command for more details.

  • metrocluster vserver show indicates an vserver is stuck at  pending-setup status

Configuration State: pending-setups

 

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.