RIP question [7:37455]
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 like such: 0---0---0 My goal is to have one of the routers go in holddown state after shutting down an interface of a connecting router. So I type in debug ip routing and clear ip route * expecting to get a routing table update of the router going in holddown then eventually gets flushed out of the table. However, with this network, it only shows that the network (or route) is deleted from the table and seems to not put it into holddown state. Is there something wrong with my network? Am I missing something? Any help on this would be greatly appreciated. Thanks! Jerry Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37455t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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 like such: 0---0---0 My goal is to have one of the routers go in holddown state after shutting down an interface of a connecting router. So I type in debug ip routing and clear ip route * expecting to get a routing table update of the router going in holddown then eventually gets flushed out of the table. However, with this network, it only shows that the network (or route) is deleted from the table and seems to not put it into holddown state. Is there something wrong with my network? Am I missing something? Any help on this would be greatly appreciated. Thanks! Jerry Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37456t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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 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 like such: 0---0---0 My goal is to have one of the routers go in holddown state after shutting down an interface of a connecting router. So I type in debug ip routing and clear ip route * expecting to get a routing table update of the router going in holddown then eventually gets flushed out of the table. However, with this network, it only shows that the network (or route) is deleted from the table and seems to not put it into holddown state. Is there something wrong with my network? Am I missing something? Any help on this would be greatly appreciated. Thanks! Jerry Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37457t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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=7i=37460t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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 R1. Go to R3 and watch the route table. After the dead time expires you should see the route listed as possibly down. Jerry P. wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... 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=7i=37461t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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, connec 02:26:26: RT: add 192.1.1.0/24 via 193.1.1.1, rip 02:26:29: is_up: 1 state: 4 sub state: 1 line: 1 Debug ip rip works on this, it's just that nothing happens with debug ip routing? What the heck?!!! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37467t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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 that's causing non-standard behavior. Also are you using RIPv1 or RIPv2. Maybe some of the debug tools only work with RIPv1?? Also, remember my cynical comment. The debug tools are to help Cisco QA debug the software, not to help network administrators troubleshoot. ;-) I think you said these were connected via Ethernet which means you could easily put a protocol analyzer on the network(s) and figure out what's really going on. Try Ethereal. It's fre. Priscilla At 03:27 PM 3/6/02, Jerry P. wrote: 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, connec 02:26:26: RT: add 192.1.1.0/24 via 193.1.1.1, rip 02:26:29: is_up: 1 state: 4 sub state: 1 line: 1 Debug ip rip works on this, it's just that nothing happens with debug ip routing? What the heck?!!! Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37477t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: RIP question [7:37455]
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 speed auto ! interface Serial0/0 no ip address shutdown ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface Serial0/1 no ip address ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 192.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 login ! end hostname r2 ! memory-size iomem 25 ip subnet-zero ! interface FastEthernet0/0 ip address 192.1.1.2 255.255.255.0 duplex auto speed auto ! interface Serial0/0 no ip address shutdown no fair-queue ! interface FastEthernet0/1 ip address 193.1.1.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1 no ip address shutdown clockrate 200 ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 192.1.1.0 network 193.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 ! end hostname r3 ! memory-size iomem 25 ip subnet-zero ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface Serial0/0 no ip address shutdown no fair-queue clockrate 200 ! interface FastEthernet0/1 ip address 193.1.1.2 255.255.255.0 duplex auto speed auto ! interface Serial0/1 no ip address shutdown clockrate 200 ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 193.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 ! end Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37482t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: RIP question [7:37455]
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, this wouldn't be the case. A serial interface notices when the other side goes down, but Ethernet might not, depending on the physical layer you're using. How are R1 and R2 connected, by the way?) Here's what you need to do: Configure R1's other Ethernet port (fa0/1) with an address from another network. Be sure to add that network to R1's RIP statement. Now use that fa0/1 interface in your test. Shut it down. That will cause R1 to send a triggered update out its fa0/0 interface (hopefully) and cause R2 and R3 to put the route into holddown. Hope that makes sense. Let us know if it works! Thanks. Priscilla At 05:17 PM 3/6/02, Jerry P. wrote: 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 speed auto ! interface Serial0/0 no ip address shutdown ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface Serial0/1 no ip address ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 192.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 login ! end hostname r2 ! memory-size iomem 25 ip subnet-zero ! interface FastEthernet0/0 ip address 192.1.1.2 255.255.255.0 duplex auto speed auto ! interface Serial0/0 no ip address shutdown no fair-queue ! interface FastEthernet0/1 ip address 193.1.1.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1 no ip address shutdown clockrate 200 ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 192.1.1.0 network 193.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 ! end hostname r3 ! memory-size iomem 25 ip subnet-zero ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface Serial0/0 no ip address shutdown no fair-queue clockrate 200 ! interface FastEthernet0/1 ip address 193.1.1.2 255.255.255.0 duplex auto speed auto ! interface Serial0/1 no ip address shutdown clockrate 200 ! interface Serial0/2 no ip address shutdown clockrate 200 ! interface Serial0/3 no ip address shutdown clockrate 200 ! router rip network 193.1.1.0 ! ip classless no ip http server ! ! line con 0 transport input none line aux 0 line vty 0 4 ! end Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37489t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: RIP question [7:37455]
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 Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37494t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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 Priscilla said) on R2: R10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 C192.1.1.0/24 is directly connected, Serial0 After all the timers expired, the route dropped out of the table. C192.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 Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37496t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: RIP question [7:37455]
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.0 Did it do this right away? Also what did the routing table show? You can also do a specific lookup by doing show ip route 154.1.0.0. Also, can you do a show ip protocol. Here's what my R3 shows. What does your show? r3#show ip protocol Routing Protocol is rip Sending updates every 30 seconds, next due in 24 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Redistributing: rip Routing for Networks: 192.168.30.0 193.1.1.0 Routing Information Sources: Gateway Distance Last Update 193.1.1.1120 0:00:04 Distance: (default is 120) All I can say is that I tried to reproduce your problem of the route not going into holddown, and I couldn't. On my ancient routers running IOS 11.0 and RIPv1, the route goes into holddown on R3 and R2. This happens whether I disconnect the cable on R1 or shut down its Ethernet interface 1. Using an analyzer, I see that R1 sends a triggered update listing 154.1.0.0 as 16 hops away out its e0 interface (the one connected to R2 in my lab). R1 does this immediately when I do a shutdown. It takes a while when I yank the cable. And here's what I see on R3: (ALL IS FINE AT FIRST) r3#show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default Gateway of last resort is not set R3.0.0.0 [120/2] via 193.1.1.1, 00:00:26, Serial0 C192.168.30.0 is directly connected, Ethernet0 R154.1.0.0 [120/2] via 193.1.1.1, 00:00:26, Serial0 R192.1.1.0 [120/1] via 193.1.1.1, 00:00:27, Serial0 C193.1.1.0 is directly connected, Serial0 r3#debug ip routing IP routing debugging is on (I YANKED THE CABLE ON R1 HERE) r3# RT: delete route to 154.1.0.0 via 193.1.1.1, rip metric [120/2] RT: no routes to 154.1.0.0, entering holddown r3#show ip route 154.1.0.0 Routing entry for 154.1.0.0 255.255.0.0 Known via rip, distance 120, metric 4294967295 (inaccessible) Redistributing via rip Advertised by rip (self originated) Last update from 193.1.1.1 on Serial0, 00:02:02 ago Hold down timer expires in 72 secs r3#show ip route 154.1.0.0 Routing entry for 154.1.0.0 255.255.0.0 Known via rip, distance 120, metric 4294967295 (inaccessible) Redistributing via rip Advertised by rip (self originated) Last update from 193.1.1.1 on Serial0, 00:03:21 ago Hold down timer expires in 0 secs r3# RT: 154.1.0.0 came out of holddown r3# (I PUT THE CABLE BACK ON R1 HERE) RT: add 154.1.0.0 255.255.0.0 via 193.1.1.1, rip metric [120/2] r3#show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default Gateway of last resort is not set R3.0.0.0 [120/2] via 193.1.1.1, 00:00:08, Serial0 C192.168.30.0 is directly connected, Ethernet0 R154.1.0.0 [120/2] via 193.1.1.1, 00:00:08, Serial0 R192.1.1.0 [120/1] via 193.1.1.1, 00:00:09, Serial0 C193.1.1.0 is directly connected, Serial0 r3# (I MOVED CONSOLE CABLE TO R1 HERE) r1#config t Enter configuration commands, one per line. End with CNTL/Z. r1(config)#int e1 r1(config-if)#shut r1(config-if)# (I MOVED THE CONSOLE CABLE BACK TO R3 HERE) r3# r3#show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default Gateway of last resort is not set R3.0.0.0 [120/2] via 193.1.1.1, 00:00:11, Serial0 C192.168.30.0 is directly connected, Ethernet0 R154.1.0.0 is possibly down, routing via 193.1.1.1, Serial0 R192.1.1.0 [120/1] via 193.1.1.1, 00:00:12, Serial0 C193.1.1.0 is directly connected, Serial0 r3#show ip route 154.1.0.0 Routing entry for 154.1.0.0 255.255.0.0 Known via rip, distance 120, metric 4294967295 (inaccessible) Redistributing via rip Advertised by rip (self originated) Last update from 193.1.1.1 on Serial0, 00:00:30 ago Hold down timer expires in 157 secs So.. that's all I can tell you. It works on my routers, but they are ancient. ;-) Priscilla
Re: RIP question [7:37455]
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: 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 Priscilla said) on R2: R10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 C192.1.1.0/24 is directly connected, Serial0 After all the timers expired, the route dropped out of the table. C192.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 Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37503t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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: 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 Priscilla said) on R2: R10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 C192.1.1.0/24 is directly connected, Serial0 After all the timers expired, the route dropped out of the table. C192.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 Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37513t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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: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: 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 Priscilla said) on R2: R10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 C192.1.1.0/24 is directly connected, Serial0 After all the timers expired, the route dropped out of the table. C192.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 Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=37514t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RIP question [7:37455]
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: 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 Priscilla said) on R2: R10.0.0.0/8 is possibly down, routing via 192.1.1.1, Serial0 C192.1.1.0/24 is directly connected, Serial0 After all the timers expired, the route dropped out of the table. C192.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=7i=37519t=37455 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
