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

接続が短時間失われると、 FAS8200 / AFF A300 で DR ミラーが機能しなくなります

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

環境

  • MetroCluster IP
  • FAS8200 / AFF A300
  • インターコネクト

説明

MetroCluster IP接続が失われてリカバリされると、物理的に接続されていて正常な状態であっても、HA、DR、またはAUXインターコネクト接続が失われる可能性があります。

iWARP接続がアップ状態であっても、ミラーステータスは無効およびオフラインと報告されます。 metrocluster interconnect show:

Cluster1::> metrocluster interconnect show
  (metrocluster interconnect show)
                          Mirror   Mirror
                  Partner Admin    Oper
Node Partner Name Type    Status   Status  Adapter Type   Status
---- ------------ ------- -------- ------- ------- ------ ------
Node1A         Node2A HA enabled online
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up
               Node1B DR disabled offline
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up
               Node2B AUX disabled offline
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up
Node2A         Node1A HA enabled online
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up
               Node2B DR disabled offline
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up
               Node1B AUX disabled offline
                                           e1a     iWARP  Up
                                           e1b     iWARP  Up

NVRAMの同期が失われたためにローカルHAがオフラインになる可能性もあります。  フェイルオーバーの適性については、を参照してください。 storage failover show:

Cluster1::> storage failover show
                              Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
Node1
               node2  false    Connected to node2,
                                       Takeover is not possible: NVRAM log
                                       not synchronized
Node2
               Node1  false    Connected to node1,
                                       Takeover is not possible: NVRAM log
                                       not synchronized

AutoSupportが使用可能な場合は METROCLUSTER-TCP-SYSCTL-MCC 、完全なAutoSupportでセクションを確認し、次のエラーを確認します。

 name=wafl qp_id=0 state=DISCONNECTED rhp=0xfffff806190ed800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=wafl qp_id=0 state=CONNECTING rhp=0xfffff8086ce41800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=raid qp_id=0 state=CONNECTING rhp=0xfffff8029f887000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=raid state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=raid qp_id=0 state=DISCONNECTED rhp=0xfffff80287209000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=raid state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=misc qp_id=0 state=CONNECTING rhp=0xfffff8087fa03000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=misc state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=misc qp_id=0 state=CONNECTING rhp=0xfffff80844c73800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client 

WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 エラーが存在する場合、問題はバグ 1307431として確認されます。 

 

 

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.