From: Nitin Venugopal (nitinsworld@gmail.com)
Date: Tue Mar 10 2009 - 11:35:47 ARST
Sorry I missed the configuration you have done for Partioning RR .You have
additional line  'no bgp default route-target filter' . This is not required
for RR
Anotther option you have is using community access-list and route-map policy
(in the inbound direction in your case)
Regds
Nitin
On Tue, Mar 10, 2009 at 5:07 PM, Nitin Venugopal <nitinsworld@gmail.com>wrote:
>
>
>   On Tue, Mar 10, 2009 at 4:38 PM, backbone systems <
> backbone.systems@gmail.com> wrote:
>
>>  Scenario...
>>
>> CE----PE1-----P(RR)------PE2-----CE
>>
>> Now i am configuring bgp-rr group on the P router to only accept
>> routes with RT of 1:100
>>
>> but after applying the config i can still see the routes from other
>> customers,
>>
>> Here is the config for P,
>>
>> router bgp 1
>>  no bgp default ipv4-unicast
>>  no bgp default route-target filter
>>  bgp log-neighbor-changes
>>  neighbor 2.2.2.2 remote-as 1
>>  neighbor 2.2.2.2 update-source Loopback0
>>  neighbor 4.4.4.4 remote-as 1
>>  neighbor 4.4.4.4 update-source Loopback0
>>  !
>>  address-family vpnv4
>>  neighbor 2.2.2.2 activate
>>  neighbor 2.2.2.2 send-community extended
>>  neighbor 2.2.2.2 route-reflector-client
>>  neighbor 4.4.4.4 activate
>>  neighbor 4.4.4.4 send-community extended
>>  neighbor 4.4.4.4 route-reflector-client
>>  bgp rr-group RR
>>  exit-address-family
>>
>>
>> ip extcommunity-list standard RR permit rt 1:100
>>
>>
>> Below is the show output for P,
>>
>> R3(config-router)#do sh ip bgp vpnv4 all
>> BGP table version is 10, local router ID is 3.3.3.3
>> Status codes: s suppressed, d damped, h history, * valid, > best, i -
>> internal,
>>              r RIB-failure, S Stale
>> Origin codes: i - IGP, e - EGP, ? - incomplete
>>
>>   Network          Next Hop            Metric LocPrf Weight Path
>> Route Distinguisher: 1:100
>> *>i1.1.1.1/32       2.2.2.2                  0    100      0 65001 i
>> *>i5.5.5.5/32       4.4.4.4                  0    100      0 65001 i
>> *>i12.0.0.0         2.2.2.2                  0    100      0 65001 i
>> *>i13.0.0.0         4.4.4.4                  0    100      0 65001 i
>> Route Distinguisher: 1:200
>> *>i7.7.7.7/32       2.2.2.2                 10    100      0 ?
>> *>i8.8.8.8/32       4.4.4.4                 65    100      0 ?
>> *>i15.0.0.0         2.2.2.2                  0    100      0 ?
>> *>i16.0.0.0         4.4.4.4                  0    100      0 ?
>> * i17.0.0.0         4.4.4.4                 65    100      0 ?
>> *>i                 2.2.2.2                 10    100      0 ?
>>
>> As u can see i can see the routes from other customer too (rt=1:200)
>>
>> Any idea whats erong in my config?
>>
>> BB
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Hi BB,
>>
>> There is an exception in case of a PE or P performing the function as RR.
>
>
>
>> The route reflector muct be capable of receiving routes that might not be
>> associated with any locally configured VRF's and reflect them to the clients
>
>
>    Thus a PE Router ( in your case- P)  performing as route reflector, the
> automatic filerting process is disbaled to enable propogation of VPNV4
> routes    between the route reflector clients
>
>  Automatic Route filtering enables the PE to reduce the resource
> consumption by rejecting information not pertaining to the VRF's configured
> on the router. (But in your case P router is a RR)
>
> HTH.
>
> Regds
> Nitin
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:04 ART