Analyzing network bottlenecks, issues, and troubleshooting
The problems and troubleshooting discussed in the previous recipes are mostly related, and may result in networking bottleneck issues. Any misbehaving link or router introducing a delay, or a network design with poor capacity planning, may result in bandwidth bottleneck issues, causing end-to-end application performance to suffer.
In this recipe, we will see how to use Wireshark to analyze bottleneck issues.
Getting ready
In order to identify bottleneck issues, we may need to reiterate the capture at multiple locations for analysis and bottleneck isolation. Ideally, packet capture at endpoints will be a good start to identify the application traffic that is impacted, and we then use other tools, such as the ping utility, to possibly narrow down the capture points.
How to do it...
- Filter the capture to display the DNS resolution packets for the application server and check the average time for resolution. This can be viewed by filtering...
