How to upload a core file for analysis

This article describes the procedure to be followed to upload a clustered Data ONTAP 8.x core file for analysis.

A clustered Data ONTAP 8.x node has experienced a panic or a forced panic has been triggered. The core needs to be uploaded to NetApp for analysis.

PROCEDURE

There are three methods for transferring a core from a clustered Data ONTAP node to NetApp.

To determine the core name, run the core show command to find the appropriate file:
Note: Verify that the core has been saved before starting the upload process.  If not, use the command coredump status to view the current status.

::> core show
Node    Core Name                             Saved    Panic Time
-----   ------------------------------------- -------  -----------------
node1
core.101178384.2014-08-28.07_18_45.nz  true    8/28/2014 03:18:45

Generally, it is recommended to perform the giveback as soon as possible for software related issues. That said, if you must collect the core file before performing the giveback, you must use Method 2 below 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.

In ONTAP 9 view the core dump files for a node by using the system node coredump show command.

Example

In the following example, core dump files are displayed for the local node:

cluster1::> system node coredump show -node local
Node:Type   Core Name                                   Saved Panic Time
----------- ------------------------------------------- ----- -----------------
node:kernel core.4073000068.2013-09-11.15_05_01.nz      true  9/11/2013 15:05:01

Method 1:

Upload using AutoSupport:
Starting with clustered Data ONTAP 8.3, it is now possible to upload core files 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:
::> autosupport show -fields transport

To start the upload of the core file:
::> autosupport invoke-core-upload -node <node name> -core-filename <file name> -case-number <case number>

To view the progress of the core upload you can use the following commands:

First, determine the seq-num of the core upload autosupport
::> autosupport history show -node <node name> -fields seq-num,subject

Then input the node name and the seq number to determine the upload status
::> autosupport history show-upload-details -node <node name> -seq-num <seq-num>

In ONTAP 9 Generate an AutoSupport message and upload a core dump file by using the system node autosupport invoke-core-upload command.

::> system node autosupport invoke-core-upload -core-filename core.4073000068.2013-09-11.15_05_01.nz -node local
The system node autosupport history show command displays information about the 50 most recent AutoSupport messages sent by nodes in the cluster.

cluster1::> system node autosupport history show -node node1
             Seq                                    Attempt  Last
Node         Num   Destination Status               Count    Update
------------ ----- ----------- -------------------- -------- -----------------
node1        56
                   smtp        ignore               1        11/18/2010 01:10:01
                   http        re-queued            2        11/18/2010 02:50:07
                   noteto      transmitting         1        11/18/2010 01:10:01
             55
                   smtp        ignore               1        11/18/2010 00:53:59
                   http        sent-successful      3        11/18/2010 01:50:03
                   noteto      sent-successful      1        11/18/2010 00:53:59

Related Link:
Setting up AutoSupport in Clustered Data ONTAP 8.3
Setting up AutoSupport in ONTAP 9

Method 2: 

Enable remote read-only HTTPS access to the root volume of each node.
For information to enable remote read-only HTTPS access, see article 1013814: How to enable remote access to a node’s root volume in a cluster
Note: With Clustered Data ONTAP 8.2.1 and newer versions, remote access is already enabled by default.

Copy the file from the root volume to a local workstation.  The file will be located in the core-dumps folder for the node specified above.
https://<cluster-mgmt-ip>/spi/

Once the file is on a local workstation, it can be uploaded using https://upload.netapp.com.
For more information, see article 1010364: How to upload a core file for analysis

Method 3:

Run the coredump upload command.
A core can be uploaded to NetApp from the storage system, provided it has access to the Internet and FTP is not blocked. The syntax for the command is as follows:
::> coredump upload -node <node_name> -corename <file name> -locationftp://ftp.netapp.com/to-ntap -type kernel -casenum <case_number>

For ONTAP 9 use the below command:
::> system node autosupport invoke-core-upload -uri https//files.company.com -core-filename core.4073000068.2013-09-11.15_05_01.nz -node local

Note: Log in with user name anonymous and the password as any valid email address.
The type and case number fields are specific for the type of core being uploaded (application or kernel), and the specific case number opened for this issue.
The type will be kernel for a system level core file and application for a user space application, also known as ucore.

Related Link:

  • 1015546: How to upload a core file from a down node in clustered Data ONTAP
twitterlinkedinmailtwitterlinkedinmail
Arco

About

View all posts by