BGP default route advertisement - change preference

hi guys,
I would appreciate some assistance here. We have a primary head office & a DR site. Routers at both sites connect to our carrier for an IP VPN service using BGP. BGP configs on each router advertise a default route 0.0.0.0.
   #sh ip bgp neighbors x.x.x.x advertised-routes
      BGP table version is 358, local router ID is x.x.x.x
      Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
      Origin codes: i - IGP, e - EGP, ? - incomplete
      Originating default network 0.0.0.0
Issue is, some of our remote sites prefer the DR router path for traffic destined to internet.
We are advertising multiple default routes to our carrier, and based on feedback from carrier, route with lowest MED is preferred.
This brings me to what i need to change from my side. Need to change the route preference so that from our remote offices, only the route to head office is preferred with DR site the least preferred route. I know there are multliple ways of doing this, however keen to get input from the experts out there.
DR site router has this BGP config currently applied:
   router bgp XXXXX
    bgp log-neighbor-changes
    redistribute connected
    redistribute ospf 1 match internal external 1 external 2
    neighbor x.x.x.x remote-as XXXX
    neighbor x.x.x.x default-originate
    neighbor x.x.x.x soft-reconfiguration inbound
    neighbor x.x.x.x route-map IMPORT-POLICY in
    neighbor x.x.x.x route-map OPI-route-advertisement out
    default-information originate
Removing the  "neighbor x.x.x.x default-originate" is not an option, as we need to have the ability to failover to DR at any point.
Thanks in advance & if you need any further info pls advise.
Rama

Hi Milan,
Thanks. Answers below:
Does it provide an MPLS backbone to you? YES
Are you using the same AS number on all your sites or different ones? Same AS
Any way, what about advertising the default route from your DR site with the site AS number prepended several times (5 times, e.g.)? That's the thing I am struggling to understand as the route-map OPI-route-advertisement already has it prepended 2 times. Shouldn't that be enough to influence which route is least preferred?
route-map OPI-route-advertisement permit 20
 match ip address prefix-list xxx default-route
 set as-path prepend XXXXX XXXXX
If your provider would permit that and hasn't configured his routers to ignore the AS_PATH length (as him a question), it should make the default route advertised from your DR less preferred within your backbone. Will ask.
Given this, any other thoughts/questions?
Thanks, Rama

