Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
Example: Configuring a Subroutine
Create the subroutine is-customer and call it from the routing policies export-customer
and import-customer. In import-customer, the action is taken only on routes that match
the route filters defined in is-customer.
[edit]
policy-options {
policy-statement is-customer {
term match-customer {
from {
route-filter 10.100.1.0/24 exact;
route-filter 10.186.100.0/24 exact;
}
then accept;
}
term drop-others {
then reject;
}
}
policy-statement export-customer {
from policy is-customer;
then accept;
}
policy-statement import-customer {
from {
protocol bgp;
policy is-customer;
}
then {
local-preference 10;
accept;
}
}
}
Configuring Routing Policy Match Conditions Based on Routing Table Entries
In addition to defining match conditions in the from statement of a policy, you can use
the condition statement to define conditions used during policy evaluation:
condition condition-name {
if-route-exists address table table-name;
}
You can include this statement at the following hierarchy levels:
• [edit policy-options]
• [edit logical-systems logical-system-name policy-options]
To define a policy condition based on the existence of routes in specific tables for use in
BGP export policies, specify a name for the condition and include the following options:
• if-route-exists address—Specify the address of the route in question.
132
Copyright © 2010, Juniper Networks, Inc.