Navigation
Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte AS Numbers and BGP Extended Community Attributes
- 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
- M, PTX, QFX, T Series
- Disabling Attribute Set Messages on Independent AS Domains for BGP Loop Detection
Configuring 4-Byte Autonomous System Numbers
This section describes how to configure a 4-byte AS number and how to verify if the BGP peer supports 4-byte AS numbers.
The AS number can be specified in plain number format or in AS-dot notation format on routers running Junos OS Release 9.2 and later. For example, the 4-byte AS number of 65,546 is represented in plain-number format as 65546. The same AS number is represented in AS-dot notation format as 1.10 on routers running Junos OS Release 9.2 and later.
- To configure a 4-byte AS number in AS-dot notation format,
include the autonomous-system statement and specify the
4-byte AS number. In the following example the AS number is set to 1.10.user@host# set routing-options autonomous-system 1.10
- To configure a 4-byte AS number in plain number format,
include the autonomous-system statement and specify the
4-byte AS number. In the following example the AS number is set to 65546.user@host# set routing-options autonomous-system 65546
- After a BGP peer session has been negotiated, you can
verify whether the peer supports 4-byte AS numbers or not. To verify
whether the peer supports 4-byte AS numbers or not, use the show bgp neighbor command. In the following example the peer does
not support 4-byte AS numbers.
user@host# show bgp neighbor 192.168.1.9 | match "AS"Peer: 192.168.1.9+179 AS 65056 Local: 192.168.1.3+52616 AS 65000 Peer does not support 4 byte AS extension
- In the following example the peer does support 4-byte
AS numbers.
user@host# show bgp neighbor 192.168.1.9 | match "AS"Peer: 192.168.1.10+52679 AS 1000000000 Local: 192.168.1.3+179 AS 65000 Peer supports 4 byte AS extension (peer-as 1000000000)
Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte AS Numbers and BGP Extended Community Attributes
- 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
- M, PTX, QFX, T Series
- Disabling Attribute Set Messages on Independent AS Domains for BGP Loop Detection
Published: 2013-02-08
Related Documentation
- M, MX, PTX, T Series
- 4-Byte Autonomous System Numbers Overview
- Configuring 4-Byte AS Numbers and BGP Extended Community Attributes
- 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
- M, PTX, QFX, T Series
- Disabling Attribute Set Messages on Independent AS Domains for BGP Loop Detection
