From: Marko Milivojevic (markom@markom.info)
Date: Tue Jul 08 2008 - 18:46:14 ART
Like we said so many times on this list - you need to think like a
router to be able to configure one ;-).
When redistributing, routers redistribute information from routing
table, not from protocol-specific tables. What do connected interfaces
show as when you do "show ip route"? They don't show as "O", or "D",
or "R", or "B" - they show as "C".
If you want those routes in a routing process, you need to
redistribute the "protocol" where they come from :-).
Marko
#18427
On Tue, Jul 8, 2008 at 10:58, CCIE3000 <ccie3000@googlemail.com> wrote:
> *Is it the normal behaviour.*
>
> Yep.
>
> You can't redis into one routing protocol and then from that routing
> protocol redis into another routing protocl on the same router.
>
> If you redis connected into EIGRP you need to redis connected into OSPF even
> if you are redistributing EIGRP into OSPF.
>
> On Tue, Jul 8, 2008 at 1:50 PM, akyccie <akyccie@gmail.com> wrote:
>
>> I notice that the connected interface part of eigrp process dosn't get
>> advertise to OSPF when you redistripute eigrp to ospf. Is it the normal
>> behaviour.
>>
>> what is the workaround here, redistribute connected ??
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:54 ART