Skip to main content
NetApp Knowledge Base

CONTAP-696985: Core Dump Failure After Network Diagnostic Collection on Certain Platforms

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

Issue

On certain platforms running multiple ONTAP versions, unloading the SIFTR ({}siftr{}) TCP diagnostic tracing module after support-directed network data collection can cause repeated failures when a core dump is later triggered. The node does not complete the core dump and is reset by its watchdog to recover, so no core file is available for follow-up analysis.
When the core dump is triggered with {}system core{}, the console displays:
PANIC : User initiated "system core" nmi on cpu 0
This is followed by repeated recursive PANIC: page fault messages and multiple recursive panics - rebooting.

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.