AutoSupport delivery is slow and truncated
Applies to
- ONTAP 9.12.1 or later
- AutoSupport
- Transport HTTPS
Issue
- Following an upgrade to ONTAP 9.14.1, noticed that AutoSupports were taking over an hour to process and deliver.
- Once delivered, noticed certain logs missing from the AutoSupport bundle
- Reviewing the Manifest we can see many logs being skipped due to exceeding the time limit
- run
::> manifest show -node * -status *-limit
- run
::> manifest show -node * -status *-limit
(system node autosupport manifest show)
AutoSupport Collected
Node Sequence Body Filename Size Status Error
----------------- --------- -------------- ----------- --------- -----------
Node-02 1052
system-info.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
motherboard-info.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
software_image.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
CLUSTER-INFO.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
diff-svcs.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
effective-cluster-version.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
cluster-version-replicated.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
autosupport.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
autosupport_budget.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
autosupport_history.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
licenses.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
managed-feature.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
vserver-info.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
nwd-config.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
nwd-service-config.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
nwd-resource-config.xml - collection-skipped-trigger-time-limit Collection stopped because the trigger time budget was exceeded
