EMS message 'fcp.io.status: Ext_Status 0x1d' occurring due to faulty host end SFP
Applies to
- All NetApp FAS / AFF Hardware Platforms
- All Data ONTAP Versions
Issue
- The following error string appears in EMS logs:
[NETAPP01: fct_tpd_thread_4:fcp.io.status:debug]: STIO Adapter:6b IO WQE failure, Handle 0x4, S_ID: 4A12xx, OX_ID: 362, Status 0x3 Ext_Status 0x1d
STIO Adapter:2b IO WQE failure, Handle 0x1, Type 8, S_ID: 79DBxx, VPI: 275, OX_ID: DB7, Status 0x3 Ext_Status 0x1d
Ext_Status 0x1didentifies that there is out of order frame delivery and it is coming from the affected hostS_ID- solace service switched between the HA pair and its active on secondary node
- Low RX observed on the affected host connected switch port
=============
Port 6:
=============
Identifier: 3 SFP
Connector: 7 LC
Transceiver: 6804406000000000 8,16,32_Gbps M5 sw Inter,Short_dist
...
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-1000485-01
Vendor Rev: B
...
Temperature: 43 Centigrade
Current: 5.660 mAmps
Voltage: 3234.6 mVolts
RX Power: -10.5 dBm (89.4 uW) -->> Low Rx
TX Power: -2.1 dBm (617.9 uW)
- Items to check include:
- Bad Start of frame
- Bad End of frame
- CRC error
- Disparity error
- Length error
- Link Reset (LR) primitive sequence received
- ISL length between switches
- Verify that SAN Fabric is clean of problems above, and check / replace any failed hardware connected to the NetApp Storage adapter.
- Some of the Items to check include:
- Loose FC connections at all light transition points
- Faulty SFP or cable (host to switch, switch to NetApp controller)
- Faulty FC patch panel (if applicable)
- Misbehaving host initiator
