Skip to main content
NetApp Knowledge Base

False positive "AutoSupport message was sent successfully"

  1. Last updated
    Aug 16, 2024
  2. Save as PDF
Views:
281
Visibility:
Public
Votes:
1
Category:
cloud-manager
Specialty:
bluexp
Last Updated:
8/16/2024, 7:01:50 AM

Applies to

  • NetApp Cloud Manager (Connector)
  • NetApp Cloud Volumes ONTAP (CVO)

Issue

  1. Triggering Connector AutoSupports will seemingly succeed:

AutoSupport message was sent successfully

 

  1. Tailing the /opt/application/netapp/cloudmanager/docker_occm/data/log/server.log will show delivery failure:
In this example, a custom rule was set up in order block asups through HTTPS
 
MyConnector ~]$ tail -f server.log
2021-08-05 16:04:54,612 UTC ERROR [                              ] [        ] [             ] [               ] (ForkJoinPool-5-worker-1) [AsupUtility:48] Failed to send AutoSupport file due to connection exception: java.net.ConnectException: connection timed out: support.netapp.com/216.240.21.18:443
java.net.ConnectException: connection timed out: support.netapp.com/216.240.21.18:443

 

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.