Administrator Guide
BGP 1323
Dell Networking BGP supports the following RFCs in whole or in part as
indicated:
• RFC 1997 – BGP Communities Attribute
• RFC 2385 – Protection of BGP Sessions via the TCP MD5 Signature
Option
• RFC 2545 – Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-
Domain Routing
• RFC 2918 – Route Refresh Capability for BGP-4
• RFC 4271 – A Border Gateway Protocol 4 (BGP-4)
• RFC 4273 – Definitions of Managed Objects for BGP-4
• RFC 4456 – BGP Route Reflection: An Alternative to Full Mesh Internal
BGP (IBGP)
• RFC 4486 – Sub-codes for BGP Cease Notification Message
• RFC 4760 – Multiprotocol Extensions for BGP-4
• RFC 5492 – Capabilities Advertisement with BGP-4
Dell Networking BGP supports both IPv4 and IPv6 peering sessions and
supports both IPv4 and IPv6 routes (RFC 4760 and RFC 2545). IPv6 peering
sessions support IPv6 routes only, but IPv4 addresses may be embedded
within IPv6 routes.
TCP MD5 authentication is supported, however, RFC 5295 is not supported.
Dell Networking BGP also supports a private MIB with information regarding:
• Internal BGP message queue status
• Transmit and receive message counters
• Decision process statistics
• Per-peer message and prefix counters
Dell Networking BGP supports configuration via the CLI only.
Routing must be enabled to enable Dell Networking BGP. Both the AS
number and the router ID are required to be configured. Enabling of BGP is
automatic when the AS number and router ID are configured. The no enable
command may be used to temporarily disable BGP without removing the
BGP configuration.