Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
• Example: Exporting IS-IS Level 2 Routes to Level 1 on page 78
• Example: Assigning Different Forwarding Next-Hop LSPs to Different Destination
Prefixes on page 78
• 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: Defining a Routing Policy from BGP to IS-IS
Accept BGP routes advertised by the peer 192.168.1.1. If a route matches, it is accepted,
and no further evaluation is performed on that route. If a route does not match, the accept
or reject action specified by the default policy is taken. (For more information about the
default routing policies, see “Default Routing Policies and Actions” on page 20.) If you
apply this routing policy to imported BGP routes, only the routes learned from the peer
192.168.1.1 and BGP transit routes are accepted from BGP peers.
[edit]
policy-options {
policy-statement bgp-to-isis {
term term1 {
from {
neighbor 192.168.1.1;
}
then {
accept;
}
}
}
}
Example: Using Routing Policy to Set a Preference
Define a routing policy which matches routes from specific next hops that are being
advertised to specific neighbors and which sets a preference. If a route does not match
the first term, it is evaluated by the second term. If it still does not match, the next routing
policy, if configured, is evaluated; then the accept or reject action specified by the default
policy is taken. (For more information about the default routing policies, see “Default
Routing Policies and Actions” on page 20.)
[edit]
policy-options {
policy-statement set-preference {
term term1 {
from {
next-hop [ 10.0.0.1 10.0.0.2 ];
}
to {
Copyright © 2010, Juniper Networks, Inc.
73