Loop?

Though you Guys would gete a kick out of this, one of our branch offices was unreachable this morning, this is what i got for a trace route.

5 4.71.248.9 60 msec 20 msec 20 msec
6 * * *
7 4.53.98.6 20 msec 20 msec 30 msec
8 64.50.232.134 40 msec 40 msec 40 msec
9 64.50.232.129 30 msec 40 msec 40 msec
10 64.50.232.130 40 msec 30 msec 30 msec
11 64.50.232.129 40 msec 30 msec 30 msec
12 64.50.232.130 40 msec 50 msec 30 msec
13 64.50.232.129 40 msec 40 msec 40 msec
14 64.50.232.130 40 msec 30 msec 40 msec
15 64.50.232.129 40 msec 40 msec 30 msec
16 64.50.232.130 40 msec 40 msec 40 msec
17 64.50.232.129 40 msec 30 msec 40 msec
18 64.50.232.130 40 msec 40 msec 40 msec
19 64.50.232.129 40 msec 30 msec 40 msec
20 64.50.232.130 40 msec 50 msec 30 msec
21 64.50.232.129 40 msec 40 msec 30 msec
22 64.50.232.130 40 msec 40 msec 40 msec
23 64.50.232.129 40 msec 30 msec 40 msec
24 64.50.232.130 40 msec 30 msec 40 msec
25 64.50.232.129 40 msec 30 msec 40 msec
26 64.50.232.130 30 msec 50 msec 40 msec
27 64.50.232.129 30 msec 40 msec 30 msec
28 64.50.232.130 40 msec 40 msec 40 msec
29 64.50.232.129 30 msec 40 msec 40 msec
30 64.50.232.130 40 msec 40 msec 30 msec

Find more posts tagged with

Comments

Chris_

Ha - I probably shouldn't laugh, but I always smile when I see that fly up the screen - even when it's my job to fix it.

rinoel

johnwest43 wrote: »

Though you Guys would gete a kick out of this, one of our branch offices was unreachable this morning, this is what i got for a trace route.

5 4.71.248.9 60 msec 20 msec 20 msec
6 * * *
7 4.53.98.6 20 msec 20 msec 30 msec
8 64.50.232.134 40 msec 40 msec 40 msec
9 64.50.232.129 30 msec 40 msec 40 msec
10 64.50.232.130 40 msec 30 msec 30 msec
11 64.50.232.129 40 msec 30 msec 30 msec
12 64.50.232.130 40 msec 50 msec 30 msec
13 64.50.232.129 40 msec 40 msec 40 msec
14 64.50.232.130 40 msec 30 msec 40 msec
15 64.50.232.129 40 msec 40 msec 30 msec
16 64.50.232.130 40 msec 40 msec 40 msec
17 64.50.232.129 40 msec 30 msec 40 msec
18 64.50.232.130 40 msec 40 msec 40 msec
19 64.50.232.129 40 msec 30 msec 40 msec
20 64.50.232.130 40 msec 50 msec 30 msec
21 64.50.232.129 40 msec 40 msec 30 msec
22 64.50.232.130 40 msec 40 msec 40 msec
23 64.50.232.129 40 msec 30 msec 40 msec
24 64.50.232.130 40 msec 30 msec 40 msec
25 64.50.232.129 40 msec 30 msec 40 msec
26 64.50.232.130 30 msec 50 msec 40 msec
27 64.50.232.129 30 msec 40 msec 30 msec
28 64.50.232.130 40 msec 40 msec 40 msec
29 64.50.232.129 30 msec 40 msec 40 msec
30 64.50.232.130 40 msec 40 msec 30 msec

Can you tell us more about your Topology...

johnwest43

sure.....

|

VPN

|

Main office ----> ISP

> Branch

PROBLEM

rinoel

johnwest43 wrote: »

sure.....

|
VPN
|

Main office ----> ISP
> Branch
^
^
PROBLEM

Any running configs about Main office and Branch ???

Forsaken_GA

I'm assuming this is resolved by now, but if you ever see it again, check the CEF table and see if it's all torqued up. That's been the culprit of the last few routing loops I've seen.

johnwest43

turns out it was a telco line issue, we are all set now. What i dont get is that when a line goes down like that traceroute usally shows a timeout. Must have been some goofy routing issues with the telco.

ehnde

johnwest43 wrote: »

turns out it was a telco line issue, we are all set now. What i dont get is that when a line goes down like that traceroute usally shows a timeout. Must have been some goofy routing issues with the telco.

They're not going to tell you exactly what happened. Better for them that you assume it was an "unavoidable technical issue". It's a liability issue

But yeah, they screwed up...probably fat fingered a configuration.