Page 236 Troubleshooting 90030500B
Examples of printout generated by the traceroute command
The following example includes replies from all intermediate Gateways:
traceroute nis.nsf.net
traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte
packet
1 helios.ee.lbl.gov (128.3.112.1) 19ms 19ms 0ms
2 lilac-dmc.Berkeley.EDU (128.3.216.1) 39ms 39ms 19ms
3 lilac-dmc.Berkeley.EDU (128.3.216.1) 39ms 39ms 19ms
4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39ms 40ms 39ms
5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39ms 39ms 39ms
6 128.32.197.4 (128.32.197.4 ) 40ms 59ms 59ms
7 131.119.2.5 (131.119.2.5) 59ms 59ms 59ms
8 129.140.70.13 (129.140.70.13) 99ms 99ms 80ms
9 129.140.71.6 (129.140.71.6) 139ms 239ms 319ms
10 129.140.81.7 (129.140.81.7) 220ms 199ms 199ms
11 nic.merit.edu (35.1.1.48) 239ms 239ms 239ms
Note:
Lines 2 and 3 are the same. This may be due to a fault on the second system,
causing it to forward packets with zero TTL.
The following example shows the result if some gateways do not respond to probe
packets:
traceroute allspice.lcs.mit.edu
traceroute to allspice.lcs.mit.edu (18.26.0.115),30 hops max
1 helios.ee.lbl.gov (128.3.112.1) 0ms 0ms 0ms
2 lilac-dmc.Berkeley.EDU (128.3.216.1) 19ms 19ms 19ms
3 lilac-dmc.Berkeley.EDU (128.3.216.1) 39ms 19ms 19ms
4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 19ms 39ms 39ms
5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 20ms 39ms 39ms
6 128.32.197.4 (128.32.197.4 ) 59ms 119ms 39ms
7 131.119.2.5 (131.119.2.5) 59ms 59ms 39ms
8 129.140.70.13 (129.140.70.13) 80ms 79ms 99ms
9 129.140.71.6 (129.140.71.6) 139ms 139ms 159ms
10 129.140.81.7 (129.140.81.7) 199ms 180ms 300ms
11 129.140.72.17 (129.140.72.17) 300ms 239ms 239ms
12 * * *
13 128.121.54.72 (128.121.54.72) 259ms 499ms 279ms
14 * * *
15 * * *
16 * * *
17 * * *
18 ALLSPICE.LCS.MIT.EDU (18.26.0.115) 339ms 279ms 279ms
Response time to
probe packets
To Next Page
Loading...
Need help?
General