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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

type:administrator:assigned-number<br />

type is the type of extended community and can be either the 16-bit numerical identifier<br />

of a specific BGP extended community or one of these types:<br />

• bandwidth—Sets up the bandwidth extended community. Specifying link bandwidth<br />

allows you to distribute traffic unequally among different BGP paths.<br />

NOTE: The link bandwidth attribute does not work concurrently with<br />

per-prefix load balancing.<br />

• domain-id—Identifies the OSPF domain from which the route originated.<br />

• origin—Identifies where the route originated.<br />

• rt-import—Identifies the route to install in the routing table.<br />

NOTE: You must identify the route by an IP address, not an AS number.<br />

• src-as—Identifies the AS from which the route originated. You must specify an AS<br />

number, not an IP address.<br />

NOTE: You must identify the AS by an AS number, not an IP address.<br />

• target—Identifies the destination to which the route is going.<br />

NOTE: For an import policy for a VPN routing and forwarding (VRF)<br />

instance, you must include at least one route target. Additionally, you<br />

cannot use wildcard characters or regular expressions in the route target<br />

for a VRF import policy. Each value you configure for a route target for a<br />

VRF import policy must be a single value.<br />

administrator is the administrator. It is either an AS number or an IP version 4 (IPv4)<br />

address prefix, depending on the type of extended community.<br />

assigned-number identifies the local provider.<br />

In Junos OS Release 9.1 and later, you can specify 4-byte AS numbers as defined in<br />

RFC 4893, BGP Support for Four-octet AS Number Space, as well as the 2-byte AS numbers<br />

that are supported in earlier releases of the Junos OS. In plain-number format, you can<br />

configure a value in the range from 1 through 4,294,967,295. To configure a target or<br />

origin extended community that includes a 4-byte AS number in the plain-number format,<br />

append the letter “L” to the end of number. For example, a target community with the<br />

4-byte AS number 334,324 and an assigned number of 132 is represented as<br />

target:334324L:132.<br />

108<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!