EMS message 'fcp.io.status: Ext_Status 0x1d' frequently occurring
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 0x1d
identifies that there is out of order frame delivery.- 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