Skip to main content
NetApp Knowledge Base

AutoSupport rastrace skipped after stats collection exceeds time budget

  1. Last updated
  2. Save as PDF
Views:
6
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Autosupport

Issue

  • From Autosupport MANIFEST.XML session, one node takes significantly longer than another node to collect cm-stats-event-data.tar.
  • cm-stats-event-data.tar collection takes 361 seconds on nodeA
  • The collection exceeds the AutoSupport performance time budget of 5 minutes.
  • The next artifact, rastrace-qos-rbr.tgz, is skipped with the status:collection-skipped-time-limit
  • A peer node, nodeB, collects a similar cm-stats-event-data.tar artifact in about 61 seconds.
  • The stats directory size and file count are similar between nodes:
  • nodeA: about 235,000 files and 22GB
  • nodeB: about 275,000 files and 23GB
  • Other AutoSupport collection items also take several times longer on nodeA than on nodeB.

 

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.