Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
Defining Routing Policies
• Example: Grouping Destination Prefixes on page 79
• Example: Grouping Source Prefixes on page 80
• Example: Grouping Source and Destination Prefixes in a Forwarding Class on page 81
• Example: Accepting Routes with Specific Destination Prefixes on page 82
• Example: Accepting Routes from BGP with a Specific Destination Prefix on page 82
• Example: Using Routing Policy in an ISP Network on page 83
To define a routing policy, include the policy-statement statement:
policy-statement policy-name {
term term-name {
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;
}
then actions;
}
}
You can include this statement at the following hierarchy levels:
• [edit policy-options]
• [edit logical-systems logical-system-name policy-options]
policy-name specifies the policy name and must be unique in the configuration. It can
contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To
include spaces in the name, enclose the entire name in quotation marks (“ ”).
term-name specifies the name of a term in the policy and must be unique in that policy.
It can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. To
include spaces in the name, enclose the entire name in quotation marks (“ ”).
A policy statement can include multiple terms, including a unnamed term which must
be the final term in the policy. To configure an unnamed term, omit the term statement
when defining match conditions and actions. However, we recommend that you name
all terms.
For information about configuring the components of a term, see the following sections:
• Configuring Match Conditions in Routing Policy Terms on page 41
• Configuring Actions in Routing Policy Terms on page 47
40
Copyright © 2010, Juniper Networks, Inc.