LIF operationally down and Link break event detected on FC target HBA due to faulty SFP on storage side

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 504

Visibility:: Public

Votes:: 0

Category:: fas-systems

Specialty:: san

Last Updated:

Applies to

Ontap 9
FC
Cisco

Issue

After following troubleshooting steps on switch port and FC cable / patch panel and testing with known good components.
network interface show output shows that LIF is Admin up and Operationally 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 and Link Up errors are seen on EMS logs as below:

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 errors were also observed for that port in EMS logs:

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) observed for that port in EMS logs:

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.

Port is showing as 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