![]() ![]() If the pattern originates somewhere in between the first and last row, the problem is probably outside your local network then contact the NOC it could be problems on the international circuitįigure 2 Problems outside your network begin in the middle. If the pattern starts on the first row in the graph (your router), you’re probably dealing with an internal network problem.įigure 1 Internal problems begin on the first hop Where the pattern begins, helps you understand the source of the problem. Do you notice any patterns leading up to the final destination? When you have an idea of what’s happening on the final destination, it’s time to look at the rows leading up to the final destination. If you are using a Windows platform, start up pingplotter and enter the name of a target destination in the Address to Trace Window. If you see high latency on your final destination, you’ve probably captured a network problem Follow the pattern to the source Steps: 1.Start up Wireshark and begin packet capture (Capture->Start) and then press OK on the Wireshark Packet Capture Options screen 2. The further to the right the black line is the longer it takes for data travel around the network. What about the black line? It shows how long it takes data to travel to your target and back. ![]() This effect is known as packet loss, and if you’re seeing it on the final destination, there’s a good chance you captured a problem. Because you're only taking 100 samples, these will be. Also, since you want to look at all your samples, you can change 'Samples to include' to 0 (ALL) or 100. The tech probably wants 1 ping per second, so change 'Trace Interval' to 1 second. Do you see a red bar? If so, that means some data was lost between your computer and the target. To stop it at 100, change ' of times to trace' to 100. The final destination is the bottom row of the trace graph Check for packet loss PingPlotter represents the final destination with the bottom row of the trace graph. Understanding PingPlotter graphs begins with the final destination. Let’s take a closer look and see what the graph tells us about the source of your network problem. If you have an Android OS device, you'll need to run this test using a desktop computer with Windows or macOS. ![]() You’ve captured something in PingPlotter that looks like evidence of a network problem. This article will show you how to how to run a ping test and traceroute using PingPlotter 5 Free, a third-party application available on Windows, macOS and iOS. This write-up covers the basic features of the graphs and their interpretation. The big question is do you understand these graphs. PingPlotter Pro can be used to trace to multiple different targets within the same instance (and each target’s configuration can be independently managed, too). Once an institution is facing problems they are prompted to share their results with the NOC for interpretation. This is a tool used by the RENU community to troubleshoot network issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |