From: Huan Pham (huan.pham@valuenet.com.au)
Date: Mon Dec 31 2007 - 13:51:00 ARST
Hi Phuc,
As Gary pointed out, can you pls double check if the /25 and above are being
learnt from other routers as well. Next hop of 163.1.18.1 does not always
mean that they are being learnt from that router. In Broadcast network such
as Ethernet, the next hop doesn't usually change.
For instance, if you have R2 taking part in RIP with R1 and SW1 via Ethernet
interface. R2 is also talking OSPF to R1 via the same Ethernet interface as
well, and redistributes all OSPF to RIP, then SW1 will get all the routes
from R2 (although next hop is still pointing to R1).
On the SW1, you can see what RIP routes are being received from what
router(s) using these 2 debug commands (turn both on)
debug ip rip database
debug ip rip event
Cheers,
Huan
> >
> > Can SW2 receive these routes from somewhere other than R1 perhaps?
> I don't think so because the next hop is from 163.1.18.1
>
>
> Gary
>
> ----- Original Message -----
> From: "nhatphuc" <nhatphuc@gmail.com>
> To: "Cisco certification" <ccielab@groupstudy.com>
> Sent: Monday, December 31, 2007 10:08 AM
> 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
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST