Skip to main content
NetApp Knowledge Base

FC Target port flaps and goes to "link not connected" state

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

Applies to

  • ONTAP 9.x
  • FCP

Issue

  • Intermittent link break events observed on the FC target port under EMS, post which the FC port resets itself:

Sun Nov 27 20:53:54 EST [NetApp: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:10a IO WQE failure, Handle 0xa, Type 8, S_ID: 11900, VPI: 3, OX_ID: 3F4, Status 0x3 Ext_Status 0x16
Sun Nov 27 22:04:06 EST [NetApp-05: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 10a with event status 1 , topology type 1, status1 0x0, status2 0x0.
Sun Nov 27 22:04:24 EST [NetApp-05: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 10a.
Sun Nov 27 22:04:31 EST [NetApp-05: fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 10a has a WQE processing failure of type SLI_ELS_REQ, command PLOGI, subtype x0, with status of 3 and an extended status x2 for NPIV port 0.
Sun Nov 27 22:04:49 EST [NetApp-05: fct_tpd_work_thread_0: scsitarget.hwpfct.errorReset:notice]: An error was encountered in the FC target driver on Fibre Channel target adapter 10a. The adapter will be automatically reset to clear the PLOGI failed for base port error (Status: 3 Extended status: 2 Index: 1) condition.
Sun Nov 27 22:04:49 EST [NetApp-05: fct_tpd_thread_10: fcp.io.status:debug]: STIO Adapter 10a resetting with 0 ITNs and 0 commands to drain
Sun Nov 27 22:04:49 EST [NetApp-05: fct_tpd_thread_10: scsitarget.fct.reset:notice]: Resetting Fibre Channel target adapter 10a.

  • ASUP SYSCONFIG-A.XML FC port status shows as Link Not Connected
 slot 10: Fibre Channel Target Host Adapter 10a
                (Emulex LPe32000 (LPe32002) rev. 12, <LINK NOT CONNECTED>)
                Board Name:        111-03249
                Serial Number:     FC72662464
                Firmware rev:      11.2.219.4
                Host Port Addr:    000000
                FC Nodename:       50:0a:09:80:80:44:6d:80 (500a098080446d80)
                FC Portname:       50:0a:09:83:a0:44:6d:80 (500a0983a0446d80)
                Connection:        No link
                Switch Port:       Unknown
		SFP Vendor Name:   FINISAR CORP.
		SFP Vendor P/N:    FTLF8532P4BCV-EM
		SFP Vendor Rev:    A
		SFP Serial No.:    PXQ1M94
		SFP Connector:     LC
		SFP Capabilities:  8, 16, 32 Gbit/Sec
  • ASUP: FCP Target Adapter TX power is in expected range under FCP-ADAPTER.XML

Received Optical Power    573.3 (uWatts)
SPF Transmitted Optical Power    798.0 (uWatts)

  • ASUP: FCP Target Adapter RX power is degrading in comparison with previous ASUPs under FCP-ADAPTER.XML as per SFP Tx and Rx power 

Latest:
Received Optical Power    415.8 (uWatts)
SPF Transmitted Optical Power    798.0 (uWatts)

Previous:
Received Optical Power    573.3 (uWatts)
SPF Transmitted Optical Power    798.0 (uWatts)

Sfpshow:
=============
Port 12:
=============
Identifier:  3    SFP
Connector:   7    LC
Transceiver: 6804404000000000 8,16,32_Gbps M5 sw Short_dist
Encoding:    6    64B66B
Baud Rate:   280  (units 100 megabaud)
Length 9u:   0    (units km)
Length 9u:   0    (units 100 meters)
Length 50u (OM2):  3    (units 10 meters)
Length 50u (OM3):  7    (units 10 meters)
Length 62.5u:0    (units 10 meters)
Length 50u (OM4):  10   (units 10 meters)
Vendor Name: BROCADE
Vendor OUI:  00:05:1e
Vendor PN:   57-1000333-01
Vendor Rev:  A
Wavelength:  850  (units nm)
Options:     083a Loss_of_Sig,Tx_Fault,Tx_Disable
BR Max:      112
BR Min:      0
Serial No:   JAF417120000GP0
RX Power:    -1.0    dBm (797.7uW)
TX Power:    -3.7    dBm (430.8 uW)

 

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.