<\/p>\n
One of NetApp’s AutoSupport best practices is to enable the storage system to automatically generate and transmit AutoSupport messages to NetApp using the integrated functionality in Data ONTAP. By enabling AutoSupport automatically, NetApp can provide proactive support through My AutoSupport<\/a>, and reactive support through the NetApp Support Center. The My AutoSupport tool allows users to administer and support their NetApp storage systems with tools such as an AutoSupport data viewer, device visualizer, storage efficiency and health check reports, and Data ONTAP upgrade plan generator.<\/p>\n <\/p>\n For a small number of users, it might not be possible for AutoSupport messages to be sent automatically due to network connectivity limitations. However, the AutoSupport data might be required for Technical Support to efficiently troubleshoot a system failure. In these cases, the AutoSupport data will have to be collected manually. In Data ONTAP 7.x and earlier, a majority of the AutoSupport data was formatted as plain text. However, in Data ONTAP 8.0 and later, AutoSupport data is increasingly being generated in the XML format, which requires an XML viewer to read the data. The switch to XML was done to minimize the size of AutoSupport messages. Additionally, in Data ONTAP\u00a08.0.1 and later, the attachments are encoded in a MIME format when stored in the storage system’s Some support engineers might find it advantageous for the user to manually send AutoSupport data in a way that would allow the NetApp systems such as My AutoSupport or the NetApp SmartSolve Tools Portal to display this data. This article contains the steps to provide AutoSupport as a file upload or in a manner that enables the data to be visible in My AutoSupport.<\/p>\n For more information on enabling AutoSupport, see the AutoSupport<\/a> section on the NetApp Support<\/a> site.<\/p>\n<\/div>\n<\/div>\n<\/div>\n <\/p>\n <\/p>\n Contents<\/strong>:<\/p>\n Data ONTAP\u00a07G storage systems<\/strong><\/a><\/p>\n Data ONTAP 8.0 7-Mode storage systems<\/strong><\/a><\/p>\n Data ONTAP 8.0.x 7-Mode storage systems<\/strong><\/a><\/p>\n Data ONTAP 8.1 7-Mode and later storage systems<\/strong><\/a><\/p>\n Clustered Data ONTAP 8.0 storage systems<\/strong><\/a><\/p>\n Clustered Data ONTAP 8.1 and later storage systems<\/strong><\/a><\/p>\n <\/p>\n Data ONTAP\u00a07G storage systems<\/a>:<\/strong><\/p>\n Perform the following steps to send the AutoSupport to NetApp’s AutoSupport e-mail:<\/p>\n Data ONTAP 8.0 7-Mode storage systems<\/a>:<\/strong><\/p>\n Perform the following steps to send the AutoSupport to NetApp’s AutoSupport email:<\/p>\n Data ONTAP 8.0.x 7-Mode storage systems<\/a>:<\/strong><\/p>\n Perform the following steps to collect an AutoSupport from the storage system and save it in a readable format:<\/p>\n Data ONTAP 8.1 7-Mode and later storage systems<\/strong><\/a>:<\/p>\n\/etc\/log\/autosupport<\/code> directory.<\/p>\nProcedure<\/h3>\n
\n
\/etc<\/code> directory on the storage system’s root volume.
\nNote<\/strong>: This directory can be accessed only as an administrator or root.<\/li>\n\/etc\/log\/autosupport<\/code> path.<\/li>\n\n
\n
YYYYYMMDDHHMM.#<\/code><\/em>.<\/li>\nYYYYYMMDDHHMM.#.files <\/code><\/em>and will contain the following message attachments:\n\n
YYYYYMMDDHHMM.#<\/code><\/em><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.ems.gz<\/code><\/li>\n YYYYMMDDHHMM.<\/code><\/em>#.rc.gz<\/code><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.exports.gz<\/code><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.hosts.gz<\/code><\/li>\nresolv.conf<\/code>: YYYYMMDDHHMM.<\/code><\/em>#.resolv_conf.gz<\/code><\/li>\nnsswitch.conf<\/code>: YYYYMMDDHHMM.<\/code><\/em>#.nsswitch_conf.gz<\/code><\/li>\ncm_stats<\/code>: YYYYMMDDHHMM.<\/code><\/em>#.cm_stats.gz<\/code><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.quotas.gz<\/code><\/li>\nusermap.cfg<\/code>: YYYYMMDDHHMM.<\/code><\/em>#.usermap_cfg.gz<\/code><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.keak_data.gz<\/code><\/li>\nYYYYMMDDHHMM.<\/code><\/em>#.shelf_log_type<\/em>.gz<\/code>
\n<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n
\nExample:
\nThe message on the storage system displays: Tue Feb 1 02:45:05 GMT [asup.post.sent:notice]:\u00a0System Notification message posted to NetApp:\u00a0System Notification from filer01 (USER_TRIGGERED\u00a0(failure))\u00a0INFO
\n<\/code>The related AutoSupport files are 201102010244.0 <\/code>and 200102010244.0.files<\/code>.<\/li>\n<\/ul>\n<\/li>\nYYYYYMMDDHHMM.# <\/code><\/em>file. Copy the contents and paste them into the body of a plain text e-mail.<\/li>\nYYYYYMMDDHHMM.#<\/code><\/em> <\/code>file, attach all the files in the corresponding YYYYYMMDDHHMM.#.files<\/code><\/em> <\/code>directory to the e-mail.<\/li>\ntest <\/code>does not appear anywhere in the following lines:\n\n
options autosupport.doit<\/code><\/li>\n<\/ul>\n<\/li>\n\n
options autosupport.to<\/code><\/li>\nautosupport.from<\/code><\/li>\n<\/ul>\n<\/li>\n <\/code>and paste it into the e-mail subject.
\nExample:
\nsubject=System Notification from filer01 (USER_TRIGGERED\u00a0(failure))\u00a0INFO\u00a0doit=USER_TRIGGERED\u00a0(failure)<\/code><\/li>\n
\nOnce NetApp receives the AutoSupport e-mail, assuming that it is in the correct format, it might take 24 – 48 hours for the initial AutoSupport to be displayed in My AutoSupport on the NetApp Support <\/a>site.
\nNote<\/strong>: Regularly sending AutoSupport messages will decrease this processing time.<\/li>\n<\/ol>\n\n
\/etc<\/code> directory on the storage system’s root volume.
\nNote<\/strong>: This directory can be accessed only as an administrator or root.<\/li>\n\/etc\/log\/autosupport<\/code> path.<\/li>\n\n
\nThe message body of the AutoSupport is the file in the format YYYYYMMDDHHMM.#<\/code><\/em>.
\nThe associated folder will have the name YYYYYMMDDHHMM.#.files<\/code><\/em>. The contents of this folder depend on the type of AutoSupport that generated it.<\/li>\n
\nExample<\/strong>:
\nThe message on the storage system shows: Tue Feb 1 02:45:05 GMT [callhome.invoke:info]: Call home for USER_TRIGGERED\u00a0(fault)
\n<\/code>The related AutoSupport files are 201102010244.0 <\/code>and 200102010244.0.files<\/code>.<\/li>\n<\/ul>\n<\/li>\nYYYYYMMDDHHMM.# <\/code><\/em>file. Copy the contents and paste them into the body of a plain text e-mail.<\/li>\nYYYYYMMDDHHMM.# <\/code><\/em>file, attach all the files in the corresponding YYYYYMMDDHHMM.#.files <\/code><\/em>directory to the e-mail.<\/li>\ntest <\/code>does not appear anywhere in the following lines:\n\n
options autosupport.doit<\/code><\/li>\n<\/ul>\n<\/li>\n\n
options autosupport.to<\/code><\/li>\nautosupport.from<\/code><\/li>\n<\/ul>\n<\/li>\n
\nOnce NetApp receives the AutoSupport e-mail, assuming that it is in the correct format, it might take 24 – 48 hours for the initial AutoSupport to be displayed in My AutoSupport on the NetApp Support Site.
\nNote<\/strong>: Regularly sending AutoSupport messages will decrease this processing time.<\/li>\n<\/ol>\n\n
\/etc<\/code> directory on the storage system’s root volume.
\nNote<\/strong>: This directory can be accessed only as an administrator or root.<\/li>\n\/etc\/log\/autosupport<\/code> path.<\/li>\n\n
\nThe message body of the AutoSupport is the file in the format YYYYYMMDDHHMM.#<\/code><\/em>.
\nThe associated folder will have the name YYYYYMMDDHHMM.#.files<\/code><\/em>. This folder contains a single file in the format YYYYYMMDDHHMM.#<\/code><\/em>.<\/li>\n
\nExample<\/strong>:
\nThe message on the storage system shows: Tue Feb 1 02:45:05 GMT [callhome.invoke:info]: Call home for USER_TRIGGERED\u00a0(fault)
\n<\/code>The related AutoSupport files are 201102010244.0 <\/code>and 200102010244.0.files<\/code>.<\/li>\n<\/ul>\n<\/li>\nYYYYYMMDDHHMM.# <\/code><\/em>file located in\/etc\/log\/autosupport<\/code>.<\/li>\n--netapp mime boundary<\/code>. This starts the mime-encoded section of the AutoSupport file.<\/li>\n--netapp mime boundary <\/code>to the end of the file. Using Notepad or VI, paste this data into a new file. \u00a0Save this file with a .mim<\/code> extension.\n\n
YYYYMMDDHHMM.# <\/code><\/em>file naming format.<\/li>\n201102010244.0<\/code>, the mime-encoded file would be saved as 201102010244.0.mim.<\/code><\/li>\n<\/ul>\n<\/li>\n.gz<\/code> files containing Data ONTAP\u00a0log and configuration files.
\nNote<\/strong>:\u00a0Using WinZip to open the .mim<\/code> file or any of the .gz<\/code> files contained within may result in the following error:
\nWarning:\u00a0Boundary expected on multipart message but found EOF.
\n<\/code>This error can be safely ignored.<\/li>\n\n
201102010244.0 <\/code>and <\/code>201102010244.0.mim.<\/code><\/li>\n\n
\n> autosupport history show<\/code>
\nIf you want to see the matching AutoSupport message type with the sequence number, use the -instance<\/code> parameter with the command.<\/li>\n.7z<\/code>):
\nNote<\/strong>: You must include