FC Target port reporting link disconnected due to faulty card on Storage end
Applies to
- ONTAP 9.x
- FC
- SAN switches
Issue
- The ONTAP FC port is reporting
link disconnected
with extended status asAdapter up
.
- A critical alert is received for FC target port error or the link shows disconnected:
- The Rx and Tx power reported on the FC port is very low-
Rx: 0.0 (uWatts)
Tx: 0.0 (uWatts)
- Verify with Harware Universe to confirm that the SFP in use is supported.
- The Rx and Tx levels on the affected FC port are displaying as optimal.
- The Rx and Tx on the switch port are displaying as optimal.
- Link break and link up events are reported in EMS logs.
Mon May 20 10:12:18 0700 [node2: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 1b with event status 1 , topology type 1, status1 0x0, status2 0x0.
Mon May 20 10:12:19 0700 [node2: nvmf_master_0: nvmf.spdk.err:debug]: fc_adm_api.c:2273 port link break: HW port 1 already offline. rc = 2
Mon May 20 10:26:09 0700 [node2: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 1b.
Mon May 20 10:37:39 0700 [node2: fct_tpd_thread_1: fcp.io.status:debug]: STIO Adapter 1b reinitialization completed successfully. Port configured online.
Mon May 20 10:37:45 0700 [node2: fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 1b has a WQE processing failure of type SLI_ELS_REQ, command FLOGI, subtype x0, with status of 3 and an extended status x2 for NPIV port 0.
- Below troubleshooting steps can be performed to isolate the issue.
- Perform cable teseting along with patch panel if cable has any issues proceed with cable reseat\replacement.
- Replace SFP on storage FC target port.
- If issue still persists, replace SFP on switch port.
- Toggle the port on storage end and see if port state changes.
- If the issue persists even after replacing cable/patch panel & SFP on either ends :
- Connect cable from bad port to any unused port on the switch and verify the link status and LED indicators
- Swap cable from working target port to the bad port and verify the status
- Isolate the issue and device to determine the device causing the bad port