Skip to main content
NetApp Knowledge Base

E-Series DBM BACKUP AutoSupport and AOD are not delivered due to IPv6 connection

Views:
72
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • AutoSupport protocol is HTTPS or HTTP
  • Configured HTTP proxy server uses IPv6 connection

Issue

  • E-Series DBM BACKUP AutoSupport and AutoSupport OnDemand(AOD) are not delivered even though DAILY and WEEKLY AutoSupport are delivered without errors
  • Alert message is sent and resolved in a short time everyday
  • ASUP-TRANSMISSION-LOGS shows that the delivery of DBM Backup fails by 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.

  • Output in web-server-trace-log-B.txt shows that AUTO_SUPPORT_DISPATCH for AUTO_SUPPORT_LFT_CHUNK is failed due to 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 is not delivered and ASUP-TRANSMISSION-LOGS shows that 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.

 

  • Was this article helpful?