How to Troubleshoot Packet Loss with Ping Command

Packet loss is a common problem in the IP networks. Ping, although simple, is an excellent tool in order to troubleshoot packet loss issues. This post describes how we can detect packet loss in a network using the ping command.

One good way to troubleshoot packet loss issues is to define a large number of ping counts (for example 500) when using the ping command. In this way, it is more possible to catch random packet loss and its pattern will be clearly distinguished by the dots among the exclamation marks. An example of a ping output with packet loss in a Cisco router is shown in the picture below:

ping output with packet loss

You can see in the picture that the ping count is set to 300, and 81% packet loss is detected in the network.

You can even stress the network further by defining a different ICMP packet size close to the MTU size (for example 1300 bytes). This could be helpful in some cases of network congestion or rate limiting implementations since more processing in needed for larger packets.

When ICMP rate limiting is configured in the network, then there is usually a symmetric pattern of packet loss in the ping output -since there is a fixed rate of accepted ICMP packets configured-, so this should give you a hint.

Now if there is indeed packet loss, how can we detect where in the network it happens, especially if there are a lot of router hops in between? There are different ways to do this. For example, a traceroute can help to see if there is some strange behavior between hops in the path, e.g. latency. One other way would be to try to investigate the connectivity hop-by-hop, for example try to ping from the source router to each router (hop) in the path separately and check in that way towards which router packet loss appears when pinging.

However, in cases of asymmetric routing (where the path from source to destination is different from the path from destination back to the source) the packet loss can be caused because of some problem in the path on the way back (from the destination to the source). In these cases, you probably also need to check the other path too.

This post described some tips on how to troubleshoot packet loss in the network by using the ping command. Later posts will provide further information and details on how to troubleshoot packet loss or other network issues with ping command.

Related articles

How to Troubleshoot High Latency with Traceroute Command

How a Router Selects the Best Route


About TelcoNotes

IP & VoIP networking

Posted on March 15, 2013, in IP Routing and tagged , , , , . Bookmark the permalink. 1 Comment.

  1. Could you please share more links or examples that is if you have them, on how to troubleshoot packet loss using ping and traceroute command. Also if you can include some network diagrams (network topology).

    I recently joined Internet Access Provider (IAP), we provide layer 2 services to ISP’s who in turn provides Internet Service Provider Services to last mile customers. Most of the tickets that I get from ISP’s is packet loss and high latency logged to ISP’s by their last mile customers. The worst part is I have less experience troubleshooting packet loss and high latency.

    I would want something to back me up especially when responding to ISP engineers who would have logged tickets with us as the upstream provider.
    Like for example, I would have established that our network portion is not the one causing packet losses or high latency on their end.

    What else can I advise ISP Engineers to check on their routers and the Customer Edge router CE?

    Really appreciate your help.

Leave a Comment

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: