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

ストレージ側のSFPの障害が原因で、FCターゲットHBAでLIFの動作状態が停止し、リンク切断イベントが検出されました

Views:
16
Visibility:
Public
Votes:
0
Category:
fas-systems<a>2009542683</a>
Specialty:
san
Last Updated:

環境

  • ONTAP 9
  • FC
  • Cisco

問題

  • EMSメッセージFCP.IO.status AEN 0x8048 recv_error occcurring  スイッチポートとFC ケーブル/パッチパネルのトラブルシューティング手順を実行し、正常なコンポーネントでテストした後。 
  • network interface show の出力から、LIFの状態がAdmin upで動作状態がdownになっていることがわかります。

cluster1::> network interface show
       Logical   Status    Network            Current   Current  Is
Vserver    Interface  Admin/Oper Address/Mask          Node    Port   Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
       NetApp_FCLIF_0e
            up/down  20:18:00:xx:xx:xx:xx:de    NetApp-03   1a    true

  • Link break detected Link Up  EMSログには次のようなエラーが記録されます。

Fri Mar 24 22:32:41 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 2d with event status 1 , topology type 1, status1 0x0, status2 0x0.
Fri Mar 24 22:32:43 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 2d.
Fri Mar 24 22:42:11 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 2d with event status 1 , topology type 1, status1 0x0, status2 0x0.
Fri Mar 24 22:42:12 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 2d.
Fri Mar 24 23:01:30 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 2d with event status 1 , topology type 1, status1 0x0, status2 0x0.
Fri Mar 24 23:01:31 +0530 [xxxIMxxx-03: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 2d.

  • IO WQE failure EMSログでそのポートのエラーも確認されました。

Wed Apr 12 08:31:43 -0600 [NetApp-03: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:1a IO WQE failure, Handle 0x0, Type 9, S_ID: 1xxx0, VPI: 4, OX_ID: 3668, Status 0x3 Ext_Status 0x1a  
Wed Apr 12 09:35:51 -0600 [NetApp-03: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:1a IO WQE failure, Handle 0x0, Type 8, S_ID: 1xxx0, VPI: 4, OX_ID: 3C7B, Status 0x3 Ext_Status 0x16  
Wed Apr 12 09:47:23 -0600 [NetApp-03: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:1a IO WQE failure, Handle 0x0, Type 8, S_ID: 1xxx0, VPI: 4, OX_ID: 4F5E, Status 0x3 Ext_Status 0x16  

  • AEN 0x8048 (RECV_ERROR) EMSログでそのポートについて確認された情報は次のとおりです。

Sun Apr 23 10:31:32  0000 [BDAFILERC01-01: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:0e AEN 0x8048 (RECV_ERROR) MboxStatus1 0x1100 MboxStatus2 0x41 Sun Apr 23 10:31:32  0000 [BDAFILERC01-01: fct_tpd_work_thread_0: scsitarget.fct.linkError:error]: FC target HBA: 2d received unexpected error: RECV_ERROR, AEN Status1: 0x8048, Status2: 0x1100, Status3: 0x41.

  • ポートの表示形式 Link disconnected 

slot 2: Fibre Channel Target Host Adapter 2d
                (Emulex LPe32000 (LPe32004) rev. 12, <LINK DISCONNECTED>)
                Board Name:        111-03xxx
                Serial Number:     FP1xxx1971
                Firmware rev:      12.4.3xx.0
                Host Port Addr:    00xx00
                FC Nodename:       50:0a:xx:xx:80:xx:xx:xx (500axxxx80xxxxxx)
                FC Portname:       50:0a:xx:xx:80:xx:xx:xx (500axxxx80xxxxxx)
                Connection:        No link
                Switch Port:       Unknown

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.