Example: troubleshooting a slow network connection

The real-time reporting provided by performance monitors can provide both the raw data and the data trend analysis that can help you isolate network problems. For example, we recently experienced a problem with a network connection between two of our Ipswitch office sites. This example shows how we used Performance Monitors to troubleshoot the slow network connection.

Scenario:

A developer working in Augusta, GA on an Atlanta-based project complained of a slow network connection between the Augusta and Atlanta offices. He stated it took 40 minutes to check in files to the source library over the T1 connection.

The Atlanta office network administrator reacted by completing the following steps:

1. On the WhatsUp Gold web interface, he accessed the Monitoring tab to select the Ping Response Time report.
2. From the Ping Response Time report, he checked the connection from the Atlanta WhatsUp Gold application to the Augusta primary server. The report showed an increased response time beginning at 11:45 a.m.

This connection was previously configured with the appropriate Performance Monitors and had accumulated data for several weeks. This data enabled the administrator to accurately narrow down the possible cause of the problem to the primary server connection. He was then able to troubleshoot that specific connection and take steps to fix the slowness issue.

To set up this type of monitor for a connection, configure the Ping Latency and Availability monitor on a device located on the other end of the connection. For more information, see Learning about network monitors.

See Also Custom Peformance Monitors Creating global custom performance monitors Creating device-specific custom performance monitors Example: monitoring router bandwidth