Hi Dave
I find using the "instance-import" (or export) command much easier than
messing about with ribs
for instance .. very simple example.
routing-options {
instance-import test;
}
# show interfaces ge-1/0/0
unit 0 {
family inet {
address 1.1.1.1/30;
}
}
# show routing-instances
l3vpn {
instance-type virtual-router;
interface ge-1/0/0.0;
routing-options {
static {
route 2.2.2.2/32 next-hop 1.1.1.2;
}
}
}
# show policy-options policy-statement test
term reject {
from {
instance l3vpn;
route-filter 1.1.1.0/30 orlonger;
}
then reject;
}
term accept {
from {
instance l3vpn;
route-filter 2.2.2.2/32 exact;
}
then accept;
}
#show route
inet.0: 10 destinations, 11 routes (9 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
2.2.2.2/32 *[Static/5] 00:06:36
> to 1.1.1.2 via ge-1/0/0.0
l3vpn.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.0/30 *[Direct/0] 00:06:36
> via ge-1/0/0.0
1.1.1.1/32 *[Local/0] 00:06:36
Local via ge-1/0/0.0
2.2.2.2/32 *[Static/5] 00:06:36
> to 1.1.1.2 via ge-1/0/0.0
snort bsd wrote:
Hi all:
Could those routes in the L3VPN table be copied to inet.0? I tried to use
policy and it doesn't seem to be working:
term l3vpn->inet.0 {
from {
rib l3vpn.inet.0;
route-filter 100.100.0.0/16 orlonger;
}
to rib inet.0;
then {
accept;
}
}
_dave
Stay connected to the people that matter most with a smarter inbox. Take
a look http://au.docs.yahoo.com/mail/smarterinbox
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
