メインコンテンツへスキップ

ONTAPを9.13.1以降にアップグレードするとAutoSupportの配信が遅くなる

Views:
29
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

環境

  • ONTAP 9 .13.1以降
  • AutoSupport
  • 転送HTTPS

問題

  • ONTAP 9 .14.1へのアップグレード後、AutoSupportの処理と配信に1時間以上かかることに気づきました。 
    • 配信後、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.