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/on-prem/ontap/da/NAS/NAS-KBs/After_ONTAP_reboot_LIFs_are_inaccessible_when_static_ARP_entries_are_present
      Applies to ONTAP 9 Issue Following an ONTAP reboot (such as an upgrade), some LIFs are inaccessible from one or more clients Pings between impacted LIFs and clients fail Filer-side packet traces do no...Applies to ONTAP 9 Issue Following an ONTAP reboot (such as an upgrade), some LIFs are inaccessible from one or more clients Pings between impacted LIFs and clients fail Filer-side packet traces do not show evidence of clients responding to outbound traffic from the filer