Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Do_both_UDP_and_TCP_connections_count_towards_the_100_000_connection_limit_per_node
      Yes, both UDP and TCP traffic contributes to the 100,000 connection limit per node. UDP is considered stateless, but ONTAP holds an internal "connection-id" open for 2 minutes in case another call com...Yes, both UDP and TCP traffic contributes to the 100,000 connection limit per node. UDP is considered stateless, but ONTAP holds an internal "connection-id" open for 2 minutes in case another call comes in on the same ip/port combination When 95% of 100K connection limit is breached, ONTAP begins deleting the Least Recently Used (LRU) UDP CID If new connections outpace the deletion rate, new UDP and TCP connections may see intermittent un-responsiveness
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_measure_Round_Trip_Time_in_Wireshark
      Applies to Any NetApp product Description Network troubleshooting involves many parts. Sometimes a simple ping may not work due to firewalls, ping throttling, etc. It may help to measure round trip ti...Applies to Any NetApp product Description Network troubleshooting involves many parts. Sometimes a simple ping may not work due to firewalls, ping throttling, etc. It may help to measure round trip time to check for things like packet loss, etc., from existing TCP or UDP traffic. An approximate RTT be gathered via a simple ping This article helps use Wireshark to identify Round Trip Time (RTT).
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Input_output_error_when_listing_directory_on_UDP_NFS_mount_in_ONTAP_9
      Applies to ONTAP 9 Issue When mounted via NFS over UDP, the client may display ls: reading directory .: Input/output error when trying to list the contents of a directory.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_UDP_traffic_intermittently_drops_after_upgrade_to_ONTAP_9.2_or_newer
      Mostly the issue is found after ONTAP is upgraded to 9.2 or later, the filer does not reply to every ICMP (ping) request even if it can be found in a packet trace. A strange behavior could be related ...Mostly the issue is found after ONTAP is upgraded to 9.2 or later, the filer does not reply to every ICMP (ping) request even if it can be found in a packet trace. A strange behavior could be related to multiple LIFs on the same port not responding at different times. This issue is affecting the NFS data transfer also if UDP is used as a transport layer causing a huge delay [root@centos-04 /]# mount -t nfs -o vers=3,proto=udp 10.128.242.45:/vol1_svm2 /mnt/vol1_svm2_ontap93