ONTAP AutoSupport (Transport HTTPS) Delivery Failure Resolution Guide
Applies to
- ONTAP 9
- AutoSupport
- Transport
- HTTPS
Description
See below for instructions on how to resolve AutoSupport issues related to Delivery or Transmission failures with the transport protocol configured as HTTPS.
Procedure
- Verify the current configuration
cluster1::> autosupport show -node <node name> -instance
Node: cluster1-1a
State: enable
SMTP Mail Hosts: mailhost
From Address: admin@email.com
List of To Addresses: address1@email.com,address2@email.com
List of Noteto Addresses: -
List of Partner Addresses: -
Send AutoSupport Messages to Vendor Support: enable
Protocol to Contact Support: HTTPS
Support Proxy URL:
...
Note: If Protocol to Contact Support
is set to SMTP and not HTTPS, refer to the SMTP Delivery Failure Resolution Guide
- Verify Connectivity
cluster1::> system node autosupport check show-details -node cluster1-1a
Node: cluster1-1a
Category: https
Component: https-put-destination
Status: failed
Detail: HTTPS PUT connectivity check failed for destination:
https://support.netapp.com/put/AsupPut/. Error: Timeout
was reached when connecting to the server -
'support.netapp.com'
Corrective Action: Possible network configuration issue. Ensure that you
have network connectivity Component: https-post-destination
Status: failed
Detail: HTTPS POST connectivity check failed for destination:
https://support.netapp.com/asupprod/post/1.0/postAsup.
Error: Timeout was reached when connecting to the server
- 'support.netapp.com'
Corrective Action: Possible network configuration issue. Ensure that you
have network connectivity
...
Category: on-demand
Component: ondemand-server
Status: failed
Detail: AutoSupport OnDemand connectivity check failed for
destination:
https://support.netapp.com/aods/asupmessage. Error:
Timeout was reached when connecting to the server -
'support.netapp.com'
Corrective Action: Possible network configuration issue. Ensure that you
have network connectivity
Category: configuration
Component: configuration
Status: ok
Detail: No configuration issues found.
5 entries were displayed.
-
Review the table below to find a Solution with a matching Error description
Error | Solution |
---|---|
|
|
|
|
|
-
(Optional) The output of notifyd.log may contain additional information:
cluster1::> node run -node (node name) -command rdfile /etc/log/mlog/notifyd.log
- copy the output to your favorite text editor
- To locate the error: Use ctrl F and search
In most cases you may start from the following line (message: Closing connection #0)
and work up to the true error message.
Use the following Table for additional messages to look for in notifyd.log:
Error | Solution |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other Useful Commands:
- Review AutoSupport History
cluster1::> system autosupport history show -node * -fields node ,seq-num ,status ,error ,destination
seq-num destination status error
------- ----------- ------ -----
39 smtp ignore ""
39 http transmission-failed
39 noteto ignore ""
38 smtp ignore ""
38 http sent-successful ""
38 noteto ignore ""
Additional Information
- Troubleshoot AutoSupport message delivery over HTTPS (ONTAP Documentation)
- ONTAP AutoSupport Resolution Guide
- What are "HTTP PUT" response codes?
- When working with NetApp Support or a Partner, we recommend that you manually upload a full AutoSupport to expedite the resolution process.