From: Mike McSpedon (Mike@xxxxxxxx)
Date: Sun Jan 30 2000 - 15:56:23 GMT-3
Zenchai,
I suspect what's happening here is that the route you are intending to
redistribute into EIGRP is not in R1's routing table via OSPF. It's a
connected route, so you should redistribute connected with a route-map to
limit the redistribution to just 137.20.20.0 /24.
HTH,
Mike
At 05:56 PM 1/29/00 -0800, zhencai wrote:
>Hi,
>
>I thought I knew redistribution and this is a fairly simply senario, but I
>couldn't make this work, any help will be greatly appreciated!!!
>
>------R1=======R2=======R3
> e0 s0 s0 s1 s0
>|-ospf-|-------eigrp-----|
>
>R1:
>interface e0
> ip addr 137.20.20.1 255.255.255.0
>interface s0
> ip addr 192.168.21.1 255.255.255.0
>router ospf 10
> redistribute eigrp 200 metric 64 subnet
> network 137.20.20.1 0.0.0.0 area 0
>router eigrp 200
> redistribute ospf 10 metric 10000 100 255 1 1500
> network 192.168.21.0
> no auto-summary
>
>R2:
>interface s0
> ip addr 192.168.21.2 255.255.255.0
>interface s1
> ip addr 192.168.17.1 255.255.255.0
>router eigrp 200
> network 192.168.17.0
> network 192.168.21.0
>
>R3:
>interface s0
> ip addr 192.168.17.2 255.255.255.0
>router eigrp 200
> network 192.168.17.0
>
>Clock rate is properly configured. From R3, I can't see R1's e0 subnet
>unless I chance R1's e0 to /16 subnet. But EIGRP is VLSM, 137.20.20.0/24
>should be able to get advertised into EIGRP. right? What did I do wrong?
>Thanks a lot.
>
>Zhen Cai
>
>p.s. IOS is 11.2(12) enterprise
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:46 GMT-3