Skip to main content
NetApp Knowledge Base

ONTAP AutoSupport Networking resolution guide

Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport
  • Transport
    • HTTP
    • HTTP(s)
    • SMTP
  • Networking


This guide will help you identify the proper solution based on your networking issue.

For example:

  • Operation timed out
  • No route to host
  • couldn't connect errors

These indicate that either ONTAP is using an invalid route or it could not obtain a route.

  • Review the LIF and route configuration to ensure ONTAP is using the management interface. (node mgmt and cluster mgmt LIF)

For a smoother experience, run the following command to gather your Nodes configuration

Verify your current configuration

::>autosupport show -node <node name> -instance

Node: cluster-01

State: enable
SMTP Mail Hosts: mailhost
From Address:
List of To Addresses:,
List of Noteto Addresses: -
List of Partner Addresses: -
Send AutoSupport Messages to Vendor Support: enable
Protocol to Contact Support: HTTP or HTTPS
Support Proxy URL:

Verify Connectivity is good
cluster1::> system node autosupport check show -node node2
                            On Demand
Node             HTTP/HTTPS Server     SMTP       Configuration
---------------- ---------- ---------- ---------- -------------
node2            ok         ok         ok         ok
Connectivity fails
  • If connectivity fails, you must check connections and firewall rules are allowed to reach


Networking error Solution
Operation timed out
  • LibCurl Error (6): Couldn't resolve host name
  • Error: Could not resolve host
  • message: Couldn't resolve host ''
failed to connect to 2620:10a:4005:c000::a78:2d11: No route
to host

This can usually be ignored.  If you are using IPv6 for your Admin SVM, then this is relevant .. otherwise it is just a symptom of a routing issue, either IP config, routing or hostname resolution.

message: connect to port 443 failed: Connection refused


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

This is an internal KB article and its content should not be copy/pasted and shared with people outside of NetApp. Always seek Duty Manager authentication of caller for password reset requests. If you need further assistance post a question in Knowledge Xchange