BGP General Operation and Messaging
(Page 2 of 2)
Route Information Exchange
Assuming the link is initialized, the two peers begin an ongoing process of telling each other what they know about networks and how to reach them. Each BGP speaker encodes information from its Routing Information Bases (RIBs) into BGP Update messages. These messages contain lists of known network addresses, as well as information about paths to various networks, described in the form of path attributes. This information is then used for the route determination as described in the preceding topic.
When a link is first set up between two peers, they ensure complete information is held by each router by exchanging their complete routing tables. Subsequently, Update messages are sent that contain only incremental updates about routes that have changed. Exchanging only updated information as needed reduces unnecessary bandwidth on the network, making BGP more efficient than it would be if it sent full routing table information on a regular basis.
The TCP session between BGP speakers can be kept open for a very long time, but Updates need to be sent only when changes occur to routes, which are usually infrequent. This means many seconds may elapse between the transmission of Update messages. To ensure that the peers maintain contact with each other, they both send Keepalive messages on a regular basis when they dont have other information to send. These are null messages that contain no data and just tell the peer device I'm still here. These messages are sent infrequentlyno more often than one per secondbut regularly enough that the peers won't think the session was interrupted.
The last type of BGP message is the BGP Notification message. This is an error message; it tells a peer that a problem occurred and describes the nature of the error condition. After sending a BGP Notification message, the device that sent it will terminate the BGP connection between the peers. A new connection will then need to be negotiated, possibly after the problem that led to the Notification has been corrected.
For more details on the four BGP message types and a description of the format used by each, refer to the detailed BGP operation section.
Home - Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.