Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring BGP Route Target Filtering for VPNs
- ACX, M, MX, PTX, QFX, SRX, T Series
- Understanding How to Define BGP Communities and Extended Communities in the Routing Policy Feature Guide for Routing Devices
- M, MX, T Series
- Example: Configuring an Export Policy for BGP Route Target Filtering
- Understanding Proxy BGP Route Target Filtering
- M, MX, PTX, T Series
- family route-target
rtf-prefix-list
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.2.
Description
Define a list of route target prefixes for use in a routing policy statement. These prefixes are only useful for filtering routes in the bpg.rtarget.0 table.
The route target filtering prefix is in the format: AS number:route target extended community/length. The first number represents the autonomous system (AS) of the device that sent the advertisement. The second group of numbers represent the route target extended community. The format of the extended community is the same as the extended community type target:. For more information about extended communities, see Understanding How to Define BGP Communities and Extended Communities .
In this route target prefix example 200:200:101/96, 200 is the AS number, 200:101 is the BGP extended community used for the route target, and 96 is the prefix length.
For more information about the route target community, see RFC 4360, BGP Extended Communities Attribute.
For more information about the route target filtering prefix format, see RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs).
Options
name—Name that identifies the list of route target filtering prefixes. The name can contain letters, numbers, and hyphens ( - ) and can be up to 255 characters long. To include spaces in the name, enclose the entire name in quotation marks (“ “).
route-targets—List of route target filtering prefixes, one route target filter per line in the configuration. When you use the rtf-prefix-list statement as a match condition, you do not have the option of configuring the list of route target filtering prefixes. You must first define and configure the route target filtering prefixes with the policy-options statement.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring BGP Route Target Filtering for VPNs
- ACX, M, MX, PTX, QFX, SRX, T Series
- Understanding How to Define BGP Communities and Extended Communities in the Routing Policy Feature Guide for Routing Devices
- M, MX, T Series
- Example: Configuring an Export Policy for BGP Route Target Filtering
- Understanding Proxy BGP Route Target Filtering
- M, MX, PTX, T Series
- family route-target
Published: 2013-07-31
Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring BGP Route Target Filtering for VPNs
- ACX, M, MX, PTX, QFX, SRX, T Series
- Understanding How to Define BGP Communities and Extended Communities in the Routing Policy Feature Guide for Routing Devices
- M, MX, T Series
- Example: Configuring an Export Policy for BGP Route Target Filtering
- Understanding Proxy BGP Route Target Filtering
- M, MX, PTX, T Series
- family route-target
