Look at this tracert... What do you think?

agustinchernitsky

Hey guys,

Look at this:

1     7 ms     1 ms     1 ms  192.168.0.17
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    19 ms    11 ms     7 ms  publica1.fibertel.com.ar [24.232.1.1]
  5     *        *        *     Request timed out.
  6    17 ms    11 ms    52 ms  bai2-cablevision-2-ar.bai.seabone.net [195.22.22
0.53]
  7   283 ms   307 ms   307 ms  ash1-new1-racc1.new.seabone.net [195.22.216.225]

  8   231 ms   307 ms   307 ms  sbc-2-us-ash2.ash.seabone.net [195.22.206.34]
  9     *      474 ms   307 ms  ded1-fa5-1-0.miamfl.sbcglobal.net [66.10.1.243]

 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *      571 ms  ded1-fa0-1-0.miamfl.sbcglobal.net [66.10.1.227]

 14   390 ms   307 ms   926 ms  bb2-g1-3-0.miamfl.sbcglobal.net [66.10.1.226]
 15   238 ms     *        *     ded1-fa0-1-0.miamfl.sbcglobal.net [66.10.1.227]

 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18  1133 ms     *        *     bb2-g1-3-0.miamfl.sbcglobal.net [66.10.1.226]
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.

Its a route from my home to a customer in the US (Miami exactly). Well, it seems to be a loop there no? Maybe a link went down and the routers are converging or they really have another problem that a CCNA doesn't know yet

What do you make of this guys? I would love some coments!

Smallguy

obviously an issue with a router but what it is exactly I have no idea.

this is obviously something that u cna reproduce and wasn't just a router that got over loaded.

but in terms of narrowing it down Im' very interested in this answer

EdTheLad

Maybe a link went down and since the route to the destination is not in the routing table the default-route just happens to point back to the originating router.The * in the output could be due to an mpls core.

blargoe

Do a pathping to the same destination, you will probably be able to find exactly which router is having the problem

agustinchernitsky

Yep... it seems there was a route problem (ie line down). Now it's up and running:

Tracing route to 66.10.10.254 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.0.17
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    22 ms    14 ms     7 ms  publica1.fibertel.com.ar [24.232.1.1]
  5     *        *        *     Request timed out.
  6    36 ms     7 ms    48 ms  bai2-cablevision-2-ar.bai.seabone.net [195.22.22
0.53]
  7   257 ms   214 ms   215 ms  ash1-new1-racc1.new.seabone.net [195.22.216.225]

  8   212 ms   215 ms   214 ms  sbc-2-us-ash2.ash.seabone.net [195.22.206.34]
  9   364 ms   244 ms   220 ms  ded1-fa5-1-0.miamfl.sbcglobal.net [66.10.1.243]

 10   245 ms   405 ms   409 ms  OOR-1121889.cus
t-rtr.swbell.net [66.10.230.110]
 11   240 ms   273 ms   235 ms  66.10.10.254