Investigating Routing Problems

In this video, get tips on how to troubleshoot routing issues.

Tony Fortunato

December 13, 2017

1 Min Read
Network Computing logo

As networks evolve, I find that some IT teams overlook routing issues. Their attitude is "if it ain’t broke, don’t fix it." Routing problems don’t necessarily result in dramatic outages, so IT teams are apt to ignore them.

When troubleshooting suspected routing issues, the obvious first step for a network analyst is to perform a trace route from his or her computer. However, results will vary, depending on where you investigate the problem.

In this video, I show the various results I got when troubleshooting a routing issue.


I recommend performing the traceroute from the client's subnet, computer, or better yet from any layer 3 (or higher) device. Don’t be fooled by a layer 2 switch since many of the corporate class switches can route as well.

Different types of routing protocols behave differently. The protocol will influence how you approach troubleshooting routing issues.  

About the Author(s)

Tony Fortunato

Sr Network Performance Specialist

Tony Fortunato is a network performance expert who has been designing, implementing and troubleshooting networks since 1989. His company, The Technology Firm, provides clients of all sizes with services ranging from project management, network design, consulting, troubleshooting, designing custom-designed training courses, and assisting with equipment installation. Tony's experience in networking started with financial trading floor networks and ISPs, where he learned to integrate and support equipment from various vendors. Tony has taught and presented at numerous colleges and universities, public forums and private classes. He blogs frequently at NetworkDataPediaand has a popular YouTube channel.

Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like

More Insights