メインコンテンツまでスキップ

IPv6接続が原因でEシリーズのDBMバックアップAutoSupportとAODが配信されない

Views:
6
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg<a>2009603748</a>
Last Updated:

環境

  • Eシリーズ
  • AutoSupportプロトコルはHTTPSまたはHTTPです。
  • 設定されたHTTPプロキシサーバがIPv6接続を使用する

問題

  • 毎日または毎週のAutoSupportがエラーなく配信されているにもかかわらず、EシリーズのDBMバックアップAutoSupportとAutoSupport OnDemand(AOD)が配信されない
  • アラートメッセージが毎日短時間で送信されて解決される
  • ASUP-TRANSMISSION-LOGS は、DBMバックアップの配信が次の方法で失敗することを示しています。 AutoSupport message dispatch failed.

Priority:INFO, ASUP Message Type:DBM Backup, ASUP Task Type:Delivery, Status:FAILED, Storage Array:<ARRAY>, SAID:<SAID>, Chassis Serial Number:<SERIAL_NO>, Thread ID:346,211, Delivery Method:HTTPS, Sequence Number:118, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message dispatch failed.

  • の出力 web-server-trace-log-B.txtAUTO_SUPPORT_DISPATCH 、の AUTO_SUPPORT_LFT_CHUNK が原因で失敗したことを示しています。 ASUP message upload failed, null status code

INFO [SMMonitorTask-791] trace [ASUPTask.java:1282] [requestId=0, deviceId=N/A] ASUP task start, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_DBM_FILE
INFO [SMMonitorTask-791] trace [ASUPHTTPClient.java:983] [requestId=0, deviceId=N/A] Connecting to HTTPS proxy server: <PROXY_SERVER:PORT>, IP <PROXY_IP>
INFO [SMMonitorTask-791] trace [ASUPHTTPClient.java:990] [requestId=0, deviceId=N/A] Proxy tunnel to server: support.netapp.com:443
INFO [SMMonitorTask-790] trace [ASUPCollectionService.java:45] [requestId=0, deviceId=N/A] Array CSB collection is starting, file: /msw_data/data/monitor/supportdata/draft/BUNDLE.<FILE>.7z
INFO [SMMonitorTask-791] trace [ASUPTask.java:1301] [requestId=0, deviceId=N/A] ASUP task complete, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_DBM_FILE, status: SUCCESS
INFO [ASUPLFTWorker-1] trace [ASUPTask.java:1282] [requestId=0, deviceId=N/A] ASUP task start, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_LFT_CHUNK
INFO [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:983] [requestId=0, deviceId=N/A] Connecting to HTTPS proxy server: <PROXY_SERVER:PORT>, IP <PROXY_IP>
INFO [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:990] [requestId=0, deviceId=N/A] Proxy tunnel to server: support.netapp.com:443
INFO [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:983] [requestId=0, deviceId=N/A] Connecting to HTTPS proxy server: <PROXY_SERVER:PORT>, IP <PROXY_IP>
INFO [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:990] [requestId=0, deviceId=N/A] Proxy tunnel to server: support.netapp.com:443
INFO [SMMonitorTask-790] trace [ASUPStatusFile.java:224] [requestId=0, deviceId=N/A] Autosupport status file generation start time: 1687290164503
INFO [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:1367] [requestId=0, deviceId=N/A] Reading file '/msw_data/data/monitor/supportdata/pending/BUNDLE.Dbmfile.<FILE>.7z' and writing to output stream
ERROR [ASUPLFTWorker-1] trace [ASUPHTTPClient.java:697] [requestId=0, deviceId=N/A] ASUP message upload failed, null status code
Caller+0    at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:697)
Caller+1    at smmonitor.asup.ASUPTask.dispatchLFTChunk(ASUPTask.java:1563)
Caller+2    at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1376)
Caller+3    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1290)
Caller+4    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:44)
ERROR [ASUPLFTWorker-1] trace [ASUPTask.java:1591] [requestId=0, deviceId=N/A] Dispatching ASUP Bundle is failed
Caller+0    at smmonitor.asup.ASUPTask.dispatchLFTChunk(ASUPTask.java:1591)
Caller+1    at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1376)
Caller+2    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1290)
Caller+3    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:44)
Caller+4    at smmonitor.shared.AbstractTask$1.call(AbstractTask.java:112)
INFO [ASUPLFTWorker-1] trace [ASUPTask.java:1301] [requestId=0, deviceId=N/A] ASUP task complete, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_LFT_CHUNK, status: FAIL

  • AODが配信されず、 ASUP-TRANSMISSION-LOGS AutoSupport message delivery failed. Server returned HTTP status code: null.

Priority:CRITICAL, ASUP Message Type:AOD Request, ASUP Task Type:AOD Poll, Status:FAILED, Storage Array:<ARRAY>, SAID:<SAID>, Chassis Serial Number:<SERIAL_NO>, Thread ID:350,500, Delivery Method:HTTPS, Sequence Number:119, Delivery URI:support.netapp.com/aods/asupmessage, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message delivery failed. Server returned HTTP status code: null.

 

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.

 

  • この記事は役に立ちましたか?