Skip to main content
NetApp Knowledge Base

E-Series controller "Assertion failed" reset due to FC chip fault

  1. Last updated
  2. Save as PDF
Views:
348
Visibility:
Public
Votes:
1
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • NetApp E-Series
  • Controller Firmware Version: 08.41.10.01 and earlier
  • Fibre Channel (FC) Host connectivity

Issue

With active I/O on a  Fibre Channel host interface, in the rare event that an I/O completion coincides with a chip fault, a controller reboot generating a core dump may occur. The following assertion can be found in excLogShow:

- ---- Log Entry #4 (Core 0) Oct-08-2020 06:18:18 AM ----
10/08/20-11:09:01 (raidSched1): ASSERT: Assertion failed: state == ExchOwnedByChip, file qlfcLLogin.cc, line 349
2020-10-08T11:09:04.062899
Assertion failed: state == ExchOwnedByChip, file qlfcLLogin.cc, line 349

 

 

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.