Bgp Updates; Bgp Sessions; Specifications - Motorola BSR 2000 Configuration And Management Manual

Release 1.0

BGP Updates

BGP routers exchange routing information in the form of BGP updates. BGP updates
contain the following attributes associated with routes that a BGP peer advertises to
its neighbors:

BGP Sessions

After exchanging a series of messages, the BGP peers establish a session over TCP.
BGP session partners rely on TCP to manage the underlying connection. Once a TCP
connection is established, a BGP router uses port 179 to communicate full routing
information with another BGP peer. As long as the connection is up, the BGP partners
can exchange a very simple set of messages with minimal overhead.
The BGP protocol includes the exchange of keep-alive messages between peers. A
keep-alive message is a signal from one endpoint to another, indicating that the first
end point is still active. Keep-alive messages are necessary to keep BGP peers aware
of the health of the connection, because TCP does not provide this service.

Specifications

The BSR supports the following Request for Comment (RFC) specifications:
526360-001-00 Rev. B
A list of ASs the routing update passed through
The AS routing update origin
Next hop information
Metrics specifying route preference
RFC 1771 — A Border Gateway Protocol 4 (BGP-4)
RFC 1745 — BGP4/IDRP for IP (OSPF Interaction)
RFC 1965 — Autonomous System Confederations for BGP
RFC 1997 — BGP Communities Attributes
RFC 1998 — An Application of the BGP Community Attribute in Multi-home
Routing
RFC 2439 — BGP Route Flap Damping
RFC 2385 — Protection of BGP Sessions via the TCP MD5 Signature Options
MGBI
Configuring BGP
12-5