Hi Oli, Thanks for your input, but i think the solution for using the extcommunity list still won't work. The poin is using import map the router only match the clause regular expression, but to import the route, we still need to put command "route-target import xxx" within vrf is it correct? So whenever i put only one route-target import , i.e: "route-target import 1:222" the PE#2 will directly importing the route for VRF ABC from PE#1 which is we don't want it, the purpose is PE#2 will import route for VRF ABC from PE#1 if and only if we put 2 (two) route-target import within "ip vrf ABC".
you can see that within config#1 that with only importing 1 (one) route-target import PE#2 should import route vrf ABC from PE#1, but is there anyway that we could put strict rule that PE#2 will only import vrf ABC if there is 2 (two) route-target import within vrf configuration. please look at "config#2" I know this is uncommon configuration, but this kind of configuration is working with non Cisco device. and now we are implementing Cisco new device to cooperate with existing PE. I have tried to used other method within route-map using "continue <seq>, which is uncommon to used, but it also didn't work, please look for "Config#3". !#Config#1 ! ! PE#2 ip vrf ABC rd 1:111 import map imp_abc export map exp_abc route-target import 1:222 ! ip extcommunity-list 101 permit RT:1:222_RT:1:333_ ! route-map imp_abc permit 10 match extcommunity 101 ! !#Config#2 ! ! PE#2 ip vrf ABC rd 1:111 import map imp_abc export map exp_abc route-target import 1:222 route-target import 1:333 ! ip extcommunity-list 101 permit RT:1:222_RT:1:333_ ! route-map imp_abc permit 10 match extcommunity 101 ! ! ! !#Config#3 ! ! PE#2 ip vrf ABC rd 1:111 import map imp_abc export map exp_abc route-target import 1:222 route-target import 1:333 ! ip extcommunity-list 10 permit rt 1:222 ip extcommunity-list 11 permit rt 1:333 ! route-map imp_abc permit 10 match extcommunity 101 ! route-map imp_abc permit 10 match extcommunity 10 continue 20 ! route-map imp_abc permit 20 match extcommunity 11 ! thanks, Rano --- On Sat, 26/12/09, Oliver Boehmer (oboehmer) <[email protected]> wrote: From: Oliver Boehmer (oboehmer) <[email protected]> Subject: RE: [c-nsp] Multiple Route-Target import within VRF To: "Rano Karno" <[email protected]>, [email protected] Date: Saturday, 26 December, 2009, 7:44 PM > > I have a question regarding how to match more than 1 (one) route-target > within importing VRF, short brief as below: > i have two PE , let say PE#1 and PE#2 > PE#1 : > VRF ABC > rd 1:111 > route-target export 1:222 > route-target export 1:333 > route-target import 1:111 > > PE#2 : > VRF ABC > rd 1:111 > route-target export 1:111 > route-target import ??? > > is there anyway to configure whenever PE#2 wanna import route from PE#1 VRF > ABC , then PE#2 should match RT:1:222 AND RT:1:333. > when i configure PE#2 with route-target import 1:222 OR 1:333 (just one of > route-target) the PE#2 vrf ABC could read the route from PE#1 vrf ABC. > i've tried doing with "import map" which is not solving the solution. > > considering it is extended community, I have read that to match 2 or more > community can be done with "standar community" where we could put command > "exact" in the end of configuration. you could use ip extcommunity-list 101 permit RT:1:222_RT:1:333_ within an import map (possibly also with a 2nd entry "ip extcommunity-list 101 permit RT:1:333_RT:1:222_", not sure about the order and requirement to match possible permutations). However I would consider defining another RT for this purpose, i.e. add "route-target export 1:444" on all the VRFs you have export 1:222 and 1:333 and import this new one.. Not sure what you're trying to achieve oli New Email addresses available on Yahoo! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! http://mail.promotions.yahoo.com/newdomains/aa/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
