メインコンテンツまでスキップ

システムが原因で拡張ステータスアダプタが停止している FCP アダプタがオフラインになっています

Views:
34
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

環境

  • ONTAP 9
  • SAN
  • ファイバチャネルターゲットホストアダプタ

問題

  • コマンドを実行すると fcp adapter show -node xxxx -adapter xx 、次のような結果になります。
  • Operational Status: offline
  • Extended Status: ADAPTER DOWN DUE TO SYSTEM
  • Error: show failed: Timeout while getting fabric information"
  • EMS / event log show で、アダプタポートに関連するエラーとアラートが報告されます
  • アダプタの再初期化に失敗しました(例)。

[NODE-02: fct_tpd_thread_0: scsitarget.hwpfct.errorReset:notice]: An error was encountered in the FC target driver on Fibre Channel target adapter 5a. The adapter will be automatically reset to clear the Depletion of Driver MQ condition.
[NODE-02: fct_tpd_thread_0: fcp.io.status:debug]: STIO Adapter 5a resetting with 0 ITN and 0 commands to drain.
[NODE-02: nvmf_master_0: nvmf.spdk.err:debug]: fc_adm_api.c:1448 Hw port 0 already offline. err = 2
[NODE-02: fct_tpd_thread_0: scsitarget.hwpfct.initFailed:alert]: Initialization of adapter failed on Fibre Channel target adapter 5a.
[NODE-02: fct_tpd_thread_0: scsitarget.fct.port.offline:error]: Fibre Channel Target port 5a was taken operationally offline due to too many errors received by the FCT driver.
[NODE-02: fct_tpd_thread_0: fcp.io.status:debug]: STIO Adapter 5a reinitialization failed, saving RAS trace data.

  • IO WQE エラー(例):

[NODE-02: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:5a IO WQE failure, Handle 0x0, Type 8, S_ID: 610601, VPI: 3, OX_ID: 18D, Status 0x3 Ext_Status 0x16

 

問題を絞り込むには、次の手順に従います

  • S_ID(ソースID)を使用してイニシエータを特定し、スイッチログまたはEMSログ内の対応するエントリと関連付けます( event log show または ActiveIQ AutoSupport経由)。
  • それぞれのイニシエータログイン またはスイッチログエントリ を検索します。[NODE-02: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '5a' by initiator port: 'WWPN​​​​​' address 0xS_ID. The target virtual port is: 'NetApp FC Target Port (LPe32000) svm-NAME:NODE-02_fc_lif_1'.​​​
  • 接続のエンドツーエンドのすべての物理コンポーネントが正常であることを確認し、 メッセージの原因となる中止/リセットの原因となって fcp.io.status:debug いる理由と対処方法を特定します。

 

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.