MPLS VPN Query

Unanswered Question
Nov 14th, 2008
User Badges:

Please find my configuration attached.I got confused with the command "route-target export 65555:500" under "ip vrf Customer2". What does this command do?

Whats the effect of the same export command given under "ip vrf Customer1"??


How can we export route-target export 65555:500 from ip vrf Customer2 with rd 65555:103?



Attachment: 
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (2 ratings)
Loading.
csco10716389 Fri, 11/14/2008 - 04:08
User Badges:

Route Target Export command help you to Inject the customer routes to the other end VPN customer,means PE-PE.


IP vrf customer2

rd 65555:103

route-target export 65555:500



aneesh.ts Fri, 11/14/2008 - 07:04
User Badges:

The same export command is given under rd:65555:500 also. So whats the difference in giving it under 65555:103?


Harold Ritter Fri, 11/14/2008 - 11:05
User Badges:
  • Cisco Employee,

Aneesh,


There is a major difference between the route distinguisher (RD) and the route target extended community.


The RD only purpose is to ensure that the VPNv4 routes injected in the SP core will be unique. The uniqueness is achieved by prepending the ipv4 prefixes received from the PE with the RD value.


The purpose of the route-target extended community is to control in which VRFs the exported prefixes are allowed to be imported.


Regards

aneesh.ts Tue, 11/18/2008 - 21:37
User Badges:

Thanks HAROLD. Your comment was really helpful. I have just one more doubt. In the below configuration vrf CUSTOMER1 is exporting its routes with route-target 61515:100. Also vrf MANAGEMENT is exporting and importing 61515:100.


So vrf MANAGEMENT will import two sets of routes with route-target 61515:100, one its same and one from vrf CUSTOMER1. Can you just explain how this whole configuration works.

How will this import-map come into picture? How will import-map only apply to routes from vrf CUSTOMER1?



**********************************************

ip vrf MANAGEMENT

rd 61515:100

import map INBOUND-TRAFFIC

export map OUTBOUND-TRAFFIC

route-target export 61515:100

route-target import 61515:100



ip vrf CUSTOMER1

rd 61515:103

route-target export 61515:103

route-target export 61515:100

route-target import 61515:103

route-target import 61515:10



route-map OUTBOUND-TRAFFIC permit 10

match ip address 20

set extcommunity rt 61515:10


route-map INBOUND-TRAFFIC permit 10

match ip address prefix-list MGMT-IPS



access-list 20 permit 10.211.2.0 0.0.0.255 log

access-list 20 permit 10.211.255.0 0.0.0.3 log



ip prefix-list MGMT-IPS seq 10 permit 10.168.1.0/24

ip prefix-list MGMT-IPS seq 20 permit 10.168.126.0/24


**********************************************


Harold Ritter Wed, 11/19/2008 - 14:03
User Badges:
  • Cisco Employee,

Aneesh,


1. Prefixes from CUSTOMER1 VRF first need to match the "route-target import 61515:100".


2. Prefixes that went through step 1 successfully are then subjected to the import-map.


3. If both step 1 and 2 are successful, the prefixes are imported in the MANAGEMENT VRF.


Regards

devang_etcom Mon, 11/17/2008 - 00:14
User Badges:
  • Gold, 750 points or more

Hi,


route-target export under the vrf configuration will allow you to advertise the route which are taged with route-target value configured in route-target export command, in your case it is "65555:500" so here you are advertising routes with the RT of 65555:500 to your neighbor.


regards

Devang Patel

Actions

This Discussion