MetroCluster key mismatch between peer clusters
Applies to
- MetroCluster
- ONTAP 9
- Onboard Key Management
Issue
metrocluster check cluster show -checkonboard-key-management -instance
shows:
Cluster01::*> 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 Key Management hierarchy key mismatch between peer clusters.
Type of Check: onboard-key-management
Cluster Name: Cluster02
Result of the Check: warning Additional Information/Recovery Steps:Internal Error. Onboard Key Management hierarchy key mismatch between peer clusters.
The following message also appears in the event log:
ALERT 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.
metrocluster vserver show shows that CRS replication is not working correctly:
Cluster: Cluster01
Vserver: vserver01
Failed Replication Reason: Apply failed for Object:vifsbyname Method: baseline. Reason: There are no active ports in IPspace"ipspace01" on node "Cluster01_Node01".