Re: MPLS VPN Route Target Rewrite

Gaurav,
Thank you for your response. I see that the prefix list is matched and tags
the route with extcommunity RT of 100:55 on R5 exporting it....

R5#sh ip prefix-list detail
Prefix-list with the last deletion/insertion: LO101
ip prefix-list LO101:
   count: 1, range entries: 0, sequences: 5 - 5, refcount: 3
   seq 5 permit 172.16.5.0/24 (*hit count: 9*, refcount: 1)

R5#sh ip bgp vpnv4 al 172.16.5.0
BGP routing table entry for 100:1:172.16.5.0/24, version 23
Paths: (1 available, best #1, table VPN_A)
  Advertised to update-groups:
        1
  Local
    0.0.0.0 from 0.0.0.0 (150.1.5.5)
      Origin incomplete, metric 0, localpref 100, weight 32768, valid,
sourced, best
      Extended Community: *RT:100:55*
      mpls labels in/out 25/aggregate(VPN_A)

Thanks

TK

On Sun, Jan 30, 2011 at 10:01 AM, GAURAV MADAN <gauravmadan1177_at_gmail.com>wrote:

> Your import stuff is looking good to me .
>
> Just check that when you are applying export-map ; you have configured
> the prefix-list very clearly and its hitting the prefix-list . The
> mistake that generally I commit is .. prefix is in VPN table as /32
> and sometimes i am trying to match /24 ..
>
> Please check the exact route in VPN table and make sure your prefic
> list is being hitt .
>
> That will make sure that your export-map is fine
>
> Let me know your findings .
>
> Thanks
> Gaurav Madan
>
> On Sun, Jan 30, 2011 at 9:19 PM, Tom Kacprzynski <tom.kac_at_gmail.com>
> wrote:
> > Carlos,
> > Thank you for your reply. My configuration is below, but basically i'm
> > trying to take the route 172.16.5.0/24 from VPN_A on R5, rewrite its
> > extended community route tag to 100:55 and have that route-tag imported
> into
> > VPN_B on R6. I have to say that it does work in terms that only VPN_B
> sees
> > it, but i don't understand why it shows that route in both BGP VPNv4
> tables
> > for VPN_A and VPN_B.
> >
> > R6#
> > ip vrf VPN_A
> > rd 100:1
> > route-target export 100:1
> > route-target import 100:1
> > ip vrf VPN_B
> > rd 100:2
> > route-target export 100:2
> > route-target import 100:2
> > * route-target import 100:55*
> >
> > R5#
> > ip vrf VPN_A
> > rd 100:1
> > export map VPN-A-EXPORT
> > route-target export 100:1
> > route-target import 100:1
> > route-target import 100:55
> > ip vrf VPN_B
> > rd 100:2
> > route-target export 100:2
> > route-target import 100:2
> >
> >
> > R5#sh route-map VPN-A-EXPORT
> > route-map VPN-A-EXPORT, permit, sequence 10
> > Match clauses:
> > ip address prefix-lists: LO101
> > Set clauses:
> > extended community RT:100:55
> > Policy routing matches: 0 packets, 0 bytes
> > route-map VPN-A-EXPORT, permit, sequence 100
> > Match clauses:
> > Set clauses:
> > extended community RT:100:1
> > Policy routing matches: 0 packets, 0 bytes
> >
> > Thank you.
> >
> > TK
> >
> >
> > On Sat, Jan 29, 2011 at 11:45 AM, Carlos G Mendioroz <tron_at_huapi.ba.ar
> >wrote:
> >
> >> Sounds like a problem with the import RT for vrf VPN_A ?
> >> The route is there with RT 100:55. What are you importing ?
> >> -Carlos
> >>
> >> Tom Kacprzynski @ 29/01/2011 14:23 -0300 dixit:
> >>
> >>> Hello experts,
> >>> Doing a lab wiht MP-BGP and can't seem to figure out how is it possible
> to
> >>> get this output. When I do *show ip bgp vpnv4 vrf VPN_A *I don't see
> >>> 172.16.5.0/24 route, but when i do *show ip bgp vpnv4 all *I see that
> >>> same
> >>> route. Shouldn't both of them show the same information. I this lab
> (INE
> >>> 14.5) I'm asked to rewrite that prefix's route target and export it
> from
> >>> one VRF table to the VPN_A table.
> >>>
> >>> Rack1R6#*show ip bgp vpnv4 vrf VPN_A*
> >>> BGP table version is 41, local router ID is 150.1.6.6
> >>> 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 VPN_A*)
> >>> <----- no 172.16.5.0/24 route (see below)
> >>> *>i155.1.58.0/24 150.1.5.5 0 100 0 ?
> >>> *> 155.1.67.0/24 0.0.0.0 0 32768 ?
> >>> *> 172.16.7.0/24 155.1.67.7 0 32768 ?
> >>>
> >>>
> >>> Rack1R6#*show ip bgp vpnv4 all*
> >>> BGP table version is 41, local router ID is 150.1.6.6
> >>> 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 VPN_A*)
> >>> *>i155.1.58.0/24 150.1.5.5 0 100 0 ?
> >>> *> 155.1.67.0/24 0.0.0.0 0 32768 ?
> >>> **>i172.16.5.0/24 150.1.5.5 0 100 0 ?
> >>> <*---- 172.16.5.0/24
> >>> *> 172.16.7.0/24 155.1.67.7 0 32768 ?
> >>> Route Distinguisher: 100:2 (default for vrf VPN_B)
> >>> *>i155.1.5.0/24 150.1.5.5 0 100 0 ?
> >>> *> 155.1.76.0/24 0.0.0.0 0 32768 ?
> >>> **>i172.16.5.0/24 150.1.5.5 0 100 0 ?**
> >>> <*---- 172.16.5.0/24
> >>> *> 192.168.6.0 0.0.0.0 0 32768 ?
> >>> *> 192.168.7.0 155.1.76.7 0 32768 ?
> >>>
> >>>
> >>>
> >>>
> >>> Rack1R6#*show ip bgp vpnv4 all 172.16.5.0*
> >>> BGP routing table entry for 100:1:172.16.5.0/24, version 31
> >>> Paths: (1 available, best #1, *no table*)
> >>> Not advertised to any peer
> >>> Local
> >>> 150.1.5.5 (metric 66) from 150.1.4.4 (150.1.4.4)
> >>> Origin incomplete, metric 0, localpref 100, valid, internal, best
> >>> Extended Community: RT:100:55
> >>> Originator: 150.1.5.5, Cluster list: 150.1.4.4
> >>> mpls labels in/out nolabel/25
> >>> BGP routing table entry for 100:2:172.16.5.0/24, version 34
> >>> Paths: (1 available, best #1, table *VPN_B*)
> >>> Not advertised to any peer
> >>> Local, imported path from 100:1:172.16.5.0/24
> >>> 150.1.5.5 (metric 66) from 150.1.4.4 (150.1.4.4)
> >>> Origin incomplete, metric 0, localpref 100, valid, internal, best
> >>> Extended Community: RT:100:55
> >>> Originator: 150.1.5.5, Cluster list: 150.1.4.4
> >>> mpls labels in/out nolabel/25
> >>>
> >>>
> >>> Thank you for any help.. i'm really stuck on this and can't figure it
> out.
> >>> I
> >>> fee like i'm missing some piece of information.
> >>>
> >>>
> >>> Blogs and organic groups at http://www.ccie.net
> >>>
> >>> _______________________________________________________________________
> >>> Subscription information may be found at:
> >>> http://www.groupstudy.com/list/CCIELab.html
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >> --
> >> 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 Sun Jan 30 2011 - 10:05:44 ART