>
> Yeah, I've got it working for direct using the same mechanism.
> That's not the issue... I'm trying to leak BGP routes from inet.0.
Just got it.
before:
inet.0: 18128 destinations, 18128 routes (18128 active, 0 holddown, 0
hidden)
BGP: 18109 routes, 18109 active
TEST2.
> Unfortunately the only way I have been able to make this work is
> with rib groupshere is what I did to put all the direct
> interfaces into my VRF.
>
> }
> routing-options {
> interface-routes {
> rib-group inet interface-routes;
> }
> rib-groups {
> interfac
Well, that was quick. Nope, not supported:
[edit routing-instances TEST routing-options]
'instance-import'
instance-import not allowed on VPN instance
error: configuration check-out failed
Ah well, worth a shot. Back to playing with rib-groups :)
-dd
> In all honesty, I have only don
{
import-rib [ inet.0 vrf.inet.0 ];
}
}
Andy
-Original Message-
From: [EMAIL PROTECTED] on behalf of Dave Diller
Sent: Tue 4/17/2007 7:37 AM
To: Nick Slabakov
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] leaking into a VRF from inet.0?
Well, that was quick. Nope
Hi Dave,
Just configure another rib-group on the opposite direction (with
keeping in mind that you need 'direct' routes for next-hop
availability) and you should be fine.
For example:
routing-options {
rib-groups {
Vrf_X-to-inet-default {
import-rib [ Vrf_X.inet.0 inet.0 ]
In the lab, I've found that I can get specific BGP routes into inet.
0 from a VRF using rib-groups and auto-export to create a granular
"leak policy". Works great.
Is it possible to do the converse - leak selected BGP routes from
inet.0 into a VRF? I've had no luck so far.
-dd
_
6 matches
Mail list logo