ping, and troubleshooting…

the premier tool to identify a problem on an internetwork is ping…  one of the major tenets of the tshoot exam is your ability to use ping to pinpoint where a problem lies… you’ll note on the cisco tshoot demo that trace (tracert) is only available at the client, and only available to trace to the far end webserver, 209.65.200.241… in this environment, tracert is virtually useless… from the client side, ipconfig is your vetting tool…

of course, once you’ve narrowed down the problem with ping, show commands will help you identify the problem… if you rely on sh run, you are doing yourself a disservice…

debug, while very useful, is no help here on the demo, and should be used very carefully in production…

any network guy who is unable to pinpoint a problem in an internetwork using these basic commands should find another line of work immediately…

if you require 3rd party tools to pinpoint an internetwork problem, pack it up, baby…

http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1902.html

Troubleshooting Tools


 

This chapter presents information about the wide variety of tools available to assist you in troubleshooting your internetwork. This includes information on using router diagnostic commands, Cisco network management tools, and third-party troubleshooting tools.

Using Router Diagnostic Commands

Cisco routers provide numerous integrated commands to assist you in monitoring and troubleshooting your internetwork. The following sections describe the basic use of these commands:

The show commands help monitor installation behavior and normal network behavior, as well as isolate problem areas.

The debug commands assist in the isolation of protocol and configuration problems.

The ping commands help determine connectivity between devices on your network.

The trace commands provide a method of determining the route by which packets reach their destination from one device to another.