16.03.2014 Views

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Junos 10.4 <strong>Policy</strong> <strong>Framework</strong> <strong>Configuration</strong> <strong>Guide</strong><br />

If a term does not have from and to statements, all routes are considered to match, and<br />

the actions apply to them all. For information about the from and to statements, see<br />

“Configuring Match Conditions in Routing <strong>Policy</strong> Terms” on page 41.<br />

You can specify one or more actions in the then statement. There are three types of<br />

actions:<br />

• Flow control actions, which affect whether to accept or reject the route and whether<br />

to evaluate the next term or routing policy.<br />

• Actions that manipulate route characteristics.<br />

• Trace action, which logs route matches.<br />

NOTE: When you specify an action that manipulates the route<br />

characteristics, the changes occur in a copy of the source route. The source<br />

route itself does not change. The effect of the action is visible only after<br />

the route is imported into or exported from the routing table. To view the<br />

source route before the routing policy has been applied, use the show route<br />

receive-protocol command. To view a route after an export policy has been<br />

applied, use the show route advertised-protocol command.<br />

During policy evaluation, the characteristics in the copy of the source route<br />

always change immediately after the action is evaluated. However, the<br />

route is not copied to the routing table or a routing protocol until the<br />

completion of the policy evaluation is complete.<br />

The then statement is optional. If you omit it, one of the following occurs:<br />

• The next term in the routing policy, if one is present, is evaluated.<br />

• If there are no more terms in the routing policy, the next routing policy, if one is present,<br />

is evaluated.<br />

• If there are no more terms or routing policies, the accept or reject action specified by<br />

the default policy is taken. For more information, see “Default Routing Policies and<br />

Actions” on page 20.<br />

The following sections discuss the following actions:<br />

• Configuring Flow Control Actions on page 49<br />

• Configuring Actions That Manipulate Route Characteristics on page 49<br />

• Configuring the Default Action in Routing Policies on page 54<br />

• Configuring a Final Action in Routing Policies on page 56<br />

• Logging Matches to a Routing <strong>Policy</strong> Term on page 56<br />

• Configuring Separate Actions for Routes in Route Lists on page 57<br />

48<br />

Copyright © 2010, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!