OKM keys mismatch between peer clusters
- Views:
- 88
- Visibility:
- Public
- Votes:
- 0
- Category:
- metrocluster
- Specialty:
- metrocluster
- Last Updated:
- 2/19/2025, 9:34:55 AM
Applies to
- MCC
- ONTAP 9
- Onboard Keymanager
- SVM-DR migration into MCC
Issue
- While running Metrocluster check, onboard key-manager gives the following error preventing switchback:
mcc01::*> metrocluster check cluster show -check onboard-key-management -instance
Type of Check: onboard-key-management
Cluster Name: mcc01
Result of the Check: warning
Additional Information/Recovery Steps: Internal Error. Onboard Key Manager hierarchy key mismatch between peer clusters. The local and partner clusters do no
Type of Check: onboard-key-management
Cluster Name: mcc02
Result of the Check: warning
Additional Information/Recovery Steps: Internal Error. Onboard Key Manager hierarchy key mismatch between peer clusters. The local and partner clusters do no2 entries were displayed.
Error remain even after following: Some VServers show their status as replication-paused:
- The following
km.mcc.okmkey.mismatch
events can be observed on both sides of the MetroCluster:
Thu Nov 21 23:15:05 +0100 [MCC-cluster-01: mgwd: km.mcc.okmkey.mismatch:alert]: This cluster is part of a MetroCluster configuration. The list of OKM hierarchy keys on one or both of the clusters is potentially corrupted.