メインコンテンツへスキップ

MetroCluster ピアクラスター間のキーの不一致

Views:
11
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

環境

  • MetroCluster
  • ONTAP 9
  • オンボードキー管理

問題

metrocluster check cluster show -checkonboard-key-management -instance には次のように表示されます:
 

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.

イベントログには、以下のメッセージも表示されます:

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 コマンドを実行すると、CRS レプリケーションが正しく機能していないことがわかります:

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".

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.