Marko, This is what Cisco documentation says:
Usage Guidelines When triggered extensions to RIP are enabled, routing updates are sent on the WAN only if one of the following events occurs: •The router receives a specific request for a routing update. (Full database is sent.) •Information from another interface modifies the routing database. (Only latest changes are sent.) •The interface comes up or goes down. (Partial database is sent.) •The router is first powered on, to ensure that at least one update is sent. (Full database is sent.) You might want to enable this feature if you are using an on-demand circuit and you are charged for usage time. Fewer routing updates will incur lower usage costs. Entries in the routing database can be either temporary or semipermanent. Entries learned from broadcasts on LANs are temporary; they will expire if not periodically refreshed by more broadcasts. Entries learned from a triggered response on the WAN are semipermanent; they do not time out like other entries. Certain events can cause these routes to time out, such as the interface going down, or if the outgoing interface is the same as the incoming interface. Neighbor updates of the routes with a metric of 16 (infinity) mean the route is unreachable, and those routes are eventually removed from the routing table. In my case it is a point-to-point network between R2 and R4 as one of the question is to have authentication between the two. As per above since my incoming and outgoing interface is the same may be thats why I loose the routes. What should be the work around it? Thanks. Regards, Samir Idris. On Mon, Apr 18, 2011 at 2:27 AM, Samir Idris <[email protected]> wrote: > Marko, > > Below is the configuration without "ip rip triggered": > > R2: > > router rip > version 2 > timers basic 30 180 0 240 > passive-interface default > no passive-interface FastEthernet0/0 > no passive-interface Serial0/1.24 > no passive-interface Serial0/1.25 > no passive-interface Serial0/1.26 > offset-list R8 in 5 > network 0.0.0.0 > no auto-summary > > R2#sh run int s0/1 > Building configuration... > Current configuration : 140 bytes > ! > interface Serial0/1 > no ip address > encapsulation frame-relay > no ip route-cache cef > clock rate 2000000 > no frame-relay inverse-arp > end > > R2#sh run int s0/1.24 > Building configuration... > Current configuration : 180 bytes > ! > interface Serial0/1.24 point-to-point > ip address 150.100.24.2 255.255.255.0 > ip rip authentication key-chain R2R4 > snmp trap link-status > frame-relay interface-dlci 204 > end > > R4: > > router rip > version 2 > timers basic 30 180 0 240 > network 0.0.0.0 > no auto-summary > R4#sh run int s0/0 > Building configuration... > Current configuration : 144 bytes > ! > interface Serial0/0 > no ip address > encapsulation frame-relay > clock rate 2000000 > no frame-relay inverse-arp > frame-relay lmi-type ansi > end > > > R4#sh run int s0/0.1 > Building configuration... > Current configuration : 179 bytes > ! > interface Serial0/0.1 point-to-point > ip address 150.100.24.4 255.255.255.0 > ip rip authentication key-chain R2R4 > snmp trap link-status > frame-relay interface-dlci 402 > end > > Routes on R4 and R2: > > R4#sh ip route | i 0/0.1 > R 100.100.250.0 [120/3] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 200.0.0.8 [120/9] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 200.0.0.9 [120/3] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 200.0.0.5 [120/2] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.220.0/24 [120/2] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.221.0/24 [120/2] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.100.0/24 [120/1] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.91.0/24 [120/3] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.69.0/24 [120/2] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.78.0/24 [120/3] via 150.100.24.2, 00:00:17, Serial0/0.1 > R 150.100.69.9/32 [120/2] via 150.100.24.2, 00:00:17, Serial0/0.1 > C 150.100.24.0/24 is directly connected, Serial0/0.1 > > R2#sh ip route rip | i 0/1.24 > R 150.100.40.0/24 [120/1] via 150.100.24.4, 00:00:05, Serial0/1.24 > R 150.100.41.0/24 [120/1] via 150.100.24.4, 00:00:05, Serial0/1.24 > > Now I am only adding "ip rip triggered" on s0/1.24 (R2) and s0/0.1 (R4) and > I will loose routes on R4: > > R4#sh ip route > Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 > E1 - OSPF external type 1, E2 - OSPF external type 2 > i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS > level-2 > ia - IS-IS inter area, * - candidate default, U - per-user static > route > o - ODR, P - periodic downloaded static route > Gateway of last resort is not set > 100.0.0.0/24 is subnetted, 1 subnets > R 100.100.250.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > 200.0.0.0/32 is subnetted, 3 subnets > R 200.0.0.8/32 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 200.0.0.9/32 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 200.0.0.5/32 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > 150.100.0.0/16 is variably subnetted, 10 subnets, 2 masks > R 150.100.220.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.221.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.100.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.91.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.69.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.78.0/24 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > R 150.100.69.9/32 is possibly down, > routing via 150.100.24.2, Serial0/0.1 > C 150.100.40.0/24 is directly connected, FastEthernet0/0 > C 150.100.41.0/24 is directly connected, FastEthernet0/1 > C 150.100.24.0/24 is directly connected, Serial0/0.1 > > R2: > > R 150.100.40.0/24 is possibly down, > routing via 150.100.24.4, Serial0/1.24 > R 150.100.41.0/24 is possibly down, > routing via 150.100.24.4, Serial0/1.24 > > I am not sure why is this happening. Can anyone answer? I need to > understand before I move forward. Thanks. > > Regards, > Samir. > > On Sun, Apr 17, 2011 at 7:17 PM, Marko Milivojevic > <[email protected]>wrote: > >> Could you paste the relevant configs from both, please? >> >> -- >> Marko Milivojevic - CCIE #18427 >> Senior Technical Instructor - IPexpert >> >> FREE CCIE training: http://bit.ly/vLecture >> >> Mailto: [email protected] >> Telephone: +1.810.326.1444 >> Web: http://www.ipexpert.com/ >> >> On Sun, Apr 17, 2011 at 10:06, Samir Idris <[email protected]> wrote: >> > Also, as soon as I configure ip rip triggered on the point-to-point >> > subinterface I create between R2 and R4 (as per IPExpert's topology), I >> > totally loose routes. I have removed "ip rip triggered" in the config >> > below: >> > >> > R4(config-subif)#do sh run int s0/0.1 >> > Building configuration... >> > Current configuration : 179 bytes >> > ! >> > interface Serial0/0.1 point-to-point >> > ip address 150.100.24.4 255.255.255.0 >> > ip rip authentication key-chain R2R4 >> > snmp trap link-status >> > frame-relay interface-dlci 402 >> > end >> > >> > R2#sh run int s0/1.24 >> > Building configuration... >> > Current configuration : 180 bytes >> > ! >> > interface Serial0/1.24 point-to-point >> > ip address 150.100.24.2 255.255.255.0 >> > ip rip authentication key-chain R2R4 >> > snmp trap link-status >> > frame-relay interface-dlci 204 >> > >> > When I run debug I see R2 recieving routes from R4 but not sending >> anything >> > back to R4. >> > >> > Can anyone see why? Thanks. >> > >> > Regards, >> > Samir Idris. >> > >> > On Sun, Apr 17, 2011 at 6:43 PM, Marko Milivojevic <[email protected] >> > >> > wrote: >> >> >> >> It is required only if you are explicitly asked to do it, otherwise no. >> >> >> >> Please note that in 12.4T, MD5 RIP authentication fails inexplicably >> >> most of the time. >> >> >> >> -- >> >> Marko Milivojevic - CCIE #18427 >> >> Senior Technical Instructor - IPexpert >> >> >> >> FREE CCIE training: http://bit.ly/vLecture >> >> >> >> Mailto: [email protected] >> >> Telephone: +1.810.326.1444 >> >> Web: http://www.ipexpert.com/ >> >> >> >> On Sun, Apr 17, 2011 at 06:35, Samir Idris <[email protected]> >> wrote: >> >> > Hi, >> >> > >> >> > A quick question: >> >> > >> >> > When configuring RIP authentication, is it necessary to specify the >> send >> >> > and >> >> > accept lifetime? I think not. Am I right? >> >> > >> >> > Key-chain R2R4: >> >> > key 1 -- text "ipexpert_R2toR4" >> >> > accept lifetime (always valid) - (always valid) [valid now] >> >> > send lifetime (always valid) - (always valid) [valid now] >> >> > >> >> > >> >> > R2(config-subif)#do sh ip proto >> >> > Routing Protocol is "rip" >> >> > Outgoing update filter list for all interfaces is not set >> >> > Incoming update filter list for all interfaces is not set >> >> > Incoming routes will have 5 added to metric if on list R8 >> >> > Sending updates every 30 seconds, next due in 19 seconds >> >> > Invalid after 180 seconds, hold down 0, flushed after 240 >> >> > Redistributing: rip >> >> > Default version control: send version 2, receive version 2 >> >> > Interface Send Recv Triggered RIP Key-chain >> >> > FastEthernet0/0 2 2 >> >> > Serial0/1.24 2 2 R2R4 >> >> > Serial0/1.25 2 2 >> >> > Serial0/1.26 2 2 >> >> > Automatic network summarization is not in effect >> >> > Maximum path: 4 >> >> > Routing for Networks: >> >> > 0.0.0.0 >> >> > Passive Interface(s): >> >> > Serial0/0 >> >> > FastEthernet0/1 >> >> > Serial0/1 >> >> > Serial0/2 >> >> > Serial0/3 >> >> > FastEthernet1/0 >> >> > FastEthernet1/1 >> >> > FastEthernet1/2 >> >> > FastEthernet1/3 >> >> > FastEthernet1/4 >> >> > FastEthernet1/5 >> >> > FastEthernet1/6 >> >> > FastEthernet1/7 >> >> > FastEthernet1/8 >> >> > FastEthernet1/9 >> >> > FastEthernet1/10 >> >> > FastEthernet1/11 >> >> > Passive Interface(s): >> >> > FastEthernet1/12 >> >> > FastEthernet1/13 >> >> > FastEthernet1/14 >> >> > FastEthernet1/15 >> >> > Vlan1 >> >> > VoIP-Null0 >> >> > Routing Information Sources: >> >> > Gateway Distance Last Update >> >> > 150.100.100.6 120 00:00:24 >> >> > 150.100.100.5 120 00:00:01 >> >> > 150.100.24.4 120 00:01:54 >> >> > 150.100.12.1 120 00:00:12 >> >> > Distance: (default is 120) >> >> > >> >> > Apr 17 15:33:49.891: RIP: ignored v2 packet from 150.100.24.4 >> (invalid >> >> > authentication) >> >> > >> >> > Regards, >> >> > Samir Idris. >> >> > _______________________________________________ >> >> > For more information regarding industry leading CCIE Lab training, >> >> > please visit www.ipexpert.com >> >> > >> > >> > >> > >> > -- >> > Samir Idris >> > >> > > > > -- > Samir Idris > -- Samir Idris _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
