Skip to main content
NetApp Knowledge Base

How to upload an ONTAP 9 core file for analysis

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

 

Applies to

  • ONTAP 9
  • Core Dump

Description

  • A  node has experienced a panic or a forced panic has been triggered and a core file (an in-memory image) has been created.
  • The core needs to be uploaded to NetApp for analysis
  • Core files are typically quite large, in the tens to hundreds of GB
  • Depending on the size of the core file and overall WAN throughput, core uploads can take an extended amount of time to complete, this is especially true for systems with large amounts of RAM (hundreds of GB)
  • Generally, it is recommended to perform the giveback as soon as possible after a core dump for software-related issues
  • More information found at Manage core dumps

Procedure

Core Dump File Identification
  1. To determine the core name, run the system node coredump show command to find the appropriate file:

Example

            ::> system node coredump show

Node    Core Name                             Saved    Panic Time
-----   ------------------------------------- -------  -----------------
node1
        core.538302378.2025-04-09.20_47_44.nz  true    4/09/2025 03:18:45

::> system node coredump show -node local

Node:Type Core Name Saved Panic Time
----------- ------------------------------------------- ----- -----------------
node:kernel core.538302378.2025-04-09.20_47_44.nz true 4/09/2025 15:05:01

  1. Verify that the core has been saved true before starting the upload process.
  2. If the core does not show as saved true use the system node coredump status command to view the current status and wait until the save is complete.

  3. Lookup the Core file segments, system node coredump segment show you will need these later.

Example

::> node coredump segment show

Node: Node01
Segment Directory: core.538302378.2025-04-09.20_47_44
           Panic Time: 4/9/2025 16:47:44
                            Number of Segments: 1
                                     Segment File Name:
                                               core.538302378.2025-04-09.20_47_44.nvram.nz
                                               core.538302378.2025-04-09.20_47_44.tagstore.nz

  1. Upload the files. There are several methods for transferring a core from ONTAP  to NetApp as outlined below.
Methods for Copying and Uploading the Core File

 

Method 1: Upload using AutoSupport
  • This is now the recommended method for uploading a core file to NetApp.

Note:

  • Transporting AutoSupport through HTTPS is required for this feature. 
  • To verify HTTPS is being used, run the following command:

::> system node autosupport show -fields transport

  1. Start the upload of the main core file by using the system node autosupport invoke-core-upload command as below. (case number is required)
Core type Command

Main Core file

::> system node coredump show

::> autosupport invoke-core-upload -node <node name> -core-filename core.4083601408.2025-02-18.20_44_01.nz -case-number <case number>

Segments (if available)

::> node coredump segment show

Node: Node01
Segment Directory: core.538302378.2025-04-09.20_47_44
   Panic Time: 4/9/2025 16:47:44
   Number of Segments: 1
   Segment File Name:
         core.538302378.2025-04-09.20_47_44.nvram.nz
         core.538302378.2025-04-09.20_47_44.tagstore.nz
  • -core-filename = Segment directory / Segment File Name

::> autosupport invoke-core-upload -node <node name> -core-filename core.538302378.2025-04-09.20_47_44/core.538302378.2025-04-09.20_47_44.nvram.nz -case-number <case number>

::> autosupport invoke-core-upload -node <node name> -core-filename core.538302378.2025-04-09.20_47_44/core.538302378.2025-04-09.20_47_44.tagstore.nz -case-number <case number>

Note: It will generate an AutoSupport message

Example:  HA Group Notification (CORE INFO: mgwd.59595.1111111.2020-05-23.15_26_50.ucore.bz2) NOTICE
  1. To view the progress of the core upload, use the following commands:
  • First, determine the sequence number (seq-num) of the core upload AutoSupport message:

::> autosupport history show -node <node name> -fields seq-num,subject

  • Then, input the node name and the seq-num to determine the upload status:

::> autosupport history show-upload-details -node <node name> -seq-num <seq-num>

  • The system node autosupport history show command displays information about the 50 most recent AutoSupport messages sent by nodes in the cluster.

::> system node autosupport history show -node <nodename>

Example

::> system node autosupport history show -node node1

             Seq                                    Attempt  Percent  Last
Node         Num   Destination Status               Count    Complete Update
------------ ----- ----------- -------------------- -------- -------- --------
node1
             1324
                   smtp        ignore               1        -        5/26/2020 00:44:48
                   http        sent-successful      1        100      5/26/2020 00:45:02
                   noteto      ignore               1        -        5/26/2020 00:44:48

​​​​​

Method 2: Service Processor Infrastructure (SPI) web interface
  • If you must collect the core file before performing the giveback, you must use Method 2 and log in to the SPI interface to download the core
  • If the node is still down but has booted to waiting for giveback, the core file should be available in the core-dumps folder for that node

Note: If you cannot see the core file when accessing the SPI from cluster-mgmt LIF, access the SPI from the node-mgmt LIF that owns the core file.

  1. Access the Service Processor Infrastructure (SPI) web interface

    1. Point the web browser to the IP address of the cluster management LIF  SPI web service URL in the following format:

    2. https://cluster-mgmt-LIF/spi

  2.  The file will be located in the core-dumps folder for the specified node.

clipboard_eb3b6a3d8f216669ac781440573a4e1d1.png

  1. Download the files from the root volume to a local workstation. 
Main Core file                            clipboard_e6f4befa3adf1a1f15b19ecc98db8a055.png
Segments (if available)
  1. Enter the Core file directory to locate the Segments

                         clipboard_edcdaeabcf870b0895f3b21149bddd682.png

  1. Download each segment (if available)

                         clipboard_e08d824e912383d362334d97c08489178.png

 

  1. Once the file is on a local workstation, it can be uploaded using an available method described in How to upload a file to NetApp.
    1. Upload the Main Core file first
    2. Then upload the Core Segments (if available) in any order
  2. If needed, check How to upload a core file from a down node in clustered Data ONTAP

 

Method 3: Copy to an external USB device​
Node Booted to ONTAP
  1. Prepare a USB device in the following manner:

    1. A device formatted with the FAT32 filesystem.

      • NOTE: FAT32 only supports files up to 4GB. Use ext2 for files over 4GB.

    2. A device formatted with the ext2 filesystem with the largefile flag set.

      • This can be done using the following command on a Linux host: Be extremely careful with the device name to make sure it is the correct device. sudo mkfs.ext2 -T largefile <device_name>.

  2. Connect the USB device to the ONTAP controller that has the core file.

  3. Confirm the USB device is seen with the system node coredump external-device show command.

  4. Copy the core file to the USB device using the system node coredump external-device save command.

  5. Once the file is on the USB device, it can be uploaded using an available method described in How to upload a file to NetApp.
  6. If needed, check How to upload a core file from a down node in clustered Data ONTAP.

Node cannot Boot

(LOADER)

 

​​

Method 4: SCP from the Cluster

Please contact NetApp Technical Support or log into the NetApp Support Site to create a case. Reference this article for assistance with the solution. 

  • The solution requires Diagnostic-level recovery. 
  • The use of Diagnostic commands and recovery steps is potentially disruptive and should only be used with guidance from NetApp Support. 
Video Reference

 

 

 

 

 

 

 

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.