[j-nsp] 答复: Merging routes from VRF to inet.0
Jack.Xu
xujianlx at gmail.com
Sun Mar 22 22:05:02 EDT 2015
Hi Tom:
This is my example. Seem meet your require.
routing-options {
interface-routes {
rib-group inet CT;
}
static {
route 0.0.0.0/0 next-hop 58.215.51.1;
}
rib-groups {
CNC {
import-rib [ inet.0 cnc.inet.0 ];
import-policy test;
}
CT {
import-rib [ inet.0 cnc.inet.0 ];
import-policy test;
}
}
}
policy-options {
policy-statement test {
term 1 {
from {
route-filter 192.168.2.0/24 orlonger;
route-filter 192.168.3.0/24 orlonger;
}
then accept;
}
term default {
then reject;
}
}
}
-----邮件原件-----
发件人: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] 代表 Tom
Eichhorn
发送时间: 2015年1月14日 17:32
收件人: jnsp
主题: [j-nsp] Merging routes from VRF to inet.0
Hi Guys,
I am currently facing a problem,
to which I do not have currently a clean solution:
I have routes in some L3 VPN vrf, and I need to merge some of them to
inet.0, but I have no real clue how to do that.
RIB-groups would only merge all, and tbh, I never understood rib-groups and
the documentation is a little bit unclear how they work.
My current solution is having a lt-interface between the inet.0 and
vrf.inet.0 and speaking BGP,
but that limits the traffic volume to one PFE (yes, I could have
lt-interfaces on each PFE and do ECMP, but that would be that dirty...)
I tried also instance-import under routing-options, but that doesn't work
for some reason, instance-export in the vrf is not supported - this only
works for virtual routers, but not VRFs...
I also tried some bad hacks on the bgp configuration, e.g. deleting the
vrf-community before importing etc, but all of that also did not work :(
Any hint or idea?
Thanks,
Tom
PS: For the other way round, getting the default route to the VRF, I simply
use a next-table inet.0 route in the vrf.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list