Skip to main content
NetApp Knowledge Base

CONTAP-589678: CONTAP-589678 SAN FC HOST IO Errors during Autosupport

  1. Last updated
  2. Save as PDF
Views:
6
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Issue

After a full Autosupport in rare cases SAN FC Host may experience IO errors. 
Example:
fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 6b has a WQE processing failure of type SLI_IO_FC_CT, command GPL, subtype x1, with status of 3 and an extended status x2 for NPIV port 0.
fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:6b IO WQE failure, Handle 0x1, Type 7, S_ID: 1234, VPI: 3, OX_ID: 3B, Status 0x3 Ext_Status 0x11  
fct_tpd_work_thread_0: scsitarget.slifct.wqeError:debug]: FC port 6b has a WQE processing failure of type SLI_ELS_REQ, command LOGOUT, subtype x0, with status of 3 and an extended status x2 for NPIV port 0.
start_asup_collecto: ems.engine.suppressed:debug]: Event 'rdma.rdr.opFailed' suppressed 1023 times in last 16772 seconds.
Timeout: Operation "fct_topology_ie_iterator::next_imp()" took longer than 60 seconds to complete [from mgwd on node "1234" (VSID: -1) to kernel at 127.0.0.1]

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.