- peer-as autonomous-system;
- [edit logical-systems logical-system-name protocols bgp],
- [edit logical-systems logical-system-name protocols bgp group group-name],
- [edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
bgp],
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
bgp group group-name],
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
bgp group group-name neighbor address],
- [edit protocols bgp],
- [edit protocols bgp group group-name],
- [edit protocols bgp group group-name neighbor address],
- [edit routing-instances routing-instance-name protocols bgp],
- [edit routing-instances routing-instance-name protocols bgp group group-name],
- [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address]
Statement introduced before JUNOS Release 7.4.
Specify the neighbor (peer) AS number.
The autonomous system (AS) numeric range in plain-number format has been extended in JUNOS Release 9.1 to provide BGP support for 4-byte AS numbers, as defined in RFC 4893, BGP Support for Four-octet AS Number Space.
Beginning with JUNOS Release 9.2, you can also configure a 4-byte AS number using the AS-dot notation format of two integer values joined by a period: <16-bit high-order value in decimal>.<16-bit low-order value in decimal>. For example, the 4-byte AS number of 65,546 in plain-number format is represented as 1.10 in the AS-dot notation format.
autonomous-system—AS number.
See Defining BGP Groups and Peers and Specifying the Peer’s AS Number.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.