Skip to main content
NetApp Knowledge Base

Onboard key manager keys don't match between clusters in a MetroCluster

Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster 
  • Onboard Key Manager
  • NVE - Volume Encryption


  • After the MetroCluster ONTAP update, MetroCluster health reports as degraded.

::> system health subsystem  show
Subsystem         Health
----------------- ------------------
SAS-connect       ok
Environment       ok
Memory            ok
Service-Processor ok
Switch-Health     ok
CIFS-NDO          ok
Motherboard       ok
IO                ok
MetroCluster      degraded
MetroCluster_Node ok
FHM-Switch        ok
FHM-Bridge        ok
SAS-connect_Cluster ok
13 entries were displayed.

::>metrocluster operation show
Operation: switchover-simulate
State: failed
Errors: Failed to validate the node and cluster components before the switchover operation.
node1 (overridable veto): Internal Error. The "clus_salt" value in the Onboard Key Manager database was not properly updated

  • Verify the keys on each cluster in a MetroCluster configuration to confirm if the same number of keys are reported.


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.