From: Goyal, Avdhesh (Avdhesh.Goyal@ps.net)
Date: Mon Dec 31 2007 - 09:30:29 ARST
I just labbed it up and it works fine. However I will suggest you to try
changing the route-map and prefix list name that may solve the problem.
AG
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
nhatphuc
Sent: Monday, December 31, 2007 3:39 PM
To: Cisco certification
Subject: Can't filter prefix longer than 24 from OSPF to RIP
HI Group,
Please help why I can't filter prefix longer than 24 redistributed into
RIP from OSPF:
This is my config:
R1
router rip
version 2
redistribute ospf 1 metric 1 route-map OSPF->RIP passive-interface
default no passive-interface FastEthernet0/0 network 163.1.0.0 no
auto-summary !
ip forward-protocol nd
!
ip http server
no ip http secure-server
!
ip prefix-list NOT_LONGER24 seq 5 permit 0.0.0.0/0 le 24 !
route-map OSPF->RIP permit 10
match ip address prefix-list NOT_LONGER24
DEBUG IP RIP on R1:
*Dec 31 17:42:39.209: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/0 (163.1.18.1) *Dec 31 17:42:39.209: RIP: build update
entries
*Dec 31 17:42:39.209: 10.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.2.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.3.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.4.0/23 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.4.4/32 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.5.5/32 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.6.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.7.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 150.1.8.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.0.0/25 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.0.128/25 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.3.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.4.0/24 via 0.0.0.0, metric 1, tag 0
Rack1R1#
*Dec 31 17:42:39.209: 163.1.5.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.6.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.7.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.12.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.13.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.13.3/32 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.15.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.35.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.38.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.45.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.45.5/32 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 163.1.54.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: RIP: build update entries
*Dec 31 17:42:39.209: 163.1.57.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 192.10.1.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 31 17:42:39.209: 204.12.1.0/24 via 0.0.0.0, metric 1, tag 0
SW2 still see route longer than 24 from R1 (163.1.18.1) SW2#
R 204.12.1.0/24 [120/1] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 163.1.0.0/25 [120/4] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 163.1.6.0/24 [120/1] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 163.1.13.3/32 [120/4] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 163.1.12.0/24 [120/1] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 150.1.6.0/24 [120/4] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 150.1.3.0/24 [120/4] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 150.1.2.0/24 [120/1] via 163.1.18.1, 00:00:04, FastEthernet0/21
R 150.1.5.5/32 [120/4] via 163.1.18.1, 00:00:05, FastEthernet0/21
R 150.1.4.4/32 [120/4] via 163.1.18.1, 00:00:05, FastEthernet0/21
Thanks
Phuc
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST