[j-nsp] auto-export vs rib-groups

[Gary Tate]

I may be reading this wrong but...

Both rib-groups and auto-export allow the importing of directly  
connected routes.  This is done in rib-groups using interface-routes  
configuration which shares directly between routing instances.  Without  
these routes forwarding would obviously break.

Gary

On Thursday, Nov 6, 2003, at 11:56 US/Pacific, Chris Hellberg wrote:

> But you can put a from protocol xyz in your import or export policy to  
> choose the protocol types you want to appear in your VRF in  
> combination with the auto-export statement.
>
> One of the reasons why I chose to say rib-groups (which I neglected to  
> mention) were less flexible is the fact you can't import  
> directly-connected routes between VRFs - you have to do some  
> static-route hackery.
>
> -----Original Message-----
> From:	Joe Soricelli [mailto:jms at juniper.net]
> Sent:	Fri 11/7/2003 4:25 AM
> To:	Chris Hellberg; MPLS Newbie; juniper-nsp at puck.nether.net
> Cc:	
> Subject:	RE: [j-nsp] auto-export vs rib-groups
> Agree with all but the 'flexible' part. Auto-export is way easier but  
> it
> moves ALL of the routes between the VRFs. Rib-groups require a lot of
> thought and configuration, but you have the option of applying routing
> policies to the groups which allows you fine-grained control over which
> routes are shared and which are not. So, I would argue that rib-groups
> are more flexible in the long run.
>
> -joe
>
>> -----Original Message-----
>> From: juniper-nsp-bounces at puck.nether.net
>> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
>> Chris Hellberg
>> Sent: Thursday, November 06, 2003 3:08 AM
>> To: MPLS Newbie; juniper-nsp at puck.nether.net
>> Subject: RE: [j-nsp] auto-export vs rib-groups
>>
>>
>> R.N.,
>>
>> Using auto-export is a lot more flexible than rib-groups both
>> from a theoretical and experience point-of-view; rib-groups
>> bring pain.
>>
>> It's also easier to explain to others how the coupling
>> between auto-export and policies work rather than try and
>> explain how rib-groups import and export routes between VRFs
>> (the configuration also changes depending on the protocol the
>> route has been learned from).
>>
>> Chris
>>
>> Just an addendum, if you've got any IPVPN policies that once
>> used a match on protocol bgp as well as a community, you'll
>> need to remove that for routes you wish to import that are
>> imported from the same node.
>>
>>
>> -----Original Message-----
>> From:	MPLS Newbie [mailto:routernewbie at hotmail.com]
>> Sent:	Thu 11/6/2003 6:56 PM
>> To:	juniper-nsp at puck.nether.net
>> Cc:	
>> Subject:	[j-nsp] auto-export vs rib-groups
>> Dear List,
>>
>>    Can someone comment based on operational experience or
>> router-geeking
>> experience regarding to using the knob of auto-export to
>> exchange routes
>> among vrf's vs using rib-groups to achieve the same?
>>
>> any pro's or con's?
>>
>> Much appreciated.
>>
>> Router Newbie
>>
>> _________________________________________________________________
>> MSN Shopping upgraded for the holidays!  Snappier product search...
>> http://shopping.msn.com
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>>
>>
>>
>>
>>
>>
>>
>> --------------------------------------------------------------
>> ----------------
>> "This communication, including any attachments, is confidential.
>> If you are not the intended recipient, you should not read
>> it - please contact me immediately, destroy it, and do not
>> copy or use any part of this communication or disclose
>> anything about it. Thank you."
>> --------------------------------------------------------------
>> ----------------
>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>>
>
>
>
>
>
> ----------------------------------------------------------------------- 
> -------
> "This communication, including any attachments, is confidential.
> If you are not the intended recipient, you should not read
> it - please contact me immediately, destroy it, and do not
> copy or use any part of this communication or disclose
> anything about it. Thank you."
> ----------------------------------------------------------------------- 
> -------
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>