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

MetroCluster フェイルオーバーモニタのnodenameのテイクオーバーが無効化され、非同期ログ

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

環境

  • ファブリックMetroCluster
  • ONTAP 9

問題

  • FCVIポートの切断は、フェイルオーバーが無効になる前に確認されます。

Mon Jan 22 20:36:54 +0100 [CL01-01: ispfcvi2500_main3: fcvi.qlgc.received.disconnect:notice]: FC-VI adapter: Disconnect request received on port 5c. QP name = WAFL, QP index = 3, Remote node's system id = 537407299.

Mon Jan 22 20:36:54 +0100 [CL01-01: fcvi_cm: pfo.failover.start.error:debug]: params: {'port': '2', 'client': 'WAFL', 'partner': 'DR Primary Partner', 'trigger': 'IPFO_TRIG_PATH_DOWN', 'reason': 'Failover not enabled'}

  • テイクオーバー無効メッセージが生成され、数秒後に自動的に有効になります:

Mon Jan 22 20:36:56 +0100 [CL0101-01: cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of CL01-02 disabled (unsynchronized log).

Mon Jan 22 20:37:50 +0100 [CL0101-01: cf_main: cf.fsm.takeoverByPartnerDisabled:error]: Failover monitor: takeover of CL0101-01 by CL0101-02 disabled (unsynchronized log)

Mon Jan 22 20:38:20 +0100 [CL01-01: cf_main: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of ASH06NETAPPCL2-02 by ASH06NETAPPCL2-01 enabled

Mon Jul 22 20:39:20 +0100 [CL01-01: cf_main: cf.fsm.takeoverOfPartnerEnabled:notice]: Failover monitor: takeover of CL01-01 enabled

  • また、以下のemsアラートを受信しました。

Mon Jan 22 20:37:00 +0100 [CL01-01: monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of CL01-02 is not possible: unsynchronized log.

Mon Jan 22 20:36:54 +0100 [CL01-01: fcvi_cm: nvmm.mirror.aborting:debug]: mirror of sysid 2, partner_type DR PARTNER and mirror state NVMM_MIRROR_ONLINE is aborted because of reason NVMM_ERR_LINK_DOWN.

  • スイッチのログには低い RX 値が表示されます。

=============
Port  0:
=============
Identifier:  3   SFP
Connector:   7   LC
Transceiver: 6804406000000000 8,16,32_Gbps M5 sw Inter,Short_dist

Current:    5.230   mAmps
Voltage:    3318.20 mVolts
RX Power:   -4.6   dBm (346.60uW)
TX Power:   -1.3   dBm (736.30 uW)

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.