Re: RIP question [7:37455]

2002-03-06 Thread Priscilla Oppenheimer
Yup, that's what I see too. He doesn't see "entering holddown." Here's what he sees according to a previous message from him: r3#debug ip routing IP routing debugging is on r3# 05:25:49: RT: del 154.1.0.0 via 193.1.1.1, rip metric [120/2] 05:25:49: RT: delete network route to 154.1.0.0 154.1.0.

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
Also, make sure you are looking at the debug at R3. R1 won't show this same info.. ""Scott H."" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Here is the debug: > > 00:04:10: RT: metric change to 10.0.0.0 via 192.1.1.1, rip metric [120/1] > new metric [120/-1] > 00:04:

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
Here is the debug: 00:04:10: RT: metric change to 10.0.0.0 via 192.1.1.1, rip metric [120/1] new metric [120/-1] 00:04:10: RT: delete route to 10.0.0.0 via 192.1.1.1, rip metric [120/4294967295 ] 00:04:10: RT: no routes to 10.0.0.0, entering holddown As soon as this happened, the route w

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
When it is listed as "possibly down" in the route table, it is in holddown. Running v1 on 12.1 code. ""Priscilla Oppenheimer"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Can you enable debug ip routing on R2? We're trying to see if the route > goes into holddown. (At least I

Re: RIP question [7:37455]

2002-03-06 Thread Priscilla Oppenheimer
Can you enable debug ip routing on R2? We're trying to see if the route goes into holddown. (At least I think that's what the problem is. The route doesn't go into holddown on his network, it just gets deleted.) The easiest way to see this is with debug ip routing. You can also see more info i

RE: RIP question [7:37455]

2002-03-06 Thread Priscilla Oppenheimer
At 06:27 PM 3/6/02, Jerry P. wrote: >When I added a network 154.1.1.0 to router r1 pinged it and shut it down >this is what r3 did: > >r3#debug ip routing >IP routing debugging is on >r3# >05:25:49: RT: del 154.1.0.0 via 193.1.1.1, rip metric [120/2] >05:25:49: RT: delete network route to 154.1.0.

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
I set this up really quick and had it working. Here is my setup: R1R2 R1 has a loopback w/ address 10.1.1.1 and is using the serial to get to R2. After the connection was up and working, I shut down the loopback on R1 and immediately got the following (due to the triggered update as Priscil

RE: RIP question [7:37455]

2002-03-06 Thread Jerry P.
When I added a network 154.1.1.0 to router r1 pinged it and shut it down this is what r3 did: r3#debug ip routing IP routing debugging is on r3# 05:25:49: RT: del 154.1.0.0 via 193.1.1.1, rip metric [120/2] 05:25:49: RT: delete network route to 154.1.0.0 I have ethernet connections from r1 to r2

RE: RIP question [7:37455]

2002-03-06 Thread Priscilla Oppenheimer
R1 won't do anything if you disconnect its fa0/0 interface. Due to split horizon and the fact that it's the only interface configured, it doesn't have anyone to update. Also, R2 probably doesn't notice a problem. I bet its Ethernet interface on that side is still up. (If you were using serial,

RE: RIP question [7:37455]

2002-03-06 Thread Jerry P.
Hi Priscilla: Here are the configs. Not much to 'em, I can ping everywhere, it's just that the routers don't seem to want to put the route into holddown. Thanks for your help! hostname r1 ! ip subnet-zero ! interface FastEthernet0/0 ip address 192.1.1.1 255.255.255.0 shutdown duplex auto

Re: RIP question [7:37455]

2002-03-06 Thread Priscilla Oppenheimer
Can you send us your configs. In theory, Cisco's RIP is supposed to do a triggered update. When R1 loses its connection it should advertise the network as unreachable (16 hops). This should put the route into holddown on the other routers. I'm wondering if you've got some sort of weird configs

Re: RIP question [7:37455]

2002-03-06 Thread Jerry P.
Hi Scott: Ok so I did what you said, shutdown R1 and enable debug ip routing on R3, I waited for 5 minutes and got no output whatsoever: r3#debug ip routing IP routing debugging is on r3# So I cleared ip route * and got this: r3#clear ip route * r3# 02:26:26: RT: add 193.1.1.0/24 via 0.0.0.0,

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
Shutting down the interface will work. However, clearing the route table tells the route process to start over. If it starts over, it has no idea that the route ever existed. Shut down the interface and wait for the timers to expire. For example: R1-R2-R3 Shut down the interface at R

Re: RIP question [7:37455]

2002-03-06 Thread Jerry P.
I tried to disconnect the cable but that delete message still appears. Isn't it possible to just shutdown the interface. Isn't it the same as unplugging the connection? ALso, only when I clear ip route* does any message appears. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
Don't clear the route table either. That defeats the purpose. ""Scott H."" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Unplug one of the cables. > > ""Jerry P."" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Hi all: > > > > I have a question about a RI

Re: RIP question [7:37455]

2002-03-06 Thread Scott H.
Unplug one of the cables. ""Jerry P."" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Hi all: > > I have a question about a RIP lab exercise that I am developing for school > that I was wondering if I could ask you about. I have three routers each > connected through ethernet l