From: Rick Mur (rick@rickmur.com)
Date: Fri Dec 12 2008 - 15:05:14 ARST
So what you are saying is that when you issue redistribute connected,
the connected interfaces of the routing protocol that's also
redistributed, won't be included anymore, just the learned routes?
Rick
On 8 dec 2008, at 21:15, Farhan Anwar wrote:
> There are two types of protocols involved in the redistribution,
> first are
> the redistributed ones which are being redistributed into another
> protocol,
> and second are the redistributing ones.
>
> When you redistribute a routing protocol into another, by default the
> process follows two rules:
> 1. It checks and redistributes the connected interfaces which are
> included
> in the redistributed protocol.
> 2. It checks and redistributes the learned routes for that
> redistributed
> protocol.
>
> But when you use "redistribute connected", and limit it to a specific
> interface using a route-map the first default rule (defined above)
> gets
> over-ruled by the route-map you have created.
>
> Hence the final result after redistribution, the routes shown in the
> redistributing protocol will be:
> 1. Routes for the Interfaces included in the route-map used in
> redistribute
> connected.
> 2. Routes learned from the redistributed protocol.
>
> So the missing routes are: Connected interfaces which were a part of
> redistributed protocol but are absent in the route-map being used in
> the
> "redistribute connected".
>
> For resolving this, just add those missing interfaces into the route-
> map as
> well.
>
> HTH.
>
> On Tue, Dec 9, 2008 at 12:18 AM, Hobbs <deadheadblues@gmail.com>
> wrote:
>
>> A common scenario is when you are redistributing among 3 protocols
>> on the
>> same router. Lab it and see what happens when you don't use it.
>>
>> On Mon, Dec 8, 2008 at 8:58 AM, Darby Weaver <ccie.weaver@gmail.com>
>> wrote:
>>
>>> I think in terms of the lab it depends on the requirements given
>>> on how
>> the
>>> interface might need to be advertised to the network.
>>>
>>> If you do use redistribute connected then you might want to use a
>> route-map
>>> to limit which interfaces are actually redistributed in the specific
>>> protocol to meet your exlicit requirements of the task at hand.
>>>
>>> For example you might be restricted from using the network command
>>> or
>> some
>>> other type of wording.
>>>
>>> In life, I suppose you can do it in either fashion.
>>>
>>>
>>>
>>>
>>> On Mon, Dec 8, 2008 at 10:20 AM, khurram noor <smartcapricon82@gmail.com
>>>> wrote:
>>>
>>>> Hi Guys,
>>>> I have a question in my mind for some days now, i always think
>>>> why is
>>>> redistribute connected command used some times while we do
>>> redistribution.
>>>> NOw i have also noticed that many times it is not used. Can
>>>> anyone tell
>>> me
>>>> what is the best place to use this command, where this command
>>>> should
>> be
>>>> used and where it is not required ? Please help as I need to
>>>> clear this
>>>> confusion.
>>>>
>>>> --
>>>> Khurram Noor
>>>> CCIP, CCNA
>>>>
>>>>
>>>> Blogs and organic groups at http://www.ccie.net
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Syed Farhan A. Hussain
> CCIE #19871
> Senior Network Consultant
> www.farhananwar.com
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:08 ARST