I can't answer which way is better, but here is another example of how to do it:
http://www.youtube.com/watch?feature=player_embedded&v=qa6sAyoLpyY Short version of what is described in the video - this way keeps you only need to update your "other" vrfs rather than the common one. Seems quite neat to me. Red VRF: RD 65000:1 RT E/I 65000:1 RT E 65000:101 RT I 65000:102 Red VRF: RD 65000:2 RT E/I 65000:2 RT E 65000:101 RT I 65000:102 Common VRF: RD 65000:101 RT E 65000:102 RT I 65000:101 Andrew On Wed, Mar 20, 2013 at 6:44 AM, Karl Putland <k...@simplesignal.com> wrote: > Here's the scenario. > > I have customer services coming into VRFs > Those customer vrfs import the necessary routes from vrf SERVICES. > The interface in vrf MAIN has an OSPF session back to my core. > Is it better to route-target import like I have it now, or for each > customer vrf to do a route-target export to a common target? > Or... is there a better way to redistribute the routes to customer networks > for my services to access? > > ip vrf 2030 > rd 65000:2001 > route-target export 65000:2001 > route-target import 65000:2030 > route-target import 60522:100 > !... > ip vrf 2030 > rd 65000:2030 > route-target export 65000:2030 > route-target import 65000:2030 > route-target import 60522:100 > > > ip vrf SERVICES > rd 60522:100 > route-target export 60522:100 > route-target import 60522:100 > > > ip vrf MAIN > rd 65000:100 > route-target export 65000:100 > route-target import 65000:100 > route-target import 65000:2010 > route-target import 65000:2001 > route-target import 65000:2002 > route-target import 65000:2003 > route-target import 65000:2004 > route-target import 65000:2005 > !... > route-target import 65000:2027 > route-target import 65000:2028 > route-target import 65000:2029 > route-target import 65000:2030 > > > > --Karl > > Karl Putland > Senior VoIP Engineer > > *SimpleSignal* > 3600 S Yosemite, Suite 150 > Denver, CO 80237 > One Number Rings All My Phones: 303-242-8608 > > SimpleSignal.com <http://www.simplesignal.com/> | > Blog<http://www.simplesignal.com/blog> > | Facebook <http://www.facebook.com/SimpleSignal?ref=ts> | > Twitter<http://twitter.com/simplesignal> > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/