Re: MPLS VPN Route Target Rewrite

Hey Tom,

Can you paste the following:-

1. "sh ip route vrf VPN_A"
2. "sh run | b ip vrf VPN_A"

Tharak Abraham Luke

On Sat, Jan 29, 2011 at 10:53 PM, Tom Kacprzynski <tom.kac_at_gmail.com> wrote:

> 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

Blogs and organic groups at http://www.ccie.net
Received on Sun Jan 30 2011 - 11:52:56 ART