In preparation for your CCNA and CCNP exam success, you’ve got to learn to troubleshoot Cisco routers. And while ping is a great basic IP connectivity tool, it doesn’t give you all the information you need to diagnose network connectivity issues.\nLet’s say you have six routers between CityA and CityB. You send a ping from A to B, and get this return:\nR1#ping 22.214.171.124\nType escape sequence to abort.\nSending 5, 100-byte ICMP Echos to 126.96.36.199, timeout is 2 seconds:\n…..\nSuccess rate is 0 percent (0\/5)\nThe five periods indicate that there is no IP connectivity to CityB. Problem is, that’s about all ping tells you. You can have 5 or 50 routers between the two points, so how can you tell which downstream router has the problem?\nThat’s where traceroute comes in. Traceroute sends three datagrams with a Time To Live (TTL) of 1. Those datagrams will timeout once they hit the first router in the path, and that router will respond with an ICMP Time Exceeded message.\nIn response, the sending router sends three more datagrams, but these have a TTL of 2. This means that the next router in line will send back ICMP Time Exceeded messages. This process continues until the final destination (CItyB) is reached the output of the command shows us the path the data took:\nRouter1#traceroute 2188.8.131.52\nType escape sequence to abort.\nTracing the route to 2184.108.40.206\n1 220.127.116.11 4 msec 4 msec 4 msec\n2 18.104.22.168 20 msec 16 msec 16 msec\n3 222.214.171.124 16 msec * 16 msec\nHow does this help troubleshoot a problem? Let’s say that the second router in this path, 126.96.36.199, doesn’t know how to get to 2188.8.131.52. The output would look like this:\nRouter1#traceroute 2184.108.40.206\nType escape sequence to abort.\nTracing the route to 2220.127.116.11\n1 18.104.22.168 4 msec 4 msec 4 msec\n2 22.214.171.124 20 msec 16 msec 16 msec\n3 * * *\nThis indicates that the router at 126.96.36.199 doesn’t know how to get to the final destination. Now you have a better idea of which router has an issue!\nNow here’s the bad part: you’re going to get 30 lines of three asterisks, and until you abort this traceroute, you’re going to just watch those asterisks go across the screen. There’s an abort sequence that the router mentions in the first line of the console output, but the router doesn’t tell you what it is! So I will – this top-secret sequence is TWICE, one right after the other.\nThat keystroke takes a little getting used to, but a CCNA or CCNP can do it! Add this command to your Cisco skill set, and it will serve you well both on the CCNA and CCNP exams and your real-world networks. And you’ll impress your friends by knowing how to stop a traceroute!