Skip to main content
NetApp Knowledge Base

OKM key hierarchy mismatch between peer clusters

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

Applies to

  • MetroCluster
  • ONTAP 9
  • AFF/ASA/FAS

Issue

"Metrocluster vserver show" shows multiple vservers in a degraded state followed by DR config replication failure alerts

"metrocluster check cluster show-check onboard-key-management -instance" states that the OKM is not in sync between the two clusters:

::*>metrocluster check cluster show-check onboard-key-management -instance
Type of Check:onboard-key-management
Cluster Name: Cluster01
Result of the Check:warning Additional Information/Recovery Steps:Internal Error. Onboard KeyManagement hierarchy key mismatch between peer clusters.
Type of Check:onboard-key-management

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.