Sprint Help

Thu Mar 18 16:59:43 UTC 2004

Joe,

You are, in fact, barking up the wrong tree. The question should be ³when I
test against my destination, am I seeing packet loss and latency?².
Traceroute is not a useful tool for determining the state of an intermediate
router on a path. ICMP TTL-Exceeded messages are rate limited and not
handled as expeditiously as forwarded packets going THROUGH a modern router.
Why? Because core routers have limited CPU, control bus, and other
resources. 

Traceroute is (but is not always) useful for:

* Determining which routers and carriers your packets are passing through
* Figuring out where there is congestion on a path (this is iffy, doesn't
always work, and assumes that there is actually congestion, not other things
going on). Not the tool of choice for this, but sometimes the only thing
you've got.

Remember, if you really had packet loss or increased latency on the 8th hop,
it would show up on all the other, upstream hops, and the destination.

-- 

Daniel Golding
Network and Telecommunications Strategies
Burton Group

On 3/18/04 11:33 AM, "Joe Marr" <joe.marr at intektechnologies.com> wrote:

> I was wondering if the wonderful members of this list could provide their
> opinions regarding the traceroute below. I have contacted sprint several times
> regarding this issue and their noc keeps coming back with ³no trouble found².
> Am I barking up the wrong up the wrong tree?
> 
> I¹m experiencing packetloss and large amounts of delay at hop 8. Both of my T
> providers say they cant do anything to help me.
> 
> C:\>tracert 67.97.251.18
> 
> 
> Tracing route to 67.97.251.18 over a maximum of 30 hops
> 
> 1   <10 ms   <10 ms   <10 ms  192.168.1.75
> 2    16 ms    15 ms    16 ms  host-64-179-34-81.pit.choiceone.net [64.179.34.8
> 1]
> 3    15 ms    16 ms    15 ms  atm6-5-992-pitb-isp-cisco.choiceone.net [64.65.2
> 10.101]
> 4    31 ms    31 ms    16 ms  chi-edge-09.inet.qwest.net [63.149.3.229]
> 5    31 ms    16 ms    31 ms  chi-core-03.inet.qwest.net [205.171.20.125]
> 6    15 ms    32 ms    31 ms  chi-brdr-03.inet.qwest.net [205.171.20.142]
> 7    16 ms    31 ms    31 ms  205.171.1.162
> 8   297 ms   375 ms    94 ms  sl-bb20-chi-4-0.sprintlink.net [144.232.8.219]
> 9    47 ms    47 ms    47 ms  sl-browing-20-0.sprintlink.net [144.223.241.22]
> 
> 10    47 ms    46 ms    63 ms  ge-2-1-0.a1.chcg.broadwing.net [216.140.15.17]
> 11    47 ms    63 ms    47 ms  so-0-1-0.c1.gnwd.broadwing.net [216.140.14.97]
> 12    47 ms    62 ms    47 ms  so-2-0-0.c1.wash.broadwing.net [216.140.16.22]
> 13    47 ms    62 ms    63 ms  p0-0-0.a1.wash.broadwing.net [216.140.8.13]
> 14    47 ms    63 ms    62 ms  p8-0-0.e0.wash.broadwing.net [216.140.8.34]
> 15   141 ms   125 ms  141 ms  67.97.250.166
> 16    *       *        *     Request timed out.
> 17    *        *       *     Request timed out.
> 18    *       *        *     Request timed out.
> 19    *       *        *     Request timed out.
> 20    *       *        *     Request timed out.
> 21    *       *        *     Request timed out.
> 22    *        *       *     Request timed out.
> 23    *       *        *     Request timed out.
> 24    *       *        *     Request timed out.
> 25    *       *        *     Request timed out.
> 26    *       *        *     Request timed out.
> 27    *        *       *     Request timed out.
> 28    *       *        *     Request timed out.
> 29    *       *        *     Request timed out.
> 30    *       *        *     Request timed out.
> 
> Trace complete.
> 
> C:\>
> Joe Marr (joe.marr at intektechnologies.com
> <mailto:joe.marr at intektechnologies.com> )
> Sr. Technology Consultant
> Intek Technologies
> 
> Phone: 1.570.322.1915
> www.intektechnologies.com <http://www.intektechnologies.com>
> 
> 