Skip to main content
NetApp Knowledge Base

AutoSupport manifest is reporting collection of files as truncated or skipped in ONTAP 9

Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport


In certain scenarios, AutoSupport data can be truncated on collection and delivery.

  • Truncation can potentially hinder proactive and reactive support capabilities if certain content in an AutoSupport collection is found to be missing.
  • This might be because the content is too large to fit within the size budget constraints.
  • To determine if AutoSupport data is being truncated, run:

::> manifest show -node * -status *-limit

To review a previous AutoSupport Seq, run:

::> system autosupport manifest show -seq-num 14 -fields prio-num,body-file,subsys,status,error,size-collected -subsys mhost -node local
node    seq-num prio-num subsys body-file    size-collected status                          error
------- ------- -------- ------ ------------ -------------- ------------------------------- -----
node-01 14      39       mhost  rdb_dump.txt 1KB            collection-truncated-size-limit ""
node-01 14      40       mhost  cluster_ha.xml
                                             730B           collection-truncated-size-limit ""

The manifest information of the AutoSupport message will include one of the following error collection codes:

  • collection-truncated-size-limit
  • collection-skipped-size-limit
  • collection-truncated-time-limit
  • collection-skipped-time-limit
  • delivery-skipped-size-limit

Expected behavior

  • Some files (e.g. log files) have individual size budgets for AutoSupport collection.
  • If a file collection is truncated because of a file-specific limit, the manifest status for this condition is collection-truncated-file-size-limit.
  • This truncation is expected behavior and can be ignored.
    • Budgets for specific files are hard-coded and not configurable.


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.
Scan to view the article on your device