Skip to main content
NetApp Knowledge Base

E-Series HTTPs AutoSupport delivery fails with a proxy server configured

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

Applies to

  • Netapp E-Series
  • SANtricity OS 11.70.3 or later

Issue

  • Unable to dispatch ASUPs via HTTPS through a proxy server.
  • The E-Series Web server logs (web-server-trace-log-B.txt) indicate the AutoSupport delivery is failing due to socket read/write failure:
2023-10-03 14:32:31,030 INFO [SMMonitorTask-42] trace [ASUPTask.java:1282] [requestId=0, deviceId=N/A] ASUP task start, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_DAILY_SCHEDULE
2023-10-03 14:32:31,075 INFO [SMMonitorTask-42] trace [ASUPHTTPClient.java:945] [requestId=0, deviceId=N/A] Connecting to HTTP proxy server: xx.xx.xx.100:80, IP xx.xx.xx.100
2023-10-03 14:32:31,115 INFO [SMMonitorTask-42] trace [ASUPHTTPClient.java:951] [requestId=0, deviceId=N/A] Proxy tunnel to server: support.netapp.com:80
2023-10-03 14:32:32,727 INFO [SMMonitorTask-42] trace [ASUPHTTPClient.java:945] [requestId=0, deviceId=N/A] Connecting to HTTP proxy server: xx.xx.xx.100:80, IP xx.xx.xx.100
2023-10-03 14:32:32,766 INFO [SMMonitorTask-42] trace [ASUPHTTPClient.java:951] [requestId=0, deviceId=N/A] Proxy tunnel to server: support.netapp.com:80
2023-10-03 14:32:32,808 INFO [SMMonitorTask-42] trace [ASUPHTTPClient.java:1367] [requestId=0, deviceId=N/A] Reading file '/msw_data/data/monitor/supportdata/pending/BUNDLE.Daily.6D039EA000390E460000000062693213.Array_NAME.1696343205185.7z' and writing to output stream
2023-10-03 14:32:53,008 ERROR [SMMonitorTask-42] trace [ASUPHTTPClient.java:749] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller 0  at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:749)
Caller 1  at smmonitor.asup.ASUPTask.dispatchAutoSupportBundle(ASUPTask.java:1695)
Caller 2  at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1386)
Caller 3  at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1290)
Caller 4  at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:44)
java.net.SocketException: Connection reset by peer (Write failed)

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.