Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

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

Views:
4,673
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport

Issue

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.

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support