From: Earl Aboytes (earl@xxxxxxxxxxxx)
Date: Sun Feb 13 2000 - 01:02:09 GMT-3
Ron,
The redistribute connected is used when you want to advertise a network but you
don't want to send routing updates into that network. You could configure it
as a passive interface but what if you have more than one. It is much easier t
o use the redistrubute connected. See pg 715 and 716 in Doyle's book.
Earl
At 05:52 PM 2/12/00 -0800, Ron Panus wrote:
>The redistribute connected command is a great feature. For example, say you
>have a lab scenario where you need to advertise a link between two routers.
>You are not allowed to include the interfaces from either router in any
>network protocol (ie OSPF network x.x.x.x) and you are not allowed to use
>static routes of ANY kind. Lets say that both routers are already running
>OSPF, but the interface that you need to advertise on each router is not and
>cannot be included with an OSPF network statement. By redistributing
>connected into OSPF
>
>router ospf 1
>redistribute connected metric 10 route-map go_con
>
>access-list 1 permit x.x.x.x 0.0.0.255
>
>route-map go_con permit 10
>match ip address 1
>
>You now have found a way to advertise that route into OSPF without breaking
>the rules of the particular scenario has stated above. The cool thing is
>that you can use this "trick" with any routing protocol to get around any
>limitation of using conventional advertising methods of having to use static
>routes. I hope that makes sense.
>
>Ron...
>
>>From: Curtis Phillips <phillipscurtis@netscape.net>
>>Reply-To: Curtis Phillips <phillipscurtis@netscape.net>
>>To: Randy Nunez <randy@nunez.com>, ccielab@groupstudy.com
>>Subject: Re: [Redistribute Connected Command]
>>Date: 12 Feb 00 20:15:15 EST
>>
>>Randy,
>>
>>I do not recollect seeing this used in any form other than as a convenient
>>way to advertise those routes in a single statement.
>>
>>This list seems very quiet..
>>
>>Curtis
>>
>>
>>Randy Nunez <randy@nunez.com> wrote:
>>I am trying to understand when you would use the redistribute connected
>>command. I understand that the command causes directly connected subnets
>>to be redistributed. According to the Cisco documentation:
>>
>>The keyword connected refers to routes which are established automatically
>>by virtue of having enabled IP on an interface. For routing protocols such
>>as OSPF and IS-IS, these routes will be redistributed as external to the
>>autonomous system.
>>
>>My assumption is that this is a method of adding the router's locally
>>connected networks to a routing protocol without adding it explicitly to
>>the routing process. I could see that you could use this statement to add
>>several loopbacks to a routing protocol without defining those subnets
>>under the routing process. You could also just add the subnets to the
>>routing process. Could someone provide examples of situations where this
>>command would be useful/necessary?
>>
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:53 GMT-3