Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
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;
default-action (accept | reject);
}
}
}
}
The resulting action is set either by the protocol or by the last policy term that is matched.
Example: Configuring the Default Action in a Routing Policy
Configure a routing policy that matches routes based on three policy terms. If the route
matches the first term, a certain community tag is attached. If the route matches two
separate terms, then both community tags are attached. If the route does not match any
terms, it is rejected (protocol’s default action). Note that the terms hub and spoke are
mutually exclusive.
[edit]
policy-options {
policy-statement test {
term set-default {
then default-action reject;
}
term hub {
from interface ge-2/1/0.5;
then {
community add test-01-hub;
default-action accept;
}
}
term spoke {
from interface [ ge-2/1/0.1 ge-2/1/0.2 ];
then {
community add test-01-spoke;
default-action accept;
}
}
term management {
from protocol direct;
then {
community add management;
default-action accept;
}
}
Copyright © 2010, Juniper Networks, Inc.
55