Re: No BGP Default route-target filter

Guys,

makes absolute sense.

Jared, if you configure extra commands as a habit, wont one get marked down
by the proctor?
it would seem one is not sure on where to configure the command or when to
use it.

Splinter

On Thu, Jun 4, 2009 at 6:38 PM, Danshtr <danshtr_at_gmail.com> wrote:

> Be default, BGP will accept VPNv4 routes with Ext-Community of route-target
> equal to route-targets which local VRFs want to import to their VRF table
> (route-target import X:Y). This behavior reduces unused VPNv4 routes in the
> router's memory.
>
> The "no bgp default route-target filter" disables this behavior. It is
> often in inter-AS MPLS VPN configurations, where transit routers participate
> in the BGP VPNv4 route distribution but do not need to import the routes to
> a local VRF tables.
> HTH,
> Dan
>
>
>
> On Thu, Jun 4, 2009 at 7:26 PM, Splinter <splinter330_at_gmail.com> wrote:
>
>> Hi All,
>>
>> need some clarification on the use of the "no bgp default route-target
>> filter"
>>
>> here is my example:
>>
>> BGP AS 1010
>> r4 ---------- r6
>> | |
>> | FR |
>> | |
>> | |
>> R2-----------R9
>> BGP AS 10
>>
>> R6 - ABC Site 3 RT 1010:10
>> R2 - ABC Site 2 RT 10:10
>> R9 - XYZ Site 2 RT 1099:10
>>
>> BGP VPNV4 setup between all routes. To my understanding i only have to
>> configure the command
>> under the PE routers that will be carry multiple VPNV4 routes. ie the will
>> be R2 and R9.
>>
>> Do i also have to configure it on R4 and R6 as well?
>>
>> thank you
>>
>> Splinter
>>
>>
>> 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
Received on Thu Jun 04 2009 - 19:02:31 ART