Table of Contents
Advertisement
}
At this point, the service PIC daemon (spd) installs routes for 30.30.30.1 and 3040::0/16, pointing to the service PIC
(sp-3/0/0 in this example). However, these routes are not advertised by default. You need to configure the routing
policy to export these routes and apply the policy to the appropriate routing protocol. An example routing policy with
OSPf is shown in the following.
[edit policy-options]
user@router# show
policy-statement ospf-exp {
}
Note that a more conservative routing policy can be configured with exact prefixes (in the from clause) that the user
wants to export. In this case, all statically configured routes are exported, and since all services PIC daemon installed
routes are static routes, this exports 6rd routes as well. Once the routing policy is in place, apply that to OSPf as in
the following:
[edit protocols]
user@router#show
ospf {
}
ospf3 {
}
The OSPf hierarchy is needed to export v4 routes (in this case, 30.30.30.1), and the ospf3 hierarchy is needed to export
v6 routes (in this case, 3040::/16).
Copyright © 2011, Juniper Networks, Inc.
v6rd-prefix 3040::0/16;
mtu-v4 9192;
}
}
rule v6rd-dom1-r1 {
match-direction input;
term t1 {
then {
v6rd rd1;
}
}
}
term a {
from protocol static;
then accept;
}
export ospf-exp;
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
export ospf-exp;
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
IMPLEMENTATION GUIDE - 6rd Configuration Guide
9
Advertisement
Table of Contents
