I traced a routing loop

aueddonline

i used the trace command on a route that had a loop, how do I stop it tracing ?

aueddonline

1 10.1.1.130 4 msec 4 msec 4 msec
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * *
R2_2611xm#
[Resuming connection 1 to 5.5.5.5 ... ]
*
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


oh it stopped

aueddonline

what's the escape sequence?

dtlokee

use the default beak sequence which is "control + shift + 6" all at the same time.

aueddonline

crap it wasn't a loop I was trying to trace a sunbent address

kryolla

The routing protocol does a good job on preventing loops. It is when you do two way redistribution loops occur or route feed back.

aueddonline

getting sleeply, i'm going to make a loop tomorrow

dtlokee

Yeah you just traced to and invalid destination, if it were a loop then it would show the same router hops over and over between all the routers in the loop.

cisco_trooper

kryolla wrote:

The routing protocol does a good job on preventing loops. It is when you do two way redistribution loops occur or route feed back.

Heh. Redistribution is a fantastic way to introduce routing loops.

GT-Rob

Or you hit a firewall :P


ctrl + shift + 6 is your friend.

ctrl + C is your unix friend

cisco_trooper

If you want lots of fun try applying some distribute-lists on ISIS.

aueddonline

the trouble with ctrl 6 X, was that I has already telneted in fro on of the other routers so all it did was logout from the session

dtlokee

aueddonline wrote:

the trouble with ctrl 6 X, was that I has already telneted in fro on of the other routers so all it did was logout from the session

Don't hit "x" and it shouldn't escape and do the "control + shift + 6" 2 times, the first one is captured by the term server and the second one goes through.