Skip to main content
NetApp Knowledge Base

Link break detected on multiple FC ports connected to same switch

Views:
127
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
MetroCluster
Last Updated:

Applies to

  • ONTAP 9
  • FCP

Issue

  • FC target port link break detected on multiple ports connected to same switch and recovers within few minutes 

       EMS log:

Mon Sep 04 04:10:43 EDT [Node32: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0f. Firmware status code status1 0x2, status2 0x7, and status4 0x0.
Mon Sep 04 04:10:43 EDT [Node32: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0h. Firmware status code status1 0x2, status2 0x7, and status4 0x0.

Mon Sep 04 04:10:43 EDT [Node34: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0h. Firmware status code status1 0x2, status2 0x7, and status4 0x0.
Mon Sep 04 04:10:43 EDT [Node34: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0f. Firmware status code status1 0x2, status2 0x7, and status4 0x0.

Mon Sep 04 04:10:43 EDT [Node39: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0f. Firmware status code status1 0x2, status2 0x7, and status4 0x0.
Mon Sep 04 04:10:43 EDT [Node39: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0h. Firmware status code status1 0x2, status2 0x7, and status4 0x0.

Mon Sep 04 04:10:43 EDT [Node40: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0h. Firmware status code status1 0x2, status2 0x7, and status4 0x0.
Mon Sep 04 04:10:43 EDT [Node40: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 0f. Firmware status code status1 0x2, status2 0x7, and status4 0x0.

  • The ports recover within few minutes 

        EMS log:


Mon Sep 04 04:15:22 EDT [Node34: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0f.
Mon Sep 04 04:15:24 EDT [Node34: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0h.
Mon Sep 04 04:15:31 EDT [Node39: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0f.
Mon Sep 04 04:15:32 EDT [Node39: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0h
Mon Sep 04 04:15:18 EDT [Node40: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0h.
Mon Sep 04 04:15:34 EDT [Node40: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 0f.

 

 

 

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.