It's more likely tied to your mask difference. IPCP doesn't pass mask information and therefore the /32 is seen below. Try turning off the "ip rip triggered" portion so that you can see routing updates every 30 seconds. See what arrives versus what is installed in "show ip rip database". Scott
_____ From: Sharath Samanth [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2008 11:19 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: [OSL | CCIE_RS] RIP Triggered updates R1 has no routes from R2. R2 is just not advertising the triggered updates to R1 even if shutdown a loop back interface. Debugs from R2 R2#show debugging Generic IP: IP packet debugging is on IP routing: RIP protocol debugging is on RIP event debugging is on R2(config)#int lo 2 R2(config-if)#shut R2(config-if)# *Mar 1 01:50:07.355: rip_route_adjust for Loopback2 going down *Mar 1 01:50:07.359: RIP: Removing everything from Loopback2's retrans queue and stopping the retrans timer. R2(config-if)# *Mar 1 01:50:09.347: %LINK-5-CHANGED: Interface Loopback2, changed state to administratively down *Mar 1 01:50:10.347: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback2, changed state to down No packets sent to R1 whatsoever. The Debug ip rip on R1 is empty. R2's interface status: R2#sh interfaces counters protocol status Protocols allocated: Serial0/0: Other, IP, CDP Serial0/1: Other, IP Serial0/2: Other, IP Serial0/3: Other, IP Loopback0: Other, IP Loopback1: Other, IP Loopback2: Other, IP VoIP-Null0: Other, IP Allocation failures: 0 R2#sh ip interface serial 0/0 Serial0/0 is up, line protocol is up Internet address is 10.60.0.4/32 Broadcast address is 255.255.255.255 Address determined by IPCP Peer address is 10.60.0.1 MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: 224.0.0.9 Outgoing access list is not set Inbound access list is not set Proxy ARP is enabled Local Proxy ARP is disabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is enabled IP Flow switching is disabled IP CEF switching is enabled IP CEF Fast switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled IP route-cache flags are Fast, CEF Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Policy routing is disabled Network address translation is disabled BGP Policy Mapping is disabled WCCP Redirect outbound is disabled WCCP Redirect inbound is disabled WCCP Redirect exclude is disabled Could this be an IOS bug? Regards Sharath On Tue, Mar 4, 2008 at 9:31 AM, Scott Morris <[EMAIL PROTECTED]> wrote: Do you have other reachability? What does your output from "debug ip rip" look like with your IPCP information? That may help you. Look at output from "show ip interface" as well. HTH, Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al. CCSI/JNCI-M/JNCI-ER VP - Technical Training - IPexpert, Inc. IPexpert Sr. Technical Instructor A Cisco Learning Partner - We Accept Learning Credits! [EMAIL PROTECTED] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 http://www.ipexpert.com <http://www.ipexpert.com/> _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sharath Samanth Sent: Monday, March 03, 2008 10:24 PM To: [email protected] Subject: [OSL | CCIE_RS] RIP Triggered updates Hi All, I have a question on the ip rip triggered updated command and need help. I have two routers R1 and R2 connected via serial link with PPP encapsulation. I have manually assigned the IP address to the serial links and have configured RIP with triggerd updates. R1 information: R1#sh ip int brief Interface IP-Address OK? Method Status Protocol Serial0/0 10.60.0.1 <http://10.60.0.1/> YES NVRAM up up Serial0/1 unassigned YES NVRAM administratively down down Serial0/2 unassigned YES NVRAM administratively down down Serial0/3 unassigned YES NVRAM administratively down down Loopback0 172.11.1.1 <http://172.11.1.1/> YES NVRAM up up Loopback1 172.11.2.1 <http://172.11.2.1/> YES NVRAM up up Loopback2 172.11.3.1 <http://172.11.3.1/> YES NVRAM administratively down down R1# R1# R1#sh ip route rip 172.22.0.0/24 is subnetted, 3 subnets R 172.22.2.0 <http://172.22.2.0/> [120/1] via 10.60.0.2 <http://10.60.0.2/> , 00:01:46, Serial0/0 R 172.22.3.0 <http://172.22.3.0/> [120/1] via 10.60.0.2 <http://10.60.0.2/> , 00:00:35, Serial0/0 R 172.22.1.0 <http://172.22.1.0/> [120/1] via 10.60.0.2 <http://10.60.0.2/> , 00:01:46, Serial0/0 R1# R1# R1#sh ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 15 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 Serial0/0 2 2 Yes RIP-KEYS Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 10.0.0.0 <http://10.0.0.0/> 172.11.0.0 <http://172.11.0.0/> Passive Interface(s): Loopback0 Loopback1 Loopback2 Routing Information Sources: Gateway Distance Last Update 10.60.0.2 <http://10.60.0.2/> 120 00:00:43 Distance: (default is 120) R2 Information R2#sh ip int brief Interface IP-Address OK? Method Status Protocol Serial0/0 10.60.0.2 <http://10.60.0.2/> YES manual up up Serial0/1 unassigned YES NVRAM administratively down down Serial0/2 unassigned YES NVRAM administratively down down Serial0/3 unassigned YES NVRAM administratively down down Loopback0 172.22.1.1 <http://172.22.1.1/> YES NVRAM up up Loopback1 172.22.2.1 <http://172.22.2.1/> YES NVRAM up up Loopback2 172.22.3.1 <http://172.22.3.1/> YES NVRAM up up R2# R2# R2# R2#sh ip route rip 172.11.0.0/24 is subnetted, 3 subnets R 172.11.3.0 <http://172.11.3.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:14, Serial0/0 R 172.11.2.0 <http://172.11.2.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:30, Serial0/0 R 172.11.1.0 <http://172.11.1.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:30, Serial0/0 R2# R2# R2# R2#sh ip pro R2#sh ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 22 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 Serial0/0 2 2 Yes RIP-KEYS Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 10.0.0.0 <http://10.0.0.0/> 172.22.0.0 <http://172.22.0.0/> Passive Interface(s): Loopback0 Loopback1 Loopback2 Routing Information Sources: Gateway Distance Last Update 10.60.0.1 <http://10.60.0.1/> 120 00:00:18 Distance: (default is 120) The triggered updated just work fine in this scenario. However, when I configure R2 to negotiate the IP address from R1's local pool, then triggered updates from R2 would not be sent to R1. R1 loses all the routes from R2. R2 retains R1's routes and triggered updates from R1 is sent to R2. R2 output after IP address is negotiated via IPCP. R2#sh ip int brief Interface IP-Address OK? Method Status Protocol Serial0/0 10.60.0.4 <http://10.60.0.4/> YES IPCP up up Serial0/1 unassigned YES NVRAM administratively down down Serial0/2 unassigned YES NVRAM administratively down down Serial0/3 unassigned YES NVRAM administratively down down Loopback0 172.22.1.1 <http://172.22.1.1/> YES NVRAM up up Loopback1 172.22.2.1 <http://172.22.2.1/> YES NVRAM up up Loopback2 172.22.3.1 <http://172.22.3.1/> YES NVRAM up up R2# R2# R2#sh ip route rip 172.11.0.0/24 is subnetted, 3 subnets R 172.11.3.0 <http://172.11.3.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:32 R 172.11.2.0 <http://172.11.2.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:32 R 172.11.1.0 <http://172.11.1.0/> [120/1] via 10.60.0.1 <http://10.60.0.1/> , 00:00:32 R2# R2# R2#sh ip pro R2#sh ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 14 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 Serial0/0 2 2 Yes RIP-KEYS Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 10.0.0.0 <http://10.0.0.0/> 172.22.0.0 <http://172.22.0.0/> Passive Interface(s): Loopback0 Loopback1 Loopback2 Routing Information Sources: Gateway Distance Last Update 10.60.0.1 <http://10.60.0.1/> 120 00:00:37 Distance: (default is 120) R1's output after R2 is configured for ip address negotiation R1#sh ip int brief Interface IP-Address OK? Method Status Protocol Serial0/0 10.60.0.1 <http://10.60.0.1/> YES NVRAM up up Serial0/1 unassigned YES NVRAM administratively down down Serial0/2 unassigned YES NVRAM administratively down down Serial0/3 unassigned YES NVRAM administratively down down Loopback0 172.11.1.1 <http://172.11.1.1/> YES NVRAM up up Loopback1 172.11.2.1 <http://172.11.2.1/> YES NVRAM up up Loopback2 172.11.3.1 <http://172.11.3.1/> YES NVRAM up up R1# R1#sh ip route rip R1# R1# R1# R1#sh ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 20 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 Serial0/0 2 2 Yes RIP-KEYS Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 10.0.0.0 <http://10.0.0.0/> 172.11.0.0 <http://172.11.0.0/> Passive Interface(s): Loopback0 Loopback1 Loopback2 Routing Information Sources: Gateway Distance Last Update 10.60.0.2 <http://10.60.0.2/> 120 00:06:16 Distance: (default is 120) So is this working as designed? will the triggered updates from the negotiated peer would not be sent to R1? Any ideas would be very helpful. regards, sharath
