Skip to main content
NetApp Knowledge Base

EMS message 'fcp.io.status: Ext_Status 0x1d' frequently occurring

Views:
3,323
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
san
Last Updated:
12/10/2024, 2:21:38 PM

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

  • Only the volume which is mount from VMware ESX using FC can not be accessed, but it is restored in less than a second.
  • This results in a degradation of performance on the guest OS side.
  • The amount of power sent from outside is low.

Node Adapter Received Optical Power
NETAPP01 10a 557.6 (uWatts)
NETAPP01 10b 600.2 (uWatts)
NETAPP01 10c 104.7 (uWatts)
NETAPP01 10d 527.4 (uWatts)
NETAPP01 1a 437.9 (uWatts)
NETAPP01 1b 829.3 (uWatts)
NETAPP01 1c 448.2 (uWatts)
NETAPP01 1d 501.9 (uWatts)

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.