Skip to main content
NetApp Knowledge Base

How to upload a Data ONTAP 7-Mode core file for analysis

  1. Last updated
    Apr 25, 2025
  2. Save as PDF
Views:
2,336
Visibility:
Public
Votes:
2
Category:
data-ontap-7
Specialty:
7dot
Last Updated:
4/25/2025, 8:37:15 AM

Applies to

  • Data ONTAP 7 and earlier    
  • Data ONTAP 8.1 7-Mode    
  • Data ONTAP 8.2 7-Mode    
  • Data ONTAP 8 7-Mode 

Description

This document describes the procedure on how to upload a Data ONTAP 7-Mode core file for analysis.

When a system panic or crash occurs, the memory contents are saved as core files on the system. NetApp can analyze these core files to diagnose the reason for the panic and suggest corrective action.

Note: If the file is not a core file (for example, a Windows event log, a messages log, or Perfstat), proceed to the 'Upload the core file' section below.

For information on uploading a clustered Data ONTAP core file, see KB  How to upload a Data ONTAP 8.x Cluster-Mode core file for analysis

Procedure

Verify that the core file is valid

Run the savecore -l (check mode) command on the storage system. If the proper panic string appears in the output, then the core file header is intact and can be read by NetApp (although it could still be incomplete). In the absence of a core file, obtain the related EMS and audit logs.
 

Prepare the core file for upload

On a CIFS or NFS licensed storage system, complete the following steps to prepare a core file for upload and analysis: 

  1. If a NetApp case was not automatically created when the storage system panicked, open a case with NetApp Support by phone or Web. 
  2. From the CIFS or NFS admin host, navigate to the /etc/crash directory. Locate the most recent core file using its timestamp and save it to the admin host.
  3. Rename the core file so that it contains the case number, using the following naming convention:

[Case_number].core.[Sequence_number].[datestamp].[timestamp].nz

Core file timestamps might not relate to the time that the storage system experienced a panic. Cores are written with a GMT timestamp, but should be converted to the local time zone where the storage system is set, when identifying the correct core file to upload.

For example, if the core file name is core.2.2011-03-04.08_53_25.nz and the case number is '2000123456', rename the core.2.2011-03-04.08_53_25.nz file to 2000123456.core.2.2011-03-04.08_53_25.nz.

Note: Any other file that you need to upload can be renamed in this fashion. Prepending the case number to the file name helps speed the identification of the file and expedite the analysis process.

Caution:Do not use ZIP, compress or modify the core file. Upload the file 'as is' - it is already compressed. Changing or splitting this file in any way might delay the core analysis.

If CIFS or NFS is not installed on the storage system, use either of the following options to get the file onto another local machine:

Option 1

Follow these steps to easily download cores using the HTTP administrative Web interface. 

  1. Set options httpd.admin.enable on
  2. Set options httpd.autoindex.enable on
  3. If HTTP admin access from particular hosts needs to be limited, set options httpd.admin.access host=<name>,<IP-address>,...
  4. In a Web browser, go to http://filername_or_ip/na_admin/cores, and download the core file.

Note: If either of the above options are not turned on, you will get an HTTP error and the URL referenced above will not be available.

Option 2

Using FTP, you can easily download any cores you need. 

  1. Enable FTP access on the storage system:
    options ftpd.enable on
  1. Set the default home directory to /etc/crash:
    options ftpd.dir.override /vol/vol0/etc/crash
  1. Connect to the storage system using FTP from a local client. Before running the FTP command, be sure to note the local directory you are in. This is the where the core file will be located when you get it.
  2. Run the ls command to find the necessary file. For this example, the core file is named core.2.nz.
  3. Run the get command to upload the core file to your local computer:
    get core.2.nz
  1. Terminate the FTP session.
  2. Turn off FTP access on the storage system.
    options ftpd.enable off
  1. Make sure that you are in the directory that the file is in, then rename the file using the naming convention specified above. 

Note: Do not upload the mini-core file unless specifically requested to do so by NetApp Global Support.

Upload the core to NetApp 

 

Additional Information

 

 

 

 

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.