AutoSupport manifest is reporting collection of files as truncated or skipped after Clustered Data ONTAP 8

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 7,693

Visibility:: Public

Votes:: 3

Category:: data-ontap-8

Specialty:: core

Last Updated:

Applies to

Clustered Data ONTAP 8
ONTAP 9
AutoSupport (ASUP)

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 behaviors:

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.