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.

Chapter 4: Routing <strong>Policy</strong> <strong>Configuration</strong><br />

Table 10: Routing <strong>Policy</strong> Match Conditions (continued)<br />

Match Condition<br />

Match<br />

Condition<br />

Category<br />

from Statement Description<br />

to Statement Description<br />

route-type value<br />

Standard<br />

Type of route. The value can be one of the following:<br />

• external—External route.<br />

• internal—Internal route.<br />

source-address-filter<br />

destination-prefix<br />

match-type<br />

<br />

Extended<br />

List of multicast source addresses. When<br />

specifying a source address, you can<br />

specify an exact match with a specific<br />

route or a less precise match using match<br />

types. You can configure either a common<br />

action that applies to the entire list or an<br />

action associated with each prefix. For<br />

more information, see “Configuring Route<br />

Lists for Use in Routing <strong>Policy</strong> Match<br />

Conditions” on page 119.<br />

You cannot specify this match condition.<br />

state (active |<br />

inactive)<br />

Standard<br />

(BGP export only) Match on the following types of advertised routes:<br />

• active—An active BGP route<br />

• inactive—A route advertised to internal BGP peers as the best external path even<br />

if the best path is an internal route<br />

• inactive—A route advertised by BGP as the best route even if the routing table did<br />

not select it to be an active route<br />

tag string tag2 string<br />

Standard<br />

Tag value. You can specify two tag strings: tag (for the first string) and tag2. These<br />

values are local to the router and can be set on configured routes or by using an import<br />

routing policy.<br />

You can specify multiple tags under one match condition by including the tags within<br />

a bracketed list. For example: from tag [ tag1 tag2 tag3 ];<br />

For OSPF and IS-IS, the tag match conditions match the 32-bit tag field in external<br />

link-state advertisement (LSA) packets.<br />

Configuring Actions in Routing <strong>Policy</strong> Terms<br />

Each term in a routing policy can include a then statement, which defines the actions to<br />

take if a route matches all the conditions in the from and to statements in the term:<br />

then {<br />

actions;<br />

}<br />

You can include this statement at the following hierarchy levels:<br />

• [edit policy-options policy-statement policy-name term term-name]<br />

• [edit logical-systems logical-system-name policy-options policy-statement policy-name<br />

term term-name]<br />

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

47

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

Saved successfully!

Ooh no, something went wrong!