Re: MPLS Route Targets

Hi Brad,

This was asked about in the last couple of days and while there isn't a
direct method to do it, it is possible to do via tcl scripts or using a
debug command and refreshing your neighbors routes.

You should be able to search through the archives from the last couple of
days - or you can read my blog post about the way to do it via tcl
http://noshut.blogspot.com/2010/08/learning-about-tclsh.html

Cheers,
Adam

On Fri, Aug 20, 2010 at 10:53 AM, Brad Edgeworth <edgie512_at_gmail.com> wrote:

> So I recently learned that 'route distinguishers' are slightly different
> from route-tags. When I troubleshoot MPLS route issues, I'd like to get
> on
> a P router and do a 'show ip bgp vpn4 all' to find all the routes for a
> particular VPN Customer.. THe problem is that this may not work right if
> you have an export map. Is there another command to will show all the
> route-targets with each route?
>
> Example Usage:
>
> R1 (CE) -- R2(PE) -- R3 (P) -- R4 (PE --Not relevant from here on out.)
>
> R2 Config:
>
> Ip vrf VPN_B
> rd 100:2
> route-target import 100:2
> route-target export 100:2
> export-map CHANGE_ROUTE_TARGET
>
> route-map CHANGE_ROUTE_TARGET permit 10
> match ip address prefix PRE_CHANGE_RT
> set extcommunity rt 100:200
>
> route-map CHANGE_ROUTE_TARGET permit 20
>
> ip prefix-list PRE_CHANGE_RT permit 175.1.5.0/24
>
> router bgp 100
> no bgp default ipv4-unicast
> neighbor 150.1.3,3 remote-as 100
> neighbor 150.1.3.3 update-source Loopback0
> !
> address-family vpnv4
> neighbor 150.1.3.3 activate
> neighbor 150.1.3.3 send-community extended
>
> address-family ipv4 vrf VPN_A
> redistribute connected
> redistribute ospf 10 vrf VPN_A
> no synchronization
>
>
> Ideally I'd like to find the command (if it exists) that will dump out all
> the route-targets riding inside the MPLS VPN similar to combining these two
> statements:
>
> Rack1R3# show ip bgp vpn4 all
> Network Next Hop Metric LocPrf Weight Path
> Route Distinguisher: *100:5* (default for vrf VPN_A)
> *>i175.1.1.0/24 150.1.2.2 0 100 0 ?
> *>i175.1.2.0/24 150.1.2.2 0 100 0 ?
> *>i175.1.3.0/24 150.1.2.2 1 100 0 ?
> *>i175.1.4.0/24 150.1.2.2 0 100 0 ?
> **>i175.1.5.0/32 150.1.2.2 2 100 0 ?*
>
> Rack1R3#show ip bgp vpn all 175.1.5.0
> BGP routing table entry for 100:5:175.1.5.0/24, version 39
> 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.3.3)
> Origin incomplete, metric 0, localpref 100, weight 32768, valid,
> sourced, best
> Extended Community: RT:100:200 OSPF DOMAIN ID:0x0005:0x000000050200
> OSPF RT:0.0.0.1:2:0 OSPF ROUTER ID:150.1.3.3:0
> mpls labels in/out 21/aggregate(VPN_A)
>
>
> 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 Fri Aug 20 2010 - 11:04:29 ART