Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
Configuring Match Conditions in Routing Policy Terms
Each term in a routing policy can include two statements, from and to, to define the
conditions that a route must match for the policy to apply:
from {
family family-name;
match-conditions;
policy subroutine-policy-name;
prefix-list name;
route-filter destination-prefix match-type ;
source-address-filter source-prefix match-type ;
}
to {
match-conditions;
policy subroutine-policy-name;
}
You can include these statements at the following hierarchy levels:
• [edit policy-options policy-statement policy-name term term-name]
• [edit logical-systems logical-system-name policy-options policy-statement policy-name
term term-name]
In the from statement, you define the criteria that an incoming route must match. You
can specify one or more match conditions. If you specify more than one, they all must
match the route for a match to occur.
The from statement is optional. If you omit the from and the to statements, all routes
are considered to match.
NOTE: In export policies, omitting the from statement from a routing policy
term might lead to unexpected results. For more information, see “Applying
Routing Policies and Policy Chains to Routing Protocols” on page 57.
In the to statement, you define the criteria that an outgoing route must match. You can
specify one or more match conditions. If you specify more than one, they all must match
the route for a match to occur. You can specify most of the same match conditions in
the to statement that you can in the from statement. In most cases, specifying a match
condition in the to statement produces the same result as specifying the same match
condition in the from statement.
The to statement is optional. If you omit both the to and the from statements, all routes
are considered to match.
Copyright © 2010, Juniper Networks, Inc.
41