Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
}
}
policy-statement if-upstream-routes-exist {
term only-certain-contributing-routes {
from { # allow either the 10.100.0.0/17 or the 10.101.0.0/27 route
route-filter 10.100.0.0/17 exact; # route to activate the generated route
route-filter 10.101.0.0/27 exact; # route to activate the generated route
}
then accept; # do not allow any other route to activate
} # the generated route in the routing table
term reject-all-other-routes {
then reject;
}
}
policy-statement customer-2--peer { # advertise customer routes to all peers
term statics {
from protocol static;
then accept;
}
term-isp-and-customer routes { # advertise internal AS 1000 customer
from { # to the customer
protocol-bgp;
route-filter 192.168.0.0/17 orlonger;
}
then accept;
} # advertise just the default route to AS 2468
term default-route {
from {
route-filter 0.0.0.0/exact;
}
then accept;
}
term reject-all-other-routes { # do not advertise any other routes
then reject;
}
}
policy-statement customer-1-peer {
term default-route { # advertise just the default route to AS 1234
from {
route-filter 0.0.0.0/0 exact;
}
then accept;
}
term reject-all-other-routes { # do not advertise any other routes
then reject;
}
}
}
Configuring Private and Exchange Peers on ISP Router 1 and 2
ISP Router 1 and ISP Router 2 each have two policies configured: the private-peers policy
and the exchange-peers policy. Because of their similar configurations, this example
describes the configuration only for ISP Router 2.
Copyright © 2010, Juniper Networks, Inc.
89