跳转到主内容

AutoSupport 交付缓慢

Views:
7
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

适用场景

  • ONTAP 9.12.1 或更高版本
  • AutoSupport
  • 传输HTTPS

问题描述

  • 升级到AutoSupport.14.1后、我们注意到ONTAP 9需要一个多小时才能完成处理和交付。 
    • 交付后、注意到AutoSupport包中缺少某些日志
  • 在查看清单时、我们可以看到许多日志因超过时间限制而被跳过
    • 运行 ::> manifest show -node * -status *-limit
::> 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

 

 

 

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.