To troubleshoot these issues, we first need to understand how packets are dropped, how we can detect these events, and how we can resolve them. Yes. Despite the maturity of network links to 10Gbps and beyond, packet loss is still an underlying network event that impacts applications today. Network packet loss: are we still coping with that today? This way, TCP can detect if a packet goes missing and resend it accordingly, ensuring reliable transmission of data. Part of the function of establishing a connection is creating the mechanism to track data that has been sent and acknowledge what is received. These are typically labelled as “discards” on interfaces.Īs we have seen in this series, TCP is a connection-oriented protocol. The sender of the traffic will determine the loss occurred and retransmit. On these connections, the egress link may not be able to keep up with the amount of ingress traffic, which may result in dropped packets. Traffic congestion can cause input/output discards on interface links, especially when translating between link speeds (10Gbps to 1Gbps for example).

In most cases, an error counter will be incremented on the interface, which helps when locating where the loss occurred.

If a frame becomes errored from point to point on a connection due to cabling issues, duplex problems, or other layer 1 events, the receiver will determine that the data is corrupted and drop it. The two most common causes of network packet loss are:

This is the third article of our series on TCP, covering all that you need to know to troubleshoot performance problems impacting business critical applications. After considering how TCP opens and closes connections, we will now examine problems that can happen to a connection in progress, specifically network packet loss.

Wireshark tcp retransmission