Similar Messages

  • Bgp default route-target filter

    Hi folks,
    how that command works, and why it don't need to be configured on an ASBR that is functioning as RR?
    Thank you very much for your support
    Regards
    Andrea

    By default, a cisco router will filter out prefixes that contain a route-target that is not use locally on that router.
    This check is disabled when you configure a route-reflector-client, since the client may need one of those routes.
    On an ASBR that IS already a RR, you don't need to mess with this command because the rt filter check is already turned off.
    However, if your ASBR is not a RR ( or doesn't have a particular VPN configured locally) and you need to advertise VPN prefixes to another AS, then you need to turn this check off or the ASBR will filter out the prefixes when they are received from its internal peers, so it will not have them to advertise to another else. In this case, you would do a "no bgp default route-target filter" on the ASBR so the routes are accepted even though they will not be used locally.
    HTH
    -Rob

  • Inject BGP Default Routes into Multiple VRF before Best Path Selection

    Hello, 
    I have the following setup:
    Multiple Border Routers with eBGP sessions to external AS. We receive a default route from this multiple AS to keep the Table manageable. We noticed an important part of our traffic was been SW routed instead of CEF when we had the Full Internet table. Router Resources came to the ground when we changed to a default. 
    Now I want to separate this default routes into different VRF. Attached is the Diagram. 
    My question is,  the multiple default route all go into the BGP Table. The BGP table then select the best route and place it on the RIB and then to the FIB. 
    I want to redistribute the different Route on the BGP table prior to the Best path selection algorithm and placed on the RIB. 
    How can I achieve this?

    Hi,
    Redistribution of multiple routes to same prefix is not possible. Even if you have configured BGP multipath and all different bgp routes got installed into routing table, during redistribution only route will be redistributed. 
    Also would like to understand the requirement of redistributing multiple BGP routes in to IGP. As per your diagram, 3 different eBGP sessions are on three different routers, so you can prefer eBGP route over iBGP received from other routers and can distribute eBGP route to IGP from each router. Thus you will have three different default routes in to IGP in core.
    Please don't forget to rate this post if it has been helpful
    - Akash

  • MP-BGP and Route-Reflector

    Hi All...
    I have this topology:
    CE2-->PE1-->P--->PE2-->CE2
    .............\-->PE3-->CE2
    In router "P" I want to configure MP-BGP, but I have many doubts with configurations this router. I need to do route-reflector too.
    Anybody can help me?
    CLRGomes

    Thanks, look my configuration:
    Router P
    router bgp 65500
    no synchronization
    no bgp default route-target filter
    bgp log-neighbor-changes
    neighbor MPLS peer-group
    neighbor MPLS remote-as 65500
    neighbor MPLS ebgp-multihop 255
    neighbor MPLS update-source Loopback0
    neighbor MPLS route-reflector-client
    neighbor MPLS allowas-in
    neighbor MPLS soft-reconfiguration inbound
    neighbor 10.10.10.2 peer-group MPLS
    neighbor 10.10.10.3 peer-group MPLS
    neighbor 10.10.10.4 peer-group MPLS
    no auto-summary
    address-family vpnv4
    neighbor MPLS route-reflector-client
    neighbor MPLS send-community both
    neighbor 10.10.10.2 activate
    neighbor 10.10.10.3 activate
    neighbor 10.10.10.4 activate
    exit-address-family
    ok...working perfect, I did MP-BGP between PE routers and I configured RDs differents too...
    Later I did between PE->CE with OSPF and working too, loadshare working.
    Thanks a lot
    CLRGomes
    CCIE R&S

  • Changing default route after import route-target

    Hi there,
    Before I import route-target, the default route is set to 192.168.0.22 . After import the vrf, suddently it change to another PE, which is 192.168.0.19 . How do I force the default route to use 192.168.0.22 ?
    before adding route-target import 4000:1
    PE#sh ip route vrf customer 0.0.0.0
    Routing entry for 0.0.0.0/0, supernet
    Known via "bgp 100", distance 200, metric 0, candidate default path,
    type internal
    Last update from 192.168.0.22 00:14:08 ago
    Routing Descriptor Blocks:
    * 192.168.0.22 (Default-IP-Routing-Table), from 192.168.0.3, 00:14:08 ago
    Route metric is 0, traffic share count is 1
    AS Hops 0
    PE#sh ip bgp vpnv4 vrf customer 0.0.0.0
    BGP routing table entry for 100:239:0.0.0.0/0, version 335256
    Paths: (2 available, best #2, table customer)
    Not advertised to any peer
    Local
    192.168.0.22 (metric 4) from 192.168.0.45 (192.168.0.45)
    Origin incomplete, metric 0, localpref 100, valid, internal
    Extended Community: RT:100:120
    Originator: 192.168.0.50, Cluster list: 192.168.0.45
    Local
    192.168.0.22 (metric 4) from 192.168.0.3 (192.168.0.3)
    Origin incomplete, metric 0, localpref 100, valid, internal, best
    Extended Community: RT:100:120
    Originator: 192.168.0.50, Cluster list: 192.168.0.3
    after adding route-target import 4000:1
    PE#sh ip route vrf customer 0.0.0.0
    Routing entry for 0.0.0.0/0, supernet
    Known via "bgp 100", distance 200, metric 0, candidate default path,
    type internal
    Last update from 192.168.0.19 00:00:09 ago
    Routing Descriptor Blocks:
    * 192.168.0.19 (Default-IP-Routing-Table), from 192.168.0.3, 00:00:09 ago
    Route metric is 0, traffic share count is 1
    AS Hops 0
    PE#sh ip bgp vpnv4 vrf customer 0.0.0.0
    BGP routing table entry for 100:239:0.0.0.0/0, version 335386
    Paths: (3 available, best #1, table customer)
    Flag: 0x1820
    Not advertised to any peer
    Local, imported path from 4000:1:0.0.0.0/0
    192.168.0.19 (metric 2) from 192.168.0.3 (192.168.0.3)
    Origin incomplete, metric 0, localpref 100, valid, internal, best
    Extended Community: RT:4000:1
    Originator: 192.168.0.19, Cluster list: 192.168.0.3
    Local
    192.168.0.22 (metric 4) from 192.168.0.45 (192.168.0.45)
    Origin incomplete, metric 0, localpref 100, valid, internal
    Extended Community: RT:100:120
    Originator: 192.168.0.50, Cluster list: 192.168.0.45
    Local
    192.168.0.22 (metric 4) from 192.168.0.3 (192.168.0.3)
    Origin incomplete, metric 0, localpref 100, valid, internal
    Extended Community: RT:100:120
    Originator: 192.168.0.50, Cluster list: 192.168.0.3
    thanks in advance.
    maher

    Maher,
    Here's an example:
    router bgp xx
    address-family vpnv4
    nei x.x.x.x route-map localpref in
    ip extcommunity 1 permit rt 4000:1
    route-map localpref permit 10
    match extcommunity 1
    set local-preference 110
    route-map localpref permit 20
    BTW: if the route with RT 4000:1 had a different RD both routes would get imported in the VRF and you could set the local-pref using an import map instead of an inbound route-map on the VPNv4 session.
    Hope this helps,

  • BGP peering via default route

    I read http://blog.ipexpert.com/2010/11/08/bgp-peering-and-default-routes/ and understood that BGP speaker will not initiate BGP connection with the other BGP router if it can reach it via default route only...And BGP peering will not come up at all if both the BGP speakers know each other via default routes only....I could not understand the reason behind this though...Could any expert help me in understanding the underlying reasoning?

    I can't think of a reason why you would want to peer with a router you don't have a route for. If you're relying on a default route for a multi-hop bgp peer session, it could cause the session to be unreliable due to changes in the network down the line from you. An unreliable bgp session would be bad on the router's cpu/memory if the session were to flap.

  • ASA 5520 - Can not change default route.

    Hi
    My asa is sitting behind a router the next hop from the ASA to the router is 10.0.0.5 I have tried to change the default route to route DMZ 0 0 10.0.0.5  to no availability right now the default route is (S*   0.0.0.0 0.0.0.0 [1/0] via 172.16.8.20, Outside) but even if I were to do a "no route Outside 0 0 172.16.8.20" the default route does not disappear when I do a "sh route" command. ant help would be greatly appreciated.

    I apologize for not being clear hopefully this helps. Basically the  default route should be: route DMZ 0.0.0.0 0.0.0.0 10.10.10.5, I had to  add a metric of 2 because otherwise it would conflict with the Gateway  of last resort, the interesting part is if I try to remove the current  gateway of last resort then the error I get is  %No matching route to delete and I try to add the new route I get ERROR: Cannot add route entry, conflict with existing routes.
    **"show ip address" output---
    Interface                Name                   IP address      Subnet mask     Method
    GigabitEthernet0/0       Outside               172.22.8.166    255.255.252.0   CONFIG
    GigabitEthernet0/3       DMZ                   10.10.10.16     255.255.255.0   CONFIG
    Management0/0            management      192.168.100.1   255.255.255.0   CONFIG
    GigabitEthernet1/0       Inside                 172.16.0.2      255.255.252.0   CONFIG
    GigabitEthernet1/1       VPN                    X.X.X.X          255.255.255.240 CONFIG
    Current IP Addresses:
    Interface                Name                   IP address      Subnet mask     Method
    GigabitEthernet0/0       Outside               172.22.8.166    255.255.252.0   CONFIG
    GigabitEthernet0/3       DMZ                   10.10.10.16     255.255.255.0   CONFIG
    Management0/0            management      192.168.100.1   255.255.255.0   CONFIG
    GigabitEthernet1/0       Inside                 172.16.0.2      255.255.252.0   CONFIG
    GigabitEthernet1/1       VPN                    X.X.X.X          255.255.255.240 CONFIG
    **"show running-config" output---
    !The DMZ route should be the gateway of last resort
    route DMZ 0.0.0.0 0.0.0.0 10.10.10.5 2
    route Outside 10.0.1.0 255.255.255.252 172.22.8.20 1
    route Outside 10.0.2.0 255.255.255.252 172.22.8.20 1
    route Outside 10.0.4.0 255.255.255.252 172.22.8.20 1
    route Outside 10.0.5.0 255.255.255.240 172.22.8.20 1
    route Outside 10.0.6.0 255.255.255.252 172.22.8.20 1
    route Outside 10.0.25.0 255.255.255.0 172.22.8.20 1
    route Outside 10.0.52.0 255.255.255.0 172.22.8.20 1
    route Inside 172.16.0.0 255.255.252.0 172.16.0.3 1
    route Outside 172.16.6.0 255.255.255.0 172.16.6.1 1
    route Outside 172.22.0.0 255.255.0.0 172.22.8.20 10
    route Outside 192.168.0.0 255.255.255.0 172.22.8.20 255
    route DMZ 192.168.200.0 255.255.255.0 156.108.124.66 1
    **"show route" output ---
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
           * - candidate default, U - per-user static route, o - ODR
           P - periodic downloaded static route
    Gateway of last resort is 172.22.8.20 to network 0.0.0.0
    S    172.16.6.0 255.255.255.0 [1/0] via 172.16.6.1, Outside
                                  [1/0] via 172.22.8.20, Outside
    C    172.16.0.0 255.255.252.0 is directly connected, Inside
    C    172.22.8.0 255.255.252.0 is directly connected, Outside
    S    172.22.0.0 255.255.0.0 [10/0] via 172.22.8.20, Outside
    D    192.168.4.8 255.255.255.252 [90/2178816] via 172.16.0.3, 66:37:21, Inside
    D    192.168.4.9 255.255.255.255 [90/2178816] via 172.16.0.3, 66:37:21, Inside
    S    10.0.2.0 255.255.255.252 [1/0] via 172.22.8.20, Outside
    D    10.0.0.0 255.255.255.0 [90/3072] via 172.16.0.3, 66:37:21, Inside
    C    10.10.10.0 255.255.255.0 is directly connected, DMZ
    S    10.0.1.0 255.255.255.252 [1/0] via 172.22.8.20, Outside
    S    10.0.6.0 255.255.255.252 [1/0] via 172.22.8.20, Outside
    S    10.0.4.0 255.255.255.252 [1/0] via 172.22.8.20, Outside
    S    10.0.5.0 255.255.255.240 [1/0] via 172.22.8.20, Outside
    S    10.0.25.0 255.255.255.0 [1/0] via 172.22.8.20, Outside
    S    10.0.52.0 255.255.255.0 [1/0] via 172.22.8.20, Outside
    S    192.168.0.0 255.255.255.0
               [255/0] via 172.22.8.20, Outside
    D    192.168.100.0 255.255.255.0 [90/3072] via 172.16.0.3, 66:37:21, Inside
    ! I have tried to remove the route below with the command "no  route Outside 0 0 172.22.8.20" but always get the error %No matching  route to delete
    S*   0.0.0.0 0.0.0.0 [1/0] via 172.22.8.20, Outside

  • CSS advertise OSPF default route?

    I have a CSS in one armed mode sitting between the Internet Edge router and PIX firewall.
    The edge router is getting a default route from BGP and distributes that into the Firewall via OSPF.
    The firewall sees the Edge router as the default gateway from the distributed route.
    Would it be possible to have the CSS (through OSPF) get the default route from the Edge router and advertise it to the Firewall?
    The goal is to have the Firewall use the CSS as it's default gateway, rather than the Edge router, but it needs to be a dynamic route.
    In turn the edge router would pass traffic through the CSS to the firewall.
    The CSS would be an intermidiate hop between the router and firewall.
    Is this something that the CSS is capable of doing?
    And from a design perspective, it is something that could be an issue?

    Thanks,
    I did see that document and played with it some last night.
    I think it should work too, but was not sure if it was not reccomended by Cisco or not.
    I have seen they they do not reccomend OSPF or RIP configurations, but I am only concerned with the default route and this would maybe solve the problem of any potential asymetric traffic flow.

  • Modify the preference value of the default route

    Hi
    How to achieve the Below ? any configuration example?
    1)How to modify the preference value of the default route to be less prefered than OSPF External route
    2)how to redistribute the default route as type 2 external route
    3)how to redistribute the default route as type 1 external route
    thanks

    Hi Ibrahim,
    See below:
    1) Can you elaborate on this a bit? Can you explain, specifically, what your trying to accomplish? I don't think you can get a default route into the OSPF RIB that is not external as the default is injected as a Type-5 LSA (e1 or e2). If your talking about getting a router to use the OSPF learned default over the default router learned via some other source (e.g. static, BGP, etc), then it depends on the source because of the Administrative Distance when comparing the two defaults ( the one default learned via OSPF has AD=110, and the other default is AD=X, where X is the Administrative Distance assigned to the protocol).
    2) Use the "default-information originate metric-type 2" command under "router ospf" -- Note this is the default
    3) Use the "default-information originate metric-type 1" command under "router ospf" -- Note, you don't need this in Totally Stubby Area.
    4) For NSSA area you have to use the "area nssa <area_num> default information-originate metric-type <type>" router subcommand. Note your NSSA should have a Type-7 LSA for the default route
    Rate if helpful.
    Joe

  • All default routing value has to be changed, while changed the work center in production order

    Dear friends,
    our client they want to change the work center in production order.according to production version work center also they are changed.so while change the WC,all the default value has be changed as per routing what we maintained in routing.At present we have to enter the manually change the W.C as well as set up time and operation time enter manually.Any other option to do the automatically capture value from routing while change in Work center in production order.pl help me on this.
    Thanks&Regards
    Sabhapathy R

    Hi Rahul,
    Thanks for reply. I am maintained in diff value  maintained routing , Ex :First routing i have  work center 'X' value maintained as a setup time in 15 Min's and operation time 10 Min's
    second work center 'Y' I have maintained as set up time 10 Min's and operation time 30 Min's,
    Now I want to change the work center in production order as a 'Y' so whatever value maintained in routing , it has to be changed automatically (10 min's and 30 Min's), but system will not change only old value only picked (15Min's AND 10 Min's).
    Now I think you get to know what the client requirement, kindly do the need full.
    Regards,
    Sabhapathy R

  • 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

  • Does anyone know how to change where incoming (via mail) calendar requests go on my MacBook? Mine insist on going to Entourage, which I don't use any more. I've tried setting the default calendar in iCal preferences. Doesn't help. Bugs me. Can you help?

    Does anyone know how to change where incoming (via mail) calendar requests go on my MacBook? Mine insist on going to Entourage, which I don't use any more. I've tried setting the default calendar in iCal preferences. Doesn't help. Bugs me. Can you help?

    Jneklason wrote:
    ~snip~
    I know this email is confusing and really hard to understand...perhaps now you will know how i've been feeling--lost and confused with all the mis-information, with a hit and miss phone, and out of time with all the 1 1/2 hr to 2 hrs EACH wasted on this issue.
    On top of all this, I can't even find out how to file a complaint with anyone higher up than Customer Service.
    I hate to tell you this, but you didn't write an email. You wrote a discussion post on the Verizon Wireless Community forum which is a public peer to peer forum. Unfortunately since you didn't mark your post as a question, the VZW reps that roam this community won't ever see your post. Before you re-post it, don't. Duplicate posts get removed from the community.
    I see there were several missteps both by the reps and yourself in your post. First you should have insisted on returning the phone within the 14 day return policy period. Second which Samsung Galaxy mini model did you purchase? The S3 mini or the S4 mini? Did you do any research prior to deciding on this device. The reps at that time deflected the easiest course of action, by trying to get you to replace the phone under insurance instead of returning the phone. The Early Edge payment option requires the current phone on the line using the early Edge must be returned to Verizon Wireless. Did you once considered going to a third party site like Swappa to purchase a gently used device for your daughter?

  • BGP route advertisement

    I am confused about which routes will a bgp speaker advertise to its bgp neighbors?
    Will it advertise the bgp routes in routing table OR will it advertise the best routes from the bgp table (but not necessarily in routing table)?

    Thanks!!
    I thought so, but in Troubleshooting IP Routing Protocols book by Cisco press, it is stated that bgp router will advertise its routes from routing table, so wanted to confirm that that was indeed wrong.
    On page 668, this is what is written:
    One rule that BGP follows when advertising prefixes to other neighbors is that the prefix being advertised must
    exist in the routing table of the advertising router.

  • Ipv6 Default route bgp

    Hi,
    I am reciving a default route on bgp over ipv6 by my service provider. I want to control to only recive the default route, but when I ask for full table I recived all the routes, I don't know how to control the prefix to only recived the default route, this is what I have (ios XR):
    prefix-set IPv6
      ::/0 le 128
    end-set
    route-policy PERMIT_IPv6
      if destination in IPv6 then
        pass
      endif
    end-policy
    router bgp 279xx
    vrf INTERNET
    neighbor 2800:xxxx:x:x:x:x:x:x
    remote-as 523xx
    description eBGP GlobeNetIPV6
    update-source Bundle-Ether4.663
    address-family ipv6 unicast
    route-policy PERMIT_IPv6 in
    route-policy IPV6_OUT out
    Sorry for my english.

    pdriver answer is the right one, you are allowing all routes
    prefix-set IPv6
      ::/0 le 128
    end-set
    it allows :: from mask 0 to mask 128, just remove the "le 128"

  • BGP Community | Route-Map | Local Pref

    While labbing today I've ran into some strange behavior with BGP communities/route-map processing. Basically the objective was from R9, send a community for the 172.30.79.0/27 route out to R7 to 65100:90 AND send a community for the 172.30.89.0/27 route out to R8 to 65100:110. Then on R9 match community 65100:90 and set the local-pref to 90 and 65100:110 to local-pref of 110. Should be easy enough but the behavior that i'm seeing is that all is working on R7 but not on R8. The R8 inbound route-map is watching the community but not setting the local-pref for some reason... Any ideas? See below.
    Topology
    ##R9’s BGP/Route-map config setting communities for the two routes out to R7 & R8##
    R9#sh run  | s bgp|route-map
    router bgp 65100
     network 172.30.79.0 mask 255.255.255.224
     network 172.30.89.0 mask 255.255.255.224
     network 192.122.3.9 mask 255.255.255.255
     neighbor 172.30.79.7 remote-as 65006
     neighbor 172.30.79.7 send-community both
     neighbor 172.30.79.7 route-map R7-OUT out
     neighbor 172.30.89.8 remote-as 65006
     neighbor 172.30.89.8 send-community both
     neighbor 172.30.89.8 route-map R8-OUT out
    ip bgp-community new-format
    route-map R7-OUT permit 10
     match ip address prefix-list 172.30.79.0/27
     set community 65100:90
    route-map R7-OUT permit 20
    route-map R8-OUT permit 10
     match ip address prefix-list 172.30.89.0/27
     set community 65100:110
    route-map R8-OUT permit 20
    ##R7’s config##
    R7#sh run | s bgp|route-map
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.79.9 remote-as 65100
      neighbor 172.30.79.9 activate
      neighbor 172.30.79.9 send-community both
      neighbor 172.30.79.9 as-override
      neighbor 172.30.79.9 route-map R9-IN in
    route-map R9-IN permit 10
     match community 65100:90
     set local-preference 90
    route-map R9-IN permit 20
    ##R7’s ‘show bgp’##
    R7#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65066:700 (default for vrf VPN)
     r>  172.30.79.0/27   172.30.79.9           90              0 65100 i
     *>  172.30.89.0/27   172.30.79.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.79.9              0             0 65100 i
    ##R8’s config##
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.89.9 remote-as 65100
      neighbor 172.30.89.9 activate
      neighbor 172.30.89.9 send-community both
      neighbor 172.30.89.9 as-override
      neighbor 172.30.89.9 route-map R9-INv2 in
    route-map R9-INv2 permit 10
     match community 65100:110
     set local-preference 110
    route-map R9-INv2 permit 20
    ##R8’s ‘show bgp’##
    R8#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     *>  172.30.79.0/27   172.30.89.9              0             0 65100 i
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN community | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN 172.30.89.0/27         
    BGP routing table entry for 65006:800:172.30.89.0/27, version 77
    Paths: (1 available, best #1, table VPN, RIB-failure(17))
      Not advertised to any peer
      Refresh Epoch 2
      65100
        172.30.89.9 from 172.30.89.9 (192.122.3.9)
          Origin IGP, metric 0, localpref 100, valid, external, best
          Community: 65100:110
          Extended Community: RT:910:910
          mpls labels in/out 45/nolabel
          rx pathid: 0, tx pathid: 0x0

    While labbing today I've ran into some strange behavior with BGP communities/route-map processing. Basically the objective was from R9, send a community for the 172.30.79.0/27 route out to R7 to 65100:90 AND send a community for the 172.30.89.0/27 route out to R8 to 65100:110. Then on R9 match community 65100:90 and set the local-pref to 90 and 65100:110 to local-pref of 110. Should be easy enough but the behavior that i'm seeing is that all is working on R7 but not on R8. The R8 inbound route-map is watching the community but not setting the local-pref for some reason... Any ideas? See below.
    Topology
    ##R9’s BGP/Route-map config setting communities for the two routes out to R7 & R8##
    R9#sh run  | s bgp|route-map
    router bgp 65100
     network 172.30.79.0 mask 255.255.255.224
     network 172.30.89.0 mask 255.255.255.224
     network 192.122.3.9 mask 255.255.255.255
     neighbor 172.30.79.7 remote-as 65006
     neighbor 172.30.79.7 send-community both
     neighbor 172.30.79.7 route-map R7-OUT out
     neighbor 172.30.89.8 remote-as 65006
     neighbor 172.30.89.8 send-community both
     neighbor 172.30.89.8 route-map R8-OUT out
    ip bgp-community new-format
    route-map R7-OUT permit 10
     match ip address prefix-list 172.30.79.0/27
     set community 65100:90
    route-map R7-OUT permit 20
    route-map R8-OUT permit 10
     match ip address prefix-list 172.30.89.0/27
     set community 65100:110
    route-map R8-OUT permit 20
    ##R7’s config##
    R7#sh run | s bgp|route-map
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.79.9 remote-as 65100
      neighbor 172.30.79.9 activate
      neighbor 172.30.79.9 send-community both
      neighbor 172.30.79.9 as-override
      neighbor 172.30.79.9 route-map R9-IN in
    route-map R9-IN permit 10
     match community 65100:90
     set local-preference 90
    route-map R9-IN permit 20
    ##R7’s ‘show bgp’##
    R7#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65066:700 (default for vrf VPN)
     r>  172.30.79.0/27   172.30.79.9           90              0 65100 i
     *>  172.30.89.0/27   172.30.79.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.79.9              0             0 65100 i
    ##R8’s config##
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.89.9 remote-as 65100
      neighbor 172.30.89.9 activate
      neighbor 172.30.89.9 send-community both
      neighbor 172.30.89.9 as-override
      neighbor 172.30.89.9 route-map R9-INv2 in
    route-map R9-INv2 permit 10
     match community 65100:110
     set local-preference 110
    route-map R9-INv2 permit 20
    ##R8’s ‘show bgp’##
    R8#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     *>  172.30.79.0/27   172.30.89.9              0             0 65100 i
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN community | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN 172.30.89.0/27         
    BGP routing table entry for 65006:800:172.30.89.0/27, version 77
    Paths: (1 available, best #1, table VPN, RIB-failure(17))
      Not advertised to any peer
      Refresh Epoch 2
      65100
        172.30.89.9 from 172.30.89.9 (192.122.3.9)
          Origin IGP, metric 0, localpref 100, valid, external, best
          Community: 65100:110
          Extended Community: RT:910:910
          mpls labels in/out 45/nolabel
          rx pathid: 0, tx pathid: 0x0

Maybe you are looking for