Reference Guide
Usage
Information
To accept 4-byte formats before entering a 4-byte AS number, configure your system. All the
routers in the Confederation must be 4 byte or 2 byte identified routers. You cannot mix them.
The autonomous systems configured in this command are visible to the EBGP neighbors. Each
autonomous system is fully meshed and contains a few connections to other autonomous
systems. The next hop, MED, and local preference information is preserved throughout the
confederation.
FTOS accepts confederation EBGP peers without a LOCAL_PREF attribute. The software sends
AS_CONFED_SET and accepts AS_CONFED_SET and AS_CONF_SEQ.
Related
Commands
bgp four-octet-as-support — enables 4-byte support for the BGP process.
bgp confederation peers
Specify the autonomous systems (ASs) that belong to the BGP confederation.
Z9000
Syntax
bgp confederation peers as-number [...as-number]
To return to the default, use the no bgp confederation peers command.
Parameters
as-number
Enter the AS number. The range is from 0 to 65535 (2 byte), from 1 to
4294967295 (4 byte), or from 0.1 to 65535.65535 (dotted format).
...as-number
(OPTIONAL) Enter up to 16 confederation numbers. The range is from
0 to 65535 (2 byte), from 1 to 4294967295 (4 byte), or from 0.1 to
65535.65535 (dotted format).
Defaults Not configured.
Command Modes ROUTER BGP
Command History
This guide is platform-specific. For command information about other platforms, refer to the
relevant
FTOS Command Line Reference Guide
.
The following is a list of the FTOS version history for this command.
Version 8.3.19.0 Introduced on the S4820T.
Version 8.3.11.1 Introduced on the Z9000.
Version 8.3.7.0 Introduced on the S4810.
Version 7.8.1.0 Introduced on the S-Series.
Version 7.7.1.0 Introduced on the C-Series. Added support for the 4-byte format.
Usage
Information
All the routers in the Confederation must be 4 byte or 2 byte identified routers. You cannot mix
them.
The autonomous systems configured in this command are visible to the EBGP neighbors. Each
autonomous system is fully meshed and contains a few connections to other autonomous
systems.
After specifying autonomous systems numbers for the BGP confederation, recycle the peers to
update their configuration.
267