STIO errors with Ext_Status 0x16 and Ext_Status 0x1d on storage adapter port due to faulty switch sfp
Applies to
- Ontap 9
- Brocade switch
- FCP
Issue
EMS
Logs reports IO WQE failure with Ext_Status 0x16 and Ext_Status 0x1dExtended status 0x16
indicates Host initiator sent abort to clear command queue.
Fri May 24 17:40:31 +0000 [Node-02: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:9a IO WQE failure, Handle 0x4, Type 8, S_ID: 110XX, VPI: 3, OX_ID: 35E, Status 0x0 Ext_Status 0x16
Sun Jul 07 05:06:40 +1000 [Node-02: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:3b IO WQE failure, Handle 0x4, Type 8, S_ID: 6C08XX, VPI: 4, OX_ID: 2F91, Status 0x3 Ext_Status 0x1d
Extended status 0x4
also seen as below.
fcp.io.status: STIO Adapter:1c IO WQE failure, Handle 0x2, Type 8, S_ID: xxx03, VPI: 3, OX_ID: 6xx, Status 0x3 Ext_Status 0x4
- Low Rx power is reported on the storage port connected to the switch.
Port 3b
Rx: 183.9 (uWatts)
Tx: 580.6 (uWatts)
- High
PCS
errors are reported on switch port connected to storage adapter port.
porterrshow :
frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout pcs uncor
tx rx in err g_eof shrt long eof out c3 fail sync sig tx rx err err
16: 58.9m 110.1m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 389 0
- Simultaneous
STIO
events are reported on storage end as thePCS
errors on switch port increases. - Plug into a known good device for fault isolation of cable and sfp by following below steps:
- In order to do fault isolation if the hardware, move the cable to next available port on the switch end and observe for any increments.
- If the issues follows on new port, replace the cable/patch panel and verify the port counters.
- If the issue does not follow to the new port, then swap the SFP of the affected port with a good known working SFP and see if the errors subsides.
- If errors subsides, proceed with the solution.