Skip to main content
NetApp Knowledge Base

How to manage Data ONTAP 8.2 AutoSupport subsystem size and time budgets

  1. Last updated
  2. Save as PDF
Views:
151
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
7dot
Last Updated:

Applies to

  • Data ONTAP 8.2 (7-mode)

Description

This article provides the procedure to manage the Data ONTAP AutoSupport subsystem size and time budgets.

Note: For specific AutoSupport budget guidance on Data ONTAP 8.2 , refer to AutoSupport can truncate on collection or delivery.

  • AutoSupport has real-world time and size constraints. As Data ONTAP grows in functionality, so does the amount of content collected and delivered in AutoSupport messages. Certain mail servers will drop e-mail messages that have exceedingly large attachments (5MB or greater), and some Web servers have file upload size limitations, too. Users expect storage systems to be able to generate AutoSupport data quickly, with minimal impact to their data serving workflows, and with minimal bandwidth requirements.
  • The AutoSupport Collection Framework organizes all content by subsystems. AutoSupport enforces time and size limits during collection to prevent  subsystem content (i.e. commands, tables and files) from not allowing other subsystem content to be collected. If a subsystem exceeds its allotted budget, AutoSupport will halt the collection for that subsystem and move the next subsystem.
  • Once the collection is finished, AutoSupport delivery budgets control the maximum size of the resulting AutoSupport compressed payload archive. There are two delivery size limits: one for SMTP and the other for HTTPS.
  • If the size of an AutoSupport archive exceeds this size limit, some content will be dropped. During delivery, the content gets added to the archive in the order of priority recorded in the manifest, until the limit is reached.

 

 

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.