Owner's Manual

698 | Chapter 26. BGP
NETGEAR 8800 User Manual
• RFC 2439—BGP Route Flap Damping
• RFC 2796—BGP Route Reflection - An Alternative to Full Mesh IBGP
• RFC 2918—Route Refresh Capability for BGP-4
• RFC 3392—Capabilities Advertisement with BGP-4
• RFC 4486—Subcodes for BGP Cease Notification Message
• RFC 4360—BGP Extended Communities Attribute
• RFC 4760—Multiprotocol Extensions for BGP-4
• RFC 4893—BGP Support for Four-octet AS Number Space
• RFC 5396—Textual Representation of Autonomous System (AS) Numbers
• draft_ieft_idr_restart_10.txt—Graceful Restart Mechanism for BGP
Note: XCM8800 supports BGP version 4 only.
Note: For complete information about software licensing, including how to
obtain and upgrade your license and what licenses are appropriate
for these features, see Appendix A, XCM8800 Software Licenses.
BGP Four-Byte AS Numbers
The XCM8800 software supports 4-byte AS numbers, which can be entered and displayed in
the ASPLAIN and ASDOT formats, which are described in RFC 5396, Textual Representation
of Autonomous System (AS) Numbers.
Note: When entering an AS number in a policy file, you must enter a
unique 2-byte or 4-byte AS number. The transition AS number, AS
23456, is not supported in policy files.
BGP Attributes
The following BGP attributes are supported by the switch:
• Origin—Defines the origin of the route. Possible values are Interior Gateway Protocol
(IGP), Exterior Gateway Protocol (EGP), and incomplete.
• AS_Path—The list of ASs that are traversed for this route. The local AS-path is added to
the BGP update packet after the policy is applied.
• AS4_Path—This attribute is used by 4-byte peers when sending updates to 2-byte peers.
This attribute carries AS-number information that can be represented only in 4-bytes.