Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • Why does a lot of small files take longer to transfer than few large files?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Why_does_a_lot_of_small_files_take_longer_to_transfer_than_few_large_files
      When transferring files, typical applications will copy over a single file at a time Each of the file creations requires several metadata operations to occur before the file has been written completel...When transferring files, typical applications will copy over a single file at a time Each of the file creations requires several metadata operations to occur before the file has been written completely With smaller files, the write portion can complete without ever reaching the bandwidth capacity of the link In the graph below you can see that the bytes in flight stayed near capacity with a large file, and the transfer rate is very sporadic with small file transfer.
    • How to Ping in NetApp Cloud Volumes ONTAP for Azure
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/How_to_Ping_in_NetApp_Cloud_Volumes_ONTAP_for_Azure
      Applies to NetApp Cloud Volumes ONTAP for Azure Description According to Microsoft's Azure documentation, the ICMP protocol is not permitted through the Azure load balancer, which will cause network p...Applies to NetApp Cloud Volumes ONTAP for Azure Description According to Microsoft's Azure documentation, the ICMP protocol is not permitted through the Azure load balancer, which will cause network pings to fail.
    • What does error 'Nblade.invTcpRecordMarker' mean?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_does_error_Nblade.invTcpRecordMarker_mean
      This error is logged in EMS when one of three invalid TCP record markers is received: Invalid reason is TCP_FRAGMENT, invalid record marker is x. Invalid reason is TCP_DATA_LENGTH_OVERFLOW, invalid re...This error is logged in EMS when one of three invalid TCP record markers is received: Invalid reason is TCP_FRAGMENT, invalid record marker is x. Invalid reason is TCP_DATA_LENGTH_OVERFLOW, invalid record marker is x. Nblade.invTcpRecordMarker:error]: Invalid TCP record marker received from remote IP address x.x.x.x on local port xxxx. Invalid reason is TCP_DATA_LENGTH_UNDERFLOW, invalid record marker is x.
    • Do both UDP and TCP connections count towards the 100,000 connection limit per node?
      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
    • How to measure Round Trip Time in Wireshark
      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).
    • NFS hangs due to half-open TCP session
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_hangs_due_to_half-open_TCP_session
      NFS mount point hangs due to firewall in between client and ONTAP
    • Frequent nfsConnResetAndClose error due to packet sent using the wrong port
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Frequent_nfsConnResetAndClose_error_due_to_packet_sent_using_the_wrong_port
      Applies to ONTAP 9 NFS v3 Issue Event log shows frequent nfsConnResetAndClose error messages The reason listed in the error message is Packet is sent using the wrong port: Example: Wed Sep 30 14:31:19...Applies to ONTAP 9 NFS v3 Issue Event log shows frequent nfsConnResetAndClose error messages The reason listed in the error message is Packet is sent using the wrong port: Example: Wed Sep 30 14:31:19 CEST [Node-01: kernel: Nblade.nfsConnResetAndClose:error]: Shutting down connection with the client. Vserver ID is 3; network data protocol is NFS, Rpc Xid 0x-750XXXXX; client IP address:port is 10.10.10.11:300. local IP address is 10.10.10.20; reason is Packet is sent using the wrong port.