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 see high latency on your final destination, you’ve probably captured a network problem Follow the pattern to the source 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. Do you see a red bar? If so, that means some data was lost between your computer and the target. 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. ![]() You’ve captured something in PingPlotter that looks like evidence of a network problem. This write-up covers the basic features of the graphs and their interpretation. The big question is do you understand these graphs. 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. |