Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
export [ dmz local-customers ];
}
}
Example: Applying Export and Import Policies to BGP Peer Groups
For three BGP peer groups, apply various export and import filters.
[edit]
protocols {
bgp {
group 1 {
type external;
peer-as 47;
export local-customers;
import [ martian-filter long-prefix-filter as47-filter ];
neighbor 192.168.1.4;
neighbor 192.168.1.5;
}
group 2 {
type external;
peer-as 42;
export local-customers;
import [ martian-filter long-prefix-filter as42-filter ];
neighbor 192.168.1.4;
neighbor 192.168.1.5;
}
group 3 {
type internal;
export local-customers;
neighbor 10.1.1.1;
}
}
}
Example: Defining a Routing Policy Based on the Number of BGP Communities
Create a policy that accepts BGP routes based on the number of BGP communities. In
this example, routes can contain two, three, or four communities to be considered a
match. For example, if a route contains three communities, it is considered a match and
is accepted. If a route contains one community, it is not considered a match and is rejected.
[edit]
policy-options {
policy-statement import-bgp {
term community {
from {
community-count 2 orhigher;
community-count 4 orlower;
}
then {
accept;
}
}
}
Copyright © 2010, Juniper Networks, Inc.
75