Filter
Top Products
Command
Modes
ROUTER BGP
Command
History
This guide is platform-specific. For command information about other platforms,
refer to the relevant Dell Networking OS Command Line Reference Guide.
The following is a list of the Dell Networking OS version history for this command.
Version Description
9.7(0.0) Introduced on the S6000–ON.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
7.8.1.0 Introduced on the S-Series.
7.7.1.0 Introduced on the C-Series. Added support for the 4-byte
format
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.
Dell Networking OS accepts confederation EBGP peers without a LOCAL_PREF
attribute. The software sends AS_CONFED_SET and accepts AS_CONFED_SET and
AS_CONF_SEQ.
If a local-as is configured, BGP does not allow for the configuration of BGP
confederation. Similarly, if BGP confederation is configured, then BGP does not
allow the configuration of local-as.
If the neighbor is an eBGP neighbor, then BGP performs a check on the first AS
number. In this scenario, it is mandatory that the first sequence in the AS path is of
type AS_SEQUENCE or AS_CONFED_SEQUENCE (in the case of confederations). If
the first entry appears as an AS_CONFED_SET and the neighbor is not in the local
AS, then this is strictly a problem with the neighbor node.
This command automatically restarts the BGP instance for the configuration to
take effect.
Related
Commands
bgp four-octet-as-support — enables 4-byte support for the BGP process.
414
Border Gateway Protocol