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.0 is on R1, connected to the other Ethernet (out the other side than that which connects to R2 and R3). So, it's weird all right. There's probably more to the story. Thanks, Priscilla At 10:22 PM 3/6/02, Scott H. wrote: >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 was listed as "possibly down" in the >route table. After the flush timer expired, I see: > >00:08:14: RT: garbage collecting entry for 10.0.0.0 > >IOS: >System image file is "flash:/c2500-ins-l.120-18.bin" > >If you notice, the route gets deleted before it enters holddown. I would >suggest that he puts a loopback on R1 to use as the test subnet as in theory >he can still reach the ethernet segment between R1 and R2 even if R1 is >shutdown. > >HTH, >Scott > >""Scott H."" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > 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 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 if you do a show ip route with the network number, i.e. show ip >route > > > 10.0.0.0. > > > > > > What version of RIP are you using? What version of IOS? > > > > > > Thanks. > > > > > > Priscilla > > > > > > At 06:56 PM 3/6/02, Scott H. wrote: > > > >I set this up really quick and had it working. Here is my setup: > > > > > > > >R1----R2 > > > > > > > >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 Priscilla > > > >said) on R2: > > > > > > > >R 10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 > > > >C 192.1.1.0/24 is directly connected, Serial0 > > > > > > > > > > > >After all the timers expired, the route dropped out of the table. > > > > > > > >C 192.1.1.0/24 is directly connected, Serial0 > > > > > > > >HTH, > > > >Scott > > > > > > > >""Jerry P."" wrote in message > > > >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > > 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 using a crossover cable. > > > > > > > > > > Jerry > > > ________________________ > > > > > > Priscilla Oppenheimer > > > http://www.priscilla.com ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=37519&t=37455 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
