- ONTAP 9
This article provides the procedure to manage the ONTAP AutoSupport subsystem size and time budgets.
Note: For specific AutoSupport budget guidance on ONTAP 9, refer to AutoSupport can truncate on collection or delivery.
- AutoSupport has both real-world time and size constraints.
- As ONTAP 9 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 on their data serving workflows, and with minimal bandwidth requirements.
- The AutoSupport Collection Framework organizes all contents by subsystems.
- AutoSupport enforces both 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 to 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 contents 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.