Skip to main content
NetApp Knowledge Base

Link break detected on Fibre Channel target HBA due to faulty cable

Views:
2,285
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • FCP

Issue

  • FC target port link - unstable/down.
  • Below events are logged in EMS on NetApp:
[?] Wed Oct 14 09:22:49 MDT [host1: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 4c with event status 1 , topology type 1, status1 0x0, status2 0x0.
[?] Wed Oct 14 09:22:50 MDT [host1: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 4c.
 
Tue Mar 05 15:19:28 0530 [NetApp: fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 3a has a WQE processing failure of type SLI_ELS_REQ, command PLOGI, subtype x0, with status of 3 and an extended status x4 for NPIV port 0. 
Tue Mar 05 15:19:29 0530 [NetApp: fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 3a has a WQE processing failure of type SLI_ELS_REQ, command PLOGI, subtype x0, with status of 3 and an extended status x1a for NPIV port 0.
Tue Mar 05 15:26:48 0530 [NetApp: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 3a with event status 1 , topology type 1, status1 0x0, status2 0x0. 
Tue Mar 05 15:26:59 0530 [NetApp: fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 3a has a WQE processing failure of type SLI_ELS_REQ, command PLOGI, subtype x0, with status of 3 and an extended status x1a for NPIV port 0."
  • Below steps can be followed to isolate the issue :
    • Check the controller port status, replace SFP if Tx signal power is low.
    • Check the SFP status of connected switch port, replace the SFP if switch port Tx power is low.
    • Replace FC cable if SFP Tx power is normal for both FC end side, but SFP Rx power is low for any side.
    • If patch panel involved, troubleshoot link components.
    • If there is low Rx signal at both ends, check for patch panels in between and try different port for testing purpose

Example:
cluster1::> fcp adapter show -node host1 -adapter 4c -instance
(network fcp adapter show)

Node: host1
Adapter: 4c
Description: Fibre Channel Target Adapter 4c (Emulex LPe16000 (LPe16004), rev. 13, 16G)
Physical Protocol: fibre-channel
Maximum Speed: 16
Administrative Status: up
Operational Status: online
Extended Status: ADAPTER UP
Host Port Address: b10140
Firmware Revision: 11.2.219.4
Data Link Rate (Gbit): 16
Fabric Established: true
Fabric Name: xx:xx:xx:xx:xx:xx:xx:xx
Connection Established: ptp
Is Connection Established: true
Mediatype: ptp
Configured Speed: auto
Adapter WWNN: aa:aa:aa:aa:aa:aa:aa:aa
Adapter WWPN: bb:bb:bb:bb:bb:bb:bb:bb
Switch Port: switch1:1/88
Form Factor Of Transceiver: SFP
Vendor Name Of Transceiver: EMULEX
Part Number Of Transceiver: AFBR-57F5MZ-ELX
Revision Of Transceiver:
Serial Number Of Transceiver: AC1544J02X7
FC Capabilities Of Transceiver: 4,8,16 (Gbit/sec)
Vendor OUI Of Transceiver: 00:17:6a
Wavelength In Nanometers: 850
Date Code Of Transceiver: 15:10:26
Validity Of Transceiver: true
Connector Used: LC
Encoding Used: 64B66B
Is Internally Calibrated: true
Received Optical Power: 56.2 (uWatts)
Is Received Power In Range: true
SPF Transmitted Optical Power: 610.0 (uWatts)
Is Xmit Power In Range: true

 

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.