How to Obtain and Upload Coredumps and Log Files in Clustered ONTAP 8.2

Note: Methods 1 & 2 do not need CDOT 8.2. Method 3 is written specifically with CDOT 8.2 in mind.

Method 1: To send coredumps via FTP

Note: You will need a NetApp Global Support case open first.

Run these commands:

cMode82::> system node coredump show

cMode82::> system node coredump upload -node cMode82-01 -corename core.1234567890.2013-07-13.03_30_30.nz -location ftp://ftp.netapp.com/to-ntap/ -type kernel -casenum 1234567890

login = anonymous

password = youremail@company.com

Method 2: Locating coredumps and logs via the systemshell and transferring via SCP

# Access system shell and browse /mroot/etc/log

cMode82::> security login unlock -username diag

cMode82::> security login password -username diag

Please enter a new password: XXXXXXXX

cMode82::> set -privilege advanced

cMode82::*> systemshell -node cMode82-01

login: diag

Password: XXXXXXXX

# Browse /mroot/etc/log

cMode82-01% cd /mroot/etc/log

cMode82-01% ls

# Delete any old tar files

cMode82-01% rm *.tar.gz

# ZIP up all the contents of /mroot/etc/log

cMode82-01% tar -czvf cMode82-01-log.tar.gz *.*

# scp the files to an administration host

cMode82-01% scp /mroot/etc/log/cMode82-01-log.tar.gz admin@10.11.12.13:/home/admin/cMode82-01-log.tar.gz

# Browse /mroot/etc/crash

cMode82-01% cd /mroot/etc/log

cMode82-01% ls

# Delete any old tar files

cMode82-01% rm *.tar.gz

# scp the files to an administration host

cMode82-01% scp /mroot/etc/crash/core.1234567890.2013-07-13.03_30_30.nz admin@10.11.12.13:/home/admin/core.1234567890.2013-07-13.03_30_30.nz

# Exit, re-lock diag, and return to priv admin

cMode82-01% exit

cMode82::*> security login lock -username diag

cMode82::*> set -privilege admin

Then upload the files to https://support.netapp.com/upload

Method 3: Using the SPI (Service Processor Infrastructure) to retrieve files via HTTP(S)

All the commands below are run from the Cluster Shell (e.g. cMode82::>)

See: https://kb.netapp.com/support/index?page=content&id=1012580

1. Confirm the IP address and firewall of the cluster management lif:

network interface show -role cluster-mgmt -fields address,firewall-policy

2. Confirm web services are enabled and online:

system services web show

3.  Confirm the firewall policy used by the cluster management LIF allows http(s):

system services firewall policy show -policy mgmt

4. Confirm spi web services are enabled for the cluster management vserver and all any desired node management vservers:

vserver services web show -name spi

5. Enable web services if necessary:

vserver services web modify -vserver cMode82 -name spi -enabled true

6. Confirm the cluster user account is configured for http access method:

security login show -username admin -application http

7. Confirm (and if necessary create) admin access-control role for spi web service:

vserver services web access create -role admin -name spi -vserver cMode82

vserver services web access show -type admin -role admin -name spi

8.  Access the files with an html browser at -

http(s)://cluster-mgmt-ip/spi/node-name/etc/log

http(s)://cluster-mgmt-ip/spi/node-name/etc/crash

- to download. 

Image: Clustered ONTAP /etc/crash Available over HTTP

Image: Clustered ONTAP /etc/log Available over HTTP