Re: MPLS Route Targets

That is correct. If no local VRF's have those RT's you would need to use the no bgp default route-target filter command.

CCIE # 23962 (SP)

Sent from my iPhone 3GS

On 21 Aug 2010, at 1:02 PM, Carlos G Mendioroz <tron_at_huapi.ba.ar> wrote:

> Cool.
> Just one question, as I have never labbed nor have experience in
> inter-AS mpls vpns: You say "in order to see" the route targets,
> but my impression of the command (no bgp default route-target filter)
> is that it actually filters, so for a reflector or a vpnv4 eBGP peer,
> you would actually need it in order to exchange such routes
> (those with no RTs used by local VRFs). Is that correct ?
>
> Thanks,
> -Carlos
>
> Paul Negron @ 20/08/2010 21:52 -0300 dixit:
>> All,
>>
>> When configuring Inter-AS VPN, The P routers ARE participating in BGP under
>> the VPNv4 Address-Family and will use the inner label to switch from carrier
>> to carrier. The default route target must be lifted in order to see the
>> route-targets on the P router. The only other way I know of is to configure
>> the route-targets on a vrf that is on the P router but not applied to any
>> interfaces.
>>
>> A similar problem would take place when using Confederations.
>>
>> The command that dumps the information on that P router or ANY router that
>> the route-targets are not configured on, is " no bgp default route-target
>> filter" under the BGP process. All of the RD information is seen. Even more
>> than a router that has the RT's configured.
>>
>>
>> Paul
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina
>
>
> 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 Sat Aug 21 2010 - 19:26:18 ART