RIP route poisoning issues

Hello Guys,

I need help . am working on some lab scenarios.

i have 3 routers connected R4,R5 and BB

R4 is connected to the BB router through the network 204.12.1.0 and the BB
router is advertising routes 30.0.0.0 and 31.0.0.0 network via rip as shown in
the below output

R4#sh ip route rip
     31.0.0.0/32 is subnetted, 5 subnets
R 31.0.4.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 31.0.2.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 31.0.3.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 31.0.0.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 31.0.1.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
     150.1.0.0/32 is subnetted, 2 subnets
R 150.1.5.5 [120/1] via 155.1.45.5, 00:00:00, Serial0/1
                  [120/1] via 155.1.0.5, 00:00:00, Serial0/0
     30.0.0.0/32 is subnetted, 6 subnets
R 30.0.5.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 30.0.4.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 30.0.3.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 30.0.2.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 30.0.1.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R 30.0.0.1 [120/1] via 204.12.1.254, 00:00:15, FastEthernet0/0
R4#

R4 as a dual connection to R5 via serial and a frame relay link and are both
runing RIP.

The problem is that R4 is continually poisoning the 30.0.0.0 and 31.0.0.0
learned from BB router. and it has a next hop of 0.0.0.0 as shown from the
debug ip rip on R4

*Mar 1 11:25:32.405: 30.0.5.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.405: 31.0.0.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.409: 31.0.1.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.413: 31.0.2.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.417: 31.0.3.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.417: 31.0.4.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:32.421: 150.1.5.5/32 via 0.0.0.0 in 1 hops
*Mar 1 11:25:32.425: 155.1.0.0/24 via 0.0.0.0 in 1 hops
*Mar 1 11:25:32.429: 155.1.45.0/24 via 0.0.0.0 in 1 hops
*Mar 1 11:25:32.429: 155.1.146.0/24 via 0.0.0.0 in 16 hops
(inaccessible)
*Mar 1 11:25:32.433: 204.12.1.0/24 via 0.0.0.0 in 16 hops
(inaccessible)
*Mar 1 11:25:33.733: RIP: received v2 update from 155.1.0.5 on Serial0/0
*Mar 1 11:25:33.737: 30.0.0.1/
R4#32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.737: 30.0.1.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.741: 30.0.2.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.745: 30.0.3.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.749: 30.0.4.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.749: 30.0.5.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.753: 31.0.0.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.757: 31.0.1.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.761: 31.0.2.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.761: 31.0.3.1/32 via 0.0.0.0 in 16 hops (inaccessible)
*Mar 1 11:25:33.765: 31.0.4.1/32 via 0.0.0.0 in 16 hops (inaccessible

This makes pings from R5 to the 30.0.0.0 and 31.0.0.0 net time out
occasionally .

Can somebody explain why this is happening?

Regards
abiola

Blogs and organic groups at http://www.ccie.net
Received on Wed Feb 17 2010 - 19:49:50 ART