Skip to main content
NetApp Knowledge Base

km.mcc.okmkey.mismatch due to SVM migration

  1. Last updated
  2. Save as PDF
Views:
90
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
metrocluster
Last Updated:

Applies to

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

Issue

After initiating an SVM-DR migration of an SVM to one side of a metrocluster, the following alert is generated:

km.mcc.okmkey.mismatch: This cluster is part of a MetroCluster configuration. The list of OKM hierarchy keys on one or both of the clusters is potentially corrupted.

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.