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

[Chris Hellberg]

Pedro,

I should have mentioned this was done on JunOS 5.3 which would not import direct routes at the time.

Another thing I should mention that even on 5.6 which imports direct routes without a problem (just tested it), with any software revision, if you've got a common management-type VPN which you want to import a number of different VRF routes to, the rib-group for the configuration for that central VRF is awful - one big ugly rib-group line.

Regards,

Chris

> -----Original Message-----
> From: Pedro Roque Marques [mailto:roque at juniper.net]
> Sent: Friday, 7 November 2003 10:56
> To: Chris Hellberg
> Cc: Joe Soricelli; MPLS Newbie; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] auto-export vs rib-groups
> 
> 
> Chris.Hellberg at telecom.co.nz (Chris Hellberg) writes:
> 
> > 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.
> > 
> 
> perhaps i'm not understanding what you mean but you can apply a
> rib-group to direct routes...
> 
> routing-options {
>     interface-routes {
> 	rib-group inet <name>;
>     }
> }
> 
> This can be the same rib-group that you use w/ other protocols to leak
> routes between instances...
> 
> Still for the overlapping VPN scenario i believe auto-export gives you
> the same functionality w/ much less configuration.
> 
> The difference between the two is that rib-groups are applied to
> routes received by a protocol before that route is added to the
> routing-table and thus before path selection.
> 
> auto-export is applied after path selection and only "exports" the
> active path.
> 
>   Pedro.
> 
> 

------------------------------------------------------------------------------
"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."
------------------------------------------------------------------------------