Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte Autonomous System Numbers
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 2-Byte AS Number
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 4-Byte AS Number
- Juniper Networks Implementation of 4-Byte Autonomous System Numbers
- Prepending 4-Byte AS Numbers in an AS Path
- Understanding 4-Byte AS Numbers and Route Distinguishers
- Understanding 4-Byte AS Numbers and Route Loop Detection
- Understanding a 4-Byte Capable Router AS Path Through a 2-Byte Capable Domain
Configuring 4-Byte AS Numbers and BGP Extended Community Attributes
A BGP community is a group of destinations that share a common property. You can configure the standard community attribute and extended community attributes for inclusion in BGP update messages.
For example, when configuring a VPN routing and forwarding (VRF) instance, you need to configure a route target. A route target is one type of BGP extended community attribute. To create a named BGP extended community attribute, include the community statement and specify the community members:
To specify the community members, you must specify the community ID. The community ID consists of three components that you specify in the following format:
The administrator field of some BGP extended community attributes is an AS number. To configure a target extended community, which includes a 4-byte AS number in the plain-number format, append the letter “L” to the end of the number.
In the following example, a target community with the 4-byte AS number 334324 and an assigned number of 132 is represented as target:334324L:132.
 | Note: If you display the target extended community information on a peer router that does not support 4-byte AS numbers, the router displays target:unknown format. |
Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte Autonomous System Numbers
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 2-Byte AS Number
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 4-Byte AS Number
- Juniper Networks Implementation of 4-Byte Autonomous System Numbers
- Prepending 4-Byte AS Numbers in an AS Path
- Understanding 4-Byte AS Numbers and Route Distinguishers
- Understanding 4-Byte AS Numbers and Route Loop Detection
- Understanding a 4-Byte Capable Router AS Path Through a 2-Byte Capable Domain
Published: 2012-11-14
Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte Autonomous System Numbers
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 2-Byte AS Number
- Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte Capable Router Using a 4-Byte AS Number
- Juniper Networks Implementation of 4-Byte Autonomous System Numbers
- Prepending 4-Byte AS Numbers in an AS Path
- Understanding 4-Byte AS Numbers and Route Distinguishers
- Understanding 4-Byte AS Numbers and Route Loop Detection
- Understanding a 4-Byte Capable Router AS Path Through a 2-Byte Capable Domain
