J-series™ Services Router User Guide
Table 146: Creating a Policy to Reject Known Invalid Routes
Task
Navigate to the Term level in the
configuration hierarchy.
Specify the routes to accept.
Accept these routes.
Specify the routes to reject.
Reject these routes.
Injecting OSPF Routes into the BGP Routing Table
You can specify a match condition for policies based on procotols by naming a
protocol from which the route is learned or to which the route is being advertised.
You can specify one of the following protocols: aggregate, BGP, direct, DVMRP,
IS-IS, local, OSPF, PIM-dense, PIM-sparse, RIP, or static
For example, you can inject or redistribute OSPF routes into the BGP
routing table by creating a routing policy.
380
Configuring a Routing Policy with a Configuration Editor
J-Web Configuration Editor
In the J-Web configuration editor
hierarchy, select Policy options>Policy
statement>Term.
1.
In the From option, click Configure.
2.
In the Route filter box, click Add
new entry.
3.
In the Address box, enter the prefix
of the routes.
4.
Click OK.
1.
In the Then option, click Configure.
2.
In the Accept option, select the Yes
check box.
3.
Click OK.
1.
In the configuration
editor hierarchy, select
Policy options>Policy
statement>Term.
2.
In the From option, click Configure.
3.
In the Route filter box, click Add
new entry.
4.
In the Value box, enter the prefix of
the routes to reject.
5.
Click OK.
1.
In the Then option, click Configure.
2.
In the Reject option, select the Yes
check box.
3.
Click OK.
CLI Configuration Editor
From the top of the CLI configuration
hierarchy, enter
edit policy-options policy-statement
rejectpolicy1 term rejectterm1
Accept routes less than 8 bits in length:
set from route-filter 0/0 up to /7 accept
1.
Specify routes less than 8 bits in
length:
set from route-filter /8 orlonger
2.
Reject these routes:
set then reject