RIP route received but not in the database

From: Michael Zuo (mzuo@ixiacom.com)
Date: Tue Mar 20 2007 - 15:19:16 ART


Hi Group,

I ran into a problem with RIP where RIP route 7.7.1.0/24 is received
from a neighbor but it does not show up in "show ip rip database". How
do I find out why it is not included in the database? I have tried
clearing ip route and reloading the router...

Thanks a lot

R3#sh run int s0/1

Building configuration...

Current configuration : 161 bytes

!

interface Serial0/1

 ip address 172.16.35.3 255.255.255.0

 ip pim dense-mode

 encapsulation ppp

 ipv6 address FEC0::35:3/125

 ipv6 nat

 ipv6 rip 1 enable

end

R3#sh run | be router rip

router rip

 version 2

 passive-interface default

 network 3.0.0.0

 network 172.16.0.0

 neighbor 172.16.234.2

 neighbor 172.16.234.4

 neighbor 172.16.35.5

 no auto-summary

R3#deb ip rip

RIP protocol debugging is on

R3#

10:38:55: RIP: received v2 update from 172.16.35.5 on Serial0/1

10:38:55: 5.5.5.0/24 via 0.0.0.0 in 1 hops

10:38:55: 7.7.1.0/24 via 0.0.0.0 in 2 hops <<<<<<<<< this is the
route in question

10:38:55: 7.7.2.0/24 via 0.0.0.0 in 2 hops

10:38:55: 7.7.3.0/24 via 0.0.0.0 in 2 hops

10:38:55: 172.16.50.0/24 via 0.0.0.0 in 1 hops

10:38:55: 172.16.102.1/32 via 0.0.0.0 in 1 hops

10:38:55: 172.16.105.0/24 via 0.0.0.0 in 1 hops

R3#sh ip rip da

2.0.0.0/8 auto-summary

2.2.2.0/24

    [1] via 172.16.234.2, 00:00:11, Serial0/0.234

3.0.0.0/8 auto-summary

3.3.3.0/24 directly connected, Loopback3

4.0.0.0/8 auto-summary

4.4.4.0/24

    [1] via 172.16.234.4, 00:00:24, Serial0/0.234

5.0.0.0/8 auto-summary

5.5.5.0/24

    [1] via 172.16.35.5, 00:00:13, Serial0/1

7.0.0.0/8 auto-summary

7.7.2.0/24
<<<<<<< 7.7.1.0 is not there !

    [2] via 172.16.35.5, 00:00:13, Serial0/1

7.7.3.0/24

    [2] via 172.16.35.5, 00:00:13, Serial0/1

22.0.0.0/8 auto-summary

22.22.22.0/24

    [2] via 172.16.234.2, 00:00:11, Serial0/0.234

    [2] via 172.16.234.4, 00:00:24, Serial0/0.234

44.0.0.0/8 auto-summary

44.44.44.0/24

    [2] via 172.16.234.2, 00:00:11, Serial0/0.234

    [2] via 172.16.234.4, 00:00:00, Serial0/0.234

172.16.0.0/16 auto-summary

172.16.12.0/24

    [1] via 172.16.234.2, 00:00:14, Serial0/0.234

172.16.16.0/24

    [2] via 172.16.234.2, 00:00:14, Serial0/0.234

    [2] via 172.16.234.4, 00:00:00, Serial0/0.234

172.16.35.0/24 directly connected, Serial0/1

172.16.35.5/32 directly connected, Serial0/1

172.16.50.0/24

    [1] via 172.16.35.5, 00:00:16, Serial0/1

172.16.64.0/24

    [1] via 172.16.234.4, 00:00:00, Serial0/0.234

172.16.100.0/22

    [2] via 172.16.234.2, 00:00:14, Serial0/0.234

    [2] via 172.16.234.4, 00:00:00, Serial0/0.234

172.16.102.0/24

    [1] via 172.16.234.2, 00:00:14, Serial0/0.234

172.16.102.1/32

    [1] via 172.16.35.5, 00:00:16, Serial0/1

172.16.104.0/24

    [1] via 172.16.234.4, 00:00:00, Serial0/0.234

172.16.105.0/24

    [1] via 172.16.35.5, 00:00:17, Serial0/1

172.16.106.0/24

    [2] via 172.16.234.2, 00:00:16, Serial0/0.234

    [2] via 172.16.234.4, 00:00:01, Serial0/0.234

172.16.110.0/24

    [2] via 172.16.234.4, 00:00:01, Serial0/0.234

172.16.124.0/24

    [1] via 172.16.234.2, 00:00:16, Serial0/0.234

    [1] via 172.16.234.4, 00:00:01, Serial0/0.234

172.16.200.0/22

    [1] via 172.16.234.2, 00:00:16, Serial0/0.234

172.16.234.0/24 directly connected, Serial0/0.234

R3#



This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:52 ART