Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapmirror_transfer_speed_is_extremely_slow
      Applies to SnapMirror Issue Those destination clusters that were moved to the new IDC or initially created from new IDC all experienced the SnapMirror performance degradation issue The ONTAP resource ...Applies to SnapMirror Issue Those destination clusters that were moved to the new IDC or initially created from new IDC all experienced the SnapMirror performance degradation issue The ONTAP resource usage and the network throughput are very low The status of the cluster peer is healthy
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_do_you_determine_the_most_specific_route_ONTAP_9.2_and_later_versions_will_use
      To determine the most specific route(s) to the destination, run the following command from the ONTAP CLI:​​​​​​ From the available routes determine which route has the "narrowest" (most-specific or sm...To determine the most specific route(s) to the destination, run the following command from the ONTAP CLI:​​​​​​ From the available routes determine which route has the "narrowest" (most-specific or smallest) subnet that the destination IP will fit into. The process is similar in IPv6, but instead of a specifiying a netmask (or more formally, a subnet mask) to define a subnet it use a network prefix; the larger the prefix the smaller the subnet.
    • 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/How_to_modify_a_gateway_or_route_for_a_Vserver
      Applies to ONTAP 9 Description In ONTAP 9, routes cannot be modified and must be removed and created.
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Adding_static_route_fail_with_Malformed_network_configuration_on_xxx__Invalid_type__expected_array_but_found
      Applies to Element OS 12.2 Issue Adding static route fails with errors : Malformed network configuration on xxxx: Invalid type: expected array but found { xxx } on NodeUI. Example :
    • https://kb.netapp.com/hybrid/StorageGRID/Maintenance/StorageGRID_admin_network_subnets_lost_after_node_reboot
      Applies to NetApp StorageGRID Admin network subnet lists Issue After a node is rebooted, the user noticed that the routes for admin network (eth0) were gone. The network config located under /etc/netw...Applies to NetApp StorageGRID Admin network subnet lists Issue After a node is rebooted, the user noticed that the routes for admin network (eth0) were gone. The network config located under /etc/network/config.json shows null value for admin network subnet lists (routes). "eth1": { "subnets": null