Re: RIP route poisoning issues

From: biola <biola_y2k_at_yahoo.com>
Date: Wed, 17 Feb 2010 20:40:43 -0800 (PST)

Find below the show run output for the routers
-

BB3#
BB3#sh run
Building configuration...

Current configuration : 1671 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname BB3
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
multilink bundle-name authenticated
!
!
!
key chain TEST
 key 1
   key-string cisco
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
archive
 log config
  hidekeys
!
!
!
!
!
!
!
!
interface Loopback0
 ip address 30.0.0.1 255.255.255.255
!
interface Loopback1
 ip address 30.0.1.1 255.255.255.255
!
interface Loopback2
 ip address 30.0.2.1 255.255.255.255
!
interface Loopback3
 ip address 30.0.3.1 255.255.255.255
!
interface Loopback4
 ip address 30.0.4.1 255.255.255.255
!
interface Loopback5
 ip address 30.0.5.1 255.255.255.255
!
interface Loopback6
 ip address 31.0.0.1 255.255.255.255
!
interface Loopback7
 ip address 31.0.1.1 255.255.255.255
!
interface Loopback8
 ip address 31.0.2.1 255.255.255.255
!
interface Loopback9
 ip address 31.0.3.1 255.255.255.255
!
interface Loopback10
 ip address 31.0.4.1 255.255.255.255
!
interface FastEthernet0/0
 ip address 204.12.1.254 255.255.255.0
 ip rip authentication mode md5
 ip rip authentication key-chain TEST
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 network 30.0.0.0
 network 31.0.0.0
 network 204.12.1.0
 no auto-summary
!
ip forward-protocol nd
!
!
ip http server
no ip http secure-server
!
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

BB3#
BB3#

R4#
R4#sh run
Building configuration...

Current configuration : 1447 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
multilink bundle-name authenticated
!
!
!
key chain TEST
 key 1
   key-string cisco
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
archive
 log config
  hidekeys
!
!
!
!
!
!
!
!
interface Loopback0
 ip address 150.1.4.4 255.255.255.255
!
interface FastEthernet0/0
 ip address 204.12.1.4 255.255.255.0
 ip rip authentication mode md5
 ip rip authentication key-chain TEST
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 155.1.0.4 255.255.255.0
 encapsulation frame-relay
 clock rate 2000000
 frame-relay map ip 155.1.0.5 405 broadcast
 no frame-relay inverse-arp
!
interface FastEthernet0/1
 ip address 155.1.146.4 255.255.255.0
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 155.1.45.4 255.255.255.0
 clock rate 2000000
!
router rip
 version 2
 network 155.1.0.0
 network 204.12.1.0
 distribute-list 10 in Serial0/0
 distribute-list 10 in Serial0/1
 no auto-summary
!
ip forward-protocol nd
!
!
ip http server
no ip http secure-server
!
!
!
!
route-map REW permit 10
 set interface Serial0/1
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R4#
R4#
R4#

R5#sh run
Building configuration...

Current configuration : 1588 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R5
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
archive
 log config
  hidekeys
!
!
!
!
!
!
!
!
interface Loopback0
 ip address 150.1.5.5 255.255.255.255
 ip rip advertise 2
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
 ip policy route-map TEST
 clock rate 2000000
!
interface Serial0/0.100 multipoint
 ip address 155.1.0.5 255.255.255.0
 ip rip advertise 2
 no ip split-horizon
 snmp trap link-status
 frame-relay map ip 155.1.0.4 504 broadcast
 frame-relay map ip 155.1.0.3 503 broadcast
 frame-relay map ip 155.1.0.2 502 broadcast
 frame-relay map ip 155.1.0.1 501 broadcast
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 155.1.45.5 255.255.255.0
 ip rip advertise 2
 shutdown
 clock rate 2000000
!
interface FastEthernet1/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 timers basic 2 6 10 15
 network 150.1.0.0
 network 155.1.0.0
 no auto-summary
!
ip forward-protocol nd
!
!
ip http server
no ip http secure-server
!
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R5#
R5#
R5#

On Wed, Feb 17, 2010 at 10:49 PM, biola <biola_y2k_at_yahoo.com> wrote:

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 - 20:40:43 ART

This archive was generated by hypermail 2.2.0 : Mon Mar 01 2010 - 06:28:36 ART