16.03.2014 Views

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Junos 10.4 <strong>Policy</strong> <strong>Framework</strong> <strong>Configuration</strong> <strong>Guide</strong><br />

In this example, the ISP policies are configured in an outbound direction; that is, the<br />

example focuses on the routes that the ISP announces to its peers and customers, and<br />

includes the following:<br />

1. The ISP has been assigned AS 1000 and the routing space of 192.168.0/17. With the<br />

exception of the two customer networks shown in Figure 11 on page 83, all other<br />

customer routes are simulated with static routes.<br />

2. The ISP has connectivity to two different exchange peers: AS 11111 and AS 22222. These<br />

peers are used for transit service to other portions of the Internet. This means that the<br />

ISP is accepting all routes (the full Internet routing table) from those BGP peers. To<br />

help maintain an optimized Internet routing table, the ISP is configured to advertise<br />

only two aggregate routes to the transit peers.<br />

3. The ISP also has direct connectivity to two private peers: AS 7000 and AS 8000. The<br />

ISP administrators want all data to the private peers to use this direct link. As a result,<br />

all the customer routes from the ISP are advertised to those private peers. These peers<br />

then advertise all their customer routes to the ISP.<br />

4. Finally, the ISP has two customers with which it communicates using BGP: AS 1234<br />

and AS 2468. Each customer has a different set of requirements.<br />

The following sections discuss the following topics:<br />

• Requesting a Single Default Route on the Customer 1 Router on page 84<br />

• Requesting Specific Routes on the Customer 2 Router on page 85<br />

• Configuring a Peer <strong>Policy</strong> on ISP Router 3 on page 87<br />

• Configuring Private and Exchange Peers on ISP Router 1 and 2 on page 89<br />

• Configuring Locally Defined Static Routes on the Exchange Peer 2 Router on page 92<br />

• Configuring Outbound and Generated Routes on the Private Peer 2 Router on page 93<br />

Requesting a Single Default Route on the Customer 1 Router<br />

Customer 1 has only a single route to the ISP and is using the ISP for transit service. This<br />

customer has requested a single default route (0.0.0.0/0) from the ISP.<br />

[edit]<br />

interfaces {<br />

so-0/0/1 {<br />

description "Connection to ISP Router 3";<br />

unit 0 {<br />

family inet {<br />

address 10.222.70.1/30;<br />

}<br />

}<br />

}<br />

fxp0 {<br />

description "MGMT INTERFACE - DO NOT DELETE";<br />

unit 0 {<br />

family inet {<br />

address 10.251.0.9/24;<br />

}<br />

}<br />

84<br />

Copyright © 2010, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!