Skip to main content
NetApp Knowledge Base

Onboard Key Manager not consistent on MetroCluster

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

Applies to

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

Issue

OKM errors are seen in the EMS logs
 
Example:
Thu Jun 05 03:15:11 +0200 [ClusterA-01: mgwd: km.run.onboard.sync.needed:alert]: The Onboard Key Manager configuration is not consistent between the local cluster and the peer cluster of the MetroCluster configuration. This can lead to a failure during a future switchover or switchback event. Synchronize the configuration on the peer cluster.

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.