BGP AS number

Hi Guys,
Let's say I have 2 CEs that use different VRFs (VRF light), can I use only one BGP AS number to peer with different PEs? or should the AS number be configured per VRF?
Thanks,

Hi,
can I use only one BGP AS number to peer with different PEs?
Not only you can - you have to. Regardless of presence and count of VRFs, you can start only a single BGP process in your configuration. It is, to my best knowledge, not possible to configure AS numbers on a per-VRF basis in BGP.
There is an option of pretending that your BGP ASN is different than the true one, activated using the neighbor local-as command. However, this is not a typical use case for this command, and if you can avoid it, you should.
Best regards,
Peter

Similar Messages

  • Filtering OSPF routes from MPBGP to BGP speaker in the same VRF

    I'm wondering if anyone has some ideas they an share on this.
    Assume the following:
    - CE1 is speaking *iBGP and OSPF to PE1 inside vrf foo
    - PE1 is mutually redistributing CE1's OSPF table with MPBGP
    - PE1 exchanges MPBGP routes with PE2.
    - PE2 is mutually redistributing CE2's OSPF table with MPBGP
    - CE2 is speaking *iBGP and OSPF to PE2 inside vrf foo
    So the problem is that the OSPF routes redistributed into MPBGP from via one CE are being announced to the other CE via the PE-CE BGP process.  Because those routes are already being received by the CE via the PE-CE OSPF process, they are showing up in the CE's BGP table as RIB failures.
    Is there any way to filter those out?  I've tried setting and matching tags and communities from within various redistribution points on the PE, but I can't seem to keep them out of the CE's BGP table.

    are you sure you are using iBGP on both sides and not eBGP?
    I'm asking because routes learnt by PE1 from CE via iBGP ( meaning same BGP AS number on CE1 and PE1 vrf foo) will not be propagated to CE2, because an iBGP route learned by a BGP speaker in not pushed to another iBGP speaker.
    So it means that a show ip bgp neighbor vrf foo advertised routes on PE2 shall  show that no routes from CE1 are being advertised to CE2.
    As mentionned earlier, changing BGP admin distance is an option. Let BGP have a better distance on your CEs and this should do the trick :
    router bgp xxx
    distance bgp 20 20 20
    Then after clearing bgp session, the rib failures are gone as OSPF is AD 110 and BGP is now AD 20 ( also remember that BGP does not annouces rib failure routes to other BGP peers)
    cheers

  • BGP Local AS

    Hello All
    When using the local-as command under address-family ipv4 vrf, is the AS local to the specific Router or is it local to whole MPLS infrastructure?
    Can anybody advise on this please?
    Many Thanks in advance.

    Hi Kaushik,
    bgp local-as is per neighbor specific. You can have 2 neighbors on same router one with local-as and other without. By default, each router will include the AS number from "router bgp <as-number>" while sending the OPEN message. With bgp local-AS, you override it and make the router use the configured AS.
    This command is useful incase of migration.
    HTH,
    Nagendra

  • ASR Zones and BGP

    We're designing a second datacenter and are looking at routers for both our MPLS network and our Internet edge. In our current datacenter we have 4x3945e routers, two on the MPLS networks and two on the Internet edge networks. Since we're going to have a 1GB link between the two datacenters, I started looking at the ASR platform for it's impressive throughput compared to the 3945e.
    I noticed the Enterprise Applications feature supports zone-based policy firewall, which seems appealing. Given the raw power of the ASR and the ability to support zones, it seems one router could handle both the external Internet access and the MPLS traffic, each residing on it's own zone.
    Considering the ASR 1001x, my two questions are
    Is my assumption correct or would the above be a security concern?
    Can each zone support a different BGP AS number?
    Thank you,
    Denny

    From within the zone, you can see what pool you're bound to by simply using
    the -q argument to poolbind(1M) with a valid pid, such as "poolbind -q $$".
    Alternatively, you can use the pooladm(1M) command with no arguments.
    Note that if you don't have pools active, this will result in a "Facility is not active"
    message but otherwise you'll see the details about the pool this zone is bound
    to.
    From the global zone, you can see the actual pool the zone is currently bound
    by doing something like "zlogin myzone 'poolbind -q $$'". And you can see
    which pool the zone will attempt to bind to the next time it reboots by using
    the "zonecfg -z myzone info pool" command.
    Does this help?

  • Inter-VRF Route leakage

    Hi Guyz,
    I have 3 VRF's on VSS core.
    1) VRF A
    2) VRF B
    3) Global VRF.
    I have Firewall in L3 mode between these VRFs. Traffic between A & B have to cross firewall.
     i can use BGP or EVN to leak routes between VRFs,  but they leak only routes tht are present in  routing table.
    Now i need to leak specific route for eg 10.10.10.10/32 from VRF A to VRF B.
    10.10.10.0/24 is directly connected interface on VRF A. 
    i need to find a way where i can leake /32 route between VRFs.
    Thanks

    Changing the autonomous system number may be necessary when 2 separate BGP networks are combined under a single autonomous system. This typically occurs when one ISP purchases another ISP. The neighbor local-as command is used initially to configure BGP peers to support 2 local autonomous system numbers to maintain peering between 2 separate BGP networks. This configuration allows the ISP to immediately make the transition without any impact on existing customer configurations
    enable
    configure terminal
    router bgp as-number
    address-family {ipv4 | ipv6 | vpnv4| [multicast | unicast | vrf {vrf-name}]}

  • IPv6 ASN question

    Hi Harold,
    We were just issued our IPv6 address block by Arin, and it came with three ASNs. Could you provide any information on why there are three (instead of just one)?  Also, would I use one of those ASNs for my EIGRP routing on the inside or are those only for use with my BGP routing to our ISPs? (in other words, can I use a private ASN for EIGRP on the inside or will that mess things up?) Thanks much!

    EIGRP AS number isn't related to BGP AS number.  As a general rule, to communicate with other ISPs via BGP you need a public AS number given to you by someone like arin.  You can pick whatever AS number you like to use for EIGRP.  Your EIGRP AS number has no bearing whatsoever on your BGP AS number.  They can be the same, or they can be different.
    hth

  • BGP peers with same AS number

    Hi All,
    As in the network topology attached (replica of actual network), I would like to know if there is any way that routes received from PE-RTR1 in CE-RTR can be advertised to PE-RTR2 and vice versa, so that PE-RTR1 & PE-RTR2 can reach each other.
    Routing protocol used between PE-RTR1 & CE and PE-RTR2 & CE is BGP.
    The issue seems to be due to same AS number of PE-RTR1 & PE-RTR2. It might not be possible to change AS numbers defined. Is there any way to overcome this situation?
    Thanks in advance..
    Regards,
    Nagabhushan

    I read that a bit too quickly.
    If you're connecting your locations via the ISP and they all use the same AS, they'll all need the statement I mentioned in my previous comment. If you already have communication between them via the ISP, then this command is probably already there.
    If you're connecting everything via fibre to the primary location, you can just peer with the other locations using the same AS and you'll be fine... though there are some considerations if you're redistributing BGP into an internal routing protocol.
    In your current configuration, is each location seeing the networks from the other sites propagating from the ISP via BGP?

  • BGP Advertisement to Specific AS Number

    HOw to setup BGP so it will not get advertised to specific AS.
    Example:
    My BGP AS 1000 and i peer with AS 2000 and 3000. I want to tell BGP AS 2000 not to advertise to AS 100, and 200. 
    Or i want to advertise my blocks to all internet but i want to make sure AS 100 and 200 wont have my prefix in the BGP table.
    thanks

    Hello,
     Create a "peer-group" where you will add those two AS to the peer-group. And apply "mhnedirli" solution above...
    and use : 
    neighbor <peer-group-name> route-map BLOCK out

  • Can you display routes advertised and/or received in OSPF, similar to BGP command sh ip bgp neighbors x.x.x.x advertised-routes?

    TOC-BP-SWa#sh ip bgp neighbors 10.14.0.3 advertised-routes
    BGP table version is 1674320, local router ID is 10.14.0.1
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *> 10.14.0.1/32     0.0.0.0                  0         32768 i
    *> 147.249.37.0/24  172.20.18.1                   120      0 2001 65015 65016 64823 7381 64681 i
    *> 147.249.38.0/24  172.20.18.1                   120      0 2001 65015 65016 64823 7381 64681 i
    *> 147.249.46.0/24  172.20.18.1                   120      0 2001 65015 65016 64823 7381 12159 12159 i
    *> 147.249.196.0/24 172.20.18.1                   120      0 2001 65015 65016 64823 64870 65124 i
    *> 147.249.237.0/24 172.20.18.1                   120      0 2001 65015 65016 64823 7381 64681 i
    TOC-BP-SWa#sh ip bgp neighbors 10.14.0.3 received-r       
    Total number of prefixes 0 
    TOC-BP-SWa#sh ip bgp neighbors 10.14.0.2 received-r
    BGP table version is 1674320, local router ID is 10.14.0.1
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *>i10.14.0.2/32     10.14.0.2                0    100      0 i
    * i147.249.37.0/24  10.14.0.2                0    120      0 2001 65015 65016 64823 7381 64681 i
    * i147.249.38.0/24  10.14.0.2                0    120      0 2001 65015 65016 64823 7381 64681 i
    * i147.249.46.0/24  10.14.0.2                0    120      0 2001 65015 65016 64823 7381 12159 12159 i
    * i147.249.196.0/24 10.14.0.2                0    120      0 2001 65015 65016 64823 64870 65124 i
    * i147.249.237.0/24 10.14.0.2                0    120      0 2001 65015 65016 64823 7381 64681 i
    Can this output be duplicated with an OSPF command? 

    Not really because OSPF does not advertise routes it sends LSAs to it's peers.
    So you need to look at the OSPF database ie. -
    "sh ip ospf database"
    which will show you all the LSAs the router is aware of.
    In terms of all the LSAs the router has received it will show all of those but it will also show you LSAs that were generated by the router itself although the advertising router IP will point to that being the case.
    In terms of all the LSAs the router advertises again it depends on the area and how that has been configured.
    So for example an ABR might well have external LSAs (which aren't tied to any area in the OSPF database) but that doesn't necessarily mean it is advertising them to peers within an area as it could have been configured not to.
    So it gives you a good idea but you need to also work out a few things for yourself as well.
    Jon

  • How many BGP peers does the 3548 switch support?

    Is it possible to run more than 40 peers on a single switch? What is the limitation if not?

    Hi ,
     You can have 40 BGP peers , IPV4 unicast routes handled by hardware is only 24000 .Enusre all your BGP peering routing updates is within this limits . 
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3548-switch/data_sheet_c78-707001.html
    Table 7. Hardware Specifications Common to Both Switches
    Mode
    Normal Mode
    Warp Mode
    Hardware tables and scalability
    Number of MAC addresses
    64,000
    8000
    Number of IPv4 unicast routes
    24,000
    4000
    Number of IPv4 hosts
    64,000
    8000
    Number of IPv4 multicast routes
    8000
    8000
    Number of VLANS
    4096
    Number of ACL entries
    4096
    Number of spanning-tree instances
    Rapid Spanning Tree Protocol (RSTP): 512
    Multiple Spanning Tree (MST) Protocol: 64
    Number of EtherChannels
    24
    Number of ports per EtherChannel
    24
    Buffer size
    6 MB shared among 16 ports; 18 MB total
    Boot flash memory
    2 GB
    HTH
    Sandy

  • Back to Back VRF on same AS number possible?

    Hi experts,
    I am studying this B2B VRF thing and I built this lab and the diagram is attached.
    Basically R101 should learn the prefix 123.123.123.10/32 on R10 through both VPNv4 and B2B VRF. Sorry if I am using the wrong terminology here but hopefully you can understand me...
    So with only the VPNv4 peering ping works between R101 and R10 on their lo100 interfaces. R2 doesn't run BGP. It only handles labels. R4 is the RR. R101 and R3 build peering with R4.
    However the B2B vrf setup doesn't work. R4 can't learn the prefix from R101. The peering between R1 and R101 on the B2B VRF setup is on directly connected interface, not through loopback 0 interfaces like other BGP VPNv4 peering. R1 learned the prefix 123.123.123.101/32 from R101 fine. It also advertised to R4.
    Here are status on R1
    R1#sho bgp vpnv4 unicast vrf TEST 123.123.123.101/32
    BGP routing table entry for 65001:10:123.123.123.101/32, version 265
    Paths: (1 available, best #1, table TEST)
      Advertised to update-groups:
         1
      Refresh Epoch 1
      Local, (Received from a RR-client)
        172.20.0.2 from 172.20.0.2 (10.135.0.101)
          Origin IGP, metric 0, localpref 100, valid, internal, best
          Extended Community: RT:65001:65002
          mpls labels in/out 26/nolabel
    R1#sho bgp vpnv4 un all neighbors 10.135.0.4 advertised-routes
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65001:10 (default for vrf TEST)
    *>i 123.123.123.101/32
                           172.20.0.2               0    100      0 i
    However R4 is getting this error with "debug bgp updates" turned on so it is not accepting it
    *Jul  2 15:52:10.168: %BGP-3-INVALID_MPLS: Invalid MPLS label (15)
                 received in update for prefix 59648:0:175864699:101.0.0.0/8 from 10.135.0.1
    Please note that the number 175864699 is actually A7B7B7B and 7B is 123. I have a feeling that the R4 is interpreted it incorrectly so it doesn't recognize the prefix. Is it because the B2B VRF setup won't work with iBGP peering?
    Thanks!

    That doesn't do it.
    I have used the page up key to skip back to the top, but why should we have to do that when most other forums I post on have a "to the top" button?
    It is a little thing, but when they can't even keep the darn servers in sync, or even up at all for that matter, it seems huge.

  • Multiple BGP instances

    Hi All,
    We have a central location (can be called as HUB location) to which multiple branch locations connect over MPLS connectivity. Currenlty we are using non-Cisco device to terminate MPLS links in central location. CE-PE routing protocol used is BGP.
    Since there are multiple MPLS service providers are involved and each of them use different AS numbers, we made use of virtual routing instances to use multiple BGP instances.
    In future, we are planning to buy Cisco routers to terminate these MPLS links. As per our findings, Cisco ISR 4451-X suffice our requirement in terms of bandwidth, number of sessions etc...
    However, we are not able to find any document as such, which gives information of multiple BGP instances configuration or virtual router instance configuration.
    So, we would like to know whether Cisco 4451-X ISR supports multiple BGP instances?
    Also it would be helpful if anyone can help to know whether is there any possibility to cluster 4451-X routers or any other way to build redundancy in terms of hardware.
    Regards,
    Nagabhushan

    Unfortunately there seems to be little documentation on 4451-x so far. It is part of the ISR G2 family though and I think it is running IOS-XE.
    I would expect it to run same features as all ISR meaning that using VRFs should be no issue. You can then peer BGP within the VRFs. You could probably even run MPLS on it if you wanted to.
    I don't believe it has any clustering functionality. Hopefully someone from Cisco can clarify with more information.
    Daniel Dib
    CCIE #37149
    Please rate helpful posts.

  • EIGRP vs BGP route path selection scenario

    I am looking for a routing solution to the following scenario.  It is a fairly simple design. 
    I have two WAN connections between sites A and B.  One is a 20 Meg Metro Ethernet Circuit running EIGRP.  The other is a 10 Meg MPLS running BGP.  What do I need to do in my configuration to make sure that the 20 Meg connection is the chosen path based off the fact that it has better speed and bandwidth?  It appears to me that the MPLS is the preferred path even though it is slower.
    See attached Diagram:
    Site A Config
    interface GigabitEthernet1/0/12
     description PADC COX P2P 20 Meg
     no switchport
     bandwidth 20480
     ip address 172.20.1.1 255.255.255.252
    interface GigabitEthernet2/0/2
     description LEVEL 3 MPLS
     no switchport
     bandwidth 10240
     ip address 172.22.0.2 255.255.255.252
    router eigrp 1
     network 10.0.1.0 0.0.0.255
     network 172.20.1.0 0.0.0.3
     network 192.168.76.8 0.0.0.3
      redistribute bgp 65003 metric 100 1 255 1 1500 route-map MPLS_NETWORKS
     redistribute static route-map DEFAULT_ROUTE
    router bgp 65003
     bgp log-neighbor-changes
     redistribute static
     redistribute eigrp 1
     neighbor 172.22.0.1 remote-as 1
     default-information originate
    Site B Config
    interface GigabitEthernet0/1
     description COX Communications 10 Meg to Venyu
     bandwidth 20480
     ip address 172.20.1.2 255.255.255.252
     duplex auto
     speed auto
     service-policy output VOIP
    interface GigabitEthernet0/2
     description Level 3 MPLS
     bandwidth 10240
     ip address 172.22.1.2 255.255.255.252
     duplex full
     speed 100
    router eigrp 1
     network 10.3.1.0 0.0.0.31
     network 10.52.1.0 0.0.0.255
     network 10.76.6.0 0.0.0.255
     network 172.20.1.0 0.0.0.3
     network 192.168.63.64 0.0.0.63
     network 192.168.76.249 0.0.0.0
     passive-interface default
     no passive-interface GigabitEthernet0/0
     no passive-interface GigabitEthernet0/1
    router bgp 65003
     bgp log-neighbor-changes
     network 10.3.1.0 mask 255.255.255.224
     network 10.52.1.0 mask 255.255.255.0
     network 10.76.6.0 mask 255.255.255.0
     network 192.168.76.249 mask 255.255.255.255
     neighbor 172.22.1.1 remote-as 1

    If each router is receiving advertisements for the same networks/subnet masks from both BGP and EIGRP it will always choose the BGP routes because they have a lower AD ie. 20 vs EIGRP 90.
    Doesn't matter what the bandwidth is.
    If you want to prefer the 20Mbps links then there are a number of options -
    1) if you can summarise each sites subnets then advertise the summary via BGP and the more specific via EIGRP.  More specific will be chosen even before AD is taken into account.
    2) change the AD of either BGP or EIGRP so EIGRP ends up with the lower AD
    3) run BGP on both links although you would still need to manipulate the attributes to make sure the link you want is used.
    Jon

  • BGP Issue In MPLS Network

    we are having a gateway router which is running a public as and having a direct peering with service provider. We are also working as MPLS-SP and providing internet services to our esteemed clients. Now I am facing a one issue if the customer is coming at remote pop which is having a BGP with private as number and customer itself is having a global as number with his own ip pool. For that I created a peering with my gateway router by putting a route for loopback and created e-bgp peering. Now when the customer pool was advertised by my gateway it doesnot get the reverse path?
    Kindly give your suggestions or designs how the ebgp can be used with gateway router in case SP is runnig MPLS.
    regards
    shivlu jain

    Shivlu,
    Its not clear why u have Private-AS at one of ur POPs , while u could have the Same Public-AS configured and run IBGP session between Your PoPs. If you have Myltiple POPs than u can go for (Route-Reflector) design.
    The Second point, If you mean what type of Internet access, Then you can have one of the following:
    1- Classic Internet Access.
    2- a dedicated Vrf for Internet Access.
    HTH
    Mohamed

  • MP-BGP and MPLS multipath load sharing

    Hi,
    I am trying to PoC MPLS multi path load sharing by using per-PE-per-VRF RDs in the network.
    I have a simple lab setup with AS65000 which consists of SITE1 PE1&PE2 routers (10.250.0.101 and 10.250.0.102), route reflector RR in the middle (10.250.0.55) and SITE2 PE1&PE2 routers (10.250.0.201 and 10.250.0.202). PE routers only do iBGP peering with centralized route reflector and passing route to 10.1.1.0/24 prefix (learned from single CE router) with 100:1 and 100:2 RDs for specific VRF.
    Route reflector gets routes with multiple RDs, makes copies of these routes in order to make local comparison to RD 55:55 configured, uses these routes and install multiple paths into its routing table (all PE routers and RR have "maximum-paths eibgp 4" configured):
    RR#sh ip bgp vpnv4 all
    BGP table version is 7, local router ID is 10.250.0.55
    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: 55:55 (default for vrf VRF-A) VRF Router ID 10.250.0.55
    * i10.1.1.0/24      10.250.0.102             0    100      0 65001 i
    *>i                 10.250.0.101             0    100      0 65001 i
    Route Distinguisher: 100:1
    *>i10.1.1.0/24      10.250.0.101             0    100      0 65001 i
    Route Distinguisher: 100:2
    *>i10.1.1.0/24      10.250.0.102             0    100      0 65001 i
    RR#sh ip route vrf VRF-A
    <output omitted>
         10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
    B       10.1.1.0/24 [200/0] via 10.250.0.102, 00:45:52
                              [200/0] via 10.250.0.101, 00:46:22
    BUT, for some reason RR doest reflects routes with multiple RDs down to SITE2 PE1&PE2 - its own clients:
    RR#sh ip bgp vpnv4 all neighbors 10.250.0.201 advertised-routes
    Total number of prefixes 0
    RR#sh ip bgp vpnv4 all neighbors 10.250.0.202 advertised-routes
    Total number of prefixes 0
    Here comes RR BGP configuration:
    router bgp 65000
    no synchronization
    bgp router-id 10.250.0.55
    bgp cluster-id 1.1.1.1
    bgp log-neighbor-changes
    neighbor 10.250.0.101 remote-as 65000
    neighbor 10.250.0.101 update-source Loopback0
    neighbor 10.250.0.101 route-reflector-client
    neighbor 10.250.0.101 soft-reconfiguration inbound
    neighbor 10.250.0.102 remote-as 65000
    neighbor 10.250.0.102 update-source Loopback0
    neighbor 10.250.0.102 route-reflector-client
    neighbor 10.250.0.102 soft-reconfiguration inbound
    neighbor 10.250.0.201 remote-as 65000
    neighbor 10.250.0.201 update-source Loopback0
    neighbor 10.250.0.201 route-reflector-client
    neighbor 10.250.0.201 soft-reconfiguration inbound
    neighbor 10.250.0.202 remote-as 65000
    neighbor 10.250.0.202 update-source Loopback0
    neighbor 10.250.0.202 route-reflector-client
    neighbor 10.250.0.202 soft-reconfiguration inbound
    no auto-summary
    address-family vpnv4
      neighbor 10.250.0.101 activate
      neighbor 10.250.0.101 send-community both
      neighbor 10.250.0.102 activate
      neighbor 10.250.0.102 send-community both
      neighbor 10.250.0.201 activate
      neighbor 10.250.0.201 send-community both
      neighbor 10.250.0.202 activate
      neighbor 10.250.0.202 send-community both
    exit-address-family
    address-family ipv4 vrf VRF-A
      maximum-paths eibgp 4
      no synchronization
      bgp router-id 10.250.0.55
      network 10.255.1.1 mask 255.255.255.255
    exit-address-family
    SITE1 PE1 configuration:
    router bgp 65000
    no synchronization
    bgp router-id 10.250.0.101
    bgp log-neighbor-changes
    neighbor 10.250.0.55 remote-as 65000
    neighbor 10.250.0.55 update-source Loopback0
    neighbor 10.250.0.55 soft-reconfiguration inbound
    no auto-summary
    address-family vpnv4
      neighbor 10.250.0.55 activate
      neighbor 10.250.0.55 send-community both
    exit-address-family
    address-family ipv4 vrf VRF-A
      neighbor 10.1.101.2 remote-as 65001
      neighbor 10.1.101.2 activate
      neighbor 10.1.101.2 soft-reconfiguration inbound
      maximum-paths eibgp 4
      no synchronization
      bgp router-id 10.250.0.101
    exit-address-family
    SITE1 PE2 configuration is similar to SITE1 PE1. They both do eBGP peering with dualhomed CE router in AS65001 which announces 10.1.1.0/24 prefix into VRF-A table.
    My question is: clearly, the issue is that RR doesn't reflect any routes to its clients (SITE2 PE1&PE2) for 10.1.1.0/24 prefix with 100:1 and 100:2 RDs that dont match it's locally configured RD 55:55 for VRF-A, although they are present in its BGP/RIB tables and used for multipathing. Is this an expected behavior or some feature limitation for specific platform or IOS version? Currently, in this test lab setup I run IOS 12.4(24)T8 on all the devices.
    Please, let me know if any further details are needed to get an idea of why this well known and widely used feature is not working correctly in my case. Thanks a lot!
    Regards,
    Sergey

    Hi Ashish,
    I tried to remove VRF and address family configurations completely from RR.
    router bgp 65000
    no synchronization
    bgp router-id 10.250.0.55
    bgp cluster-id 1.1.1.1
    bgp log-neighbor-changes
    neighbor 10.250.0.101 remote-as 65000
    neighbor 10.250.0.101 update-source Loopback0
    neighbor 10.250.0.101 route-reflector-client
    neighbor 10.250.0.101 soft-reconfiguration inbound
    neighbor 10.250.0.102 remote-as 65000
    neighbor 10.250.0.102 update-source Loopback0
    neighbor 10.250.0.102 route-reflector-client
    neighbor 10.250.0.102 soft-reconfiguration inbound
    neighbor 10.250.0.201 remote-as 65000
    neighbor 10.250.0.201 update-source Loopback0
    neighbor 10.250.0.201 route-reflector-client
    neighbor 10.250.0.201 soft-reconfiguration inbound
    neighbor 10.250.0.202 remote-as 65000
    neighbor 10.250.0.202 update-source Loopback0
    neighbor 10.250.0.202 route-reflector-client
    neighbor 10.250.0.202 soft-reconfiguration inbound
    no auto-summary
    address-family vpnv4
      neighbor 10.250.0.101 activate
      neighbor 10.250.0.101 send-community both
      neighbor 10.250.0.102 activate
      neighbor 10.250.0.102 send-community both
      neighbor 10.250.0.201 activate
      neighbor 10.250.0.201 send-community both
      neighbor 10.250.0.202 activate
      neighbor 10.250.0.202 send-community both
    exit-address-family
    After this, RR doesn't accept any routes at all from S1PE1&S1PE2 routers, thus not reflecting any routes down to its clients S2PE1&S2PE2 as well:
    S1PE1#sh ip bgp vpnv4 all
    BGP table version is 6, local router ID is 10.250.0.101
    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: 100:1 (default for vrf VRF-A) VRF Router ID 10.250.0.101
    *> 10.1.1.0/24      10.1.101.2               0             0 65001 i
    S1PE1#sh ip bgp vpnv4 all neighbors 10.250.0.55 advertised-routes
    BGP table version is 6, local router ID is 10.250.0.101
    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: 100:1 (default for vrf VRF-A) VRF Router ID 10.250.0.101
    *> 10.1.1.0/24      10.1.101.2               0             0 65001 i
    Total number of prefixes 1
    S1PE2#sh ip bgp vpnv4 all
    BGP table version is 6, local router ID is 10.250.0.102
    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: 100:2 (default for vrf VRF-A) VRF Router ID 10.250.0.102
    *> 10.1.1.0/24      10.1.201.2               0             0 65001 i
    S1PE2#sh ip bgp vpnv4 all neighbors 10.250.0.55 advertised-routes
    BGP table version is 6, local router ID is 10.250.0.102
    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: 100:2 (default for vrf VRF-A) VRF Router ID 10.250.0.102
    *> 10.1.1.0/24      10.1.201.2               0             0 65001 i
    Total number of prefixes 1
    RR#sh ip bgp vpnv4 all
    RR#sh ip bgp vpnv4 all neighbors 10.250.0.101 routes
    Total number of prefixes 0
    RR#sh ip bgp vpnv4 all neighbors 10.250.0.102 routes
    Total number of prefixes 0
    Any feedback is appreciated. Thanks.
    Regards,
    Sergey

Maybe you are looking for