Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/LIF_is_unable_to_reach_gateway
      LIF is unable to reach gateway, it is timing out. [  6067] TCP connection to ip 172.xx.xx.xx, port 445 failed: No route to host. [  6069] TCP connection to ip 172.xx.xx.xx, port 445 failed: No route t...LIF is unable to reach gateway, it is timing out. [  6067] TCP connection to ip 172.xx.xx.xx, port 445 failed: No route to host. [  6069] TCP connection to ip 172.xx.xx.xx, port 445 failed: No route to host. [  6072] TCP connection to ip 172.xx.xx.xx, port 445 failed: No route to host. Note: In the above examples, Gateway is configured to be on 192.168.1.1, LIF is configured for 192.168.1.0/24 network, indicating it should be in the same subnet, thus a subnetting mistake is ruled out.
    • https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/AIQUM_Cluster_monitoring_fails_Enter_a_valid_Hostname_or_Port
      Applies to ActiveIQ Unified Manager (UM) (version and OS unrelated) ONTAP 9 Issue Trying to add a cluster with HTTPS or monitor an existing cluster within UM fails with error: Failed to fetch the HTTP...Applies to ActiveIQ Unified Manager (UM) (version and OS unrelated) ONTAP 9 Issue Trying to add a cluster with HTTPS or monitor an existing cluster within UM fails with error: Failed to fetch the HTTPS certificate from <cluster_ip> Enter a valid Hostname or Port. HTTP discovery also fails, even if HTTP is enabled on the cluster with error: Unable to communicate with cluster <cluster_ip>