
Configuring IP Services
5-8
Keeping the Connection Alive
Once Open messages have been exchanged, each speaker then sends a Keepalive
message (see “Keepalive Message” on page 5-10) to confirm the BGP connection.
A neighbor relationship now exists between the two BGP peers. BGP peers
periodically issue a Keepalive message to maintain the connection.
Sending an Update Message on the Connection
Once a connection is established, the BGP speaker uses one or more Update
messages (see “Update Message” on page 5-10) to send the entire IP routing table
(compliant with local BGP export policies). BGP, however, does not require the
entire routing table to be sent again. Therefore, the BGP speaker must keep a
current version of the routing information received from of all of its peers for as
long as the connection to each peer is valid. This information will be updated via
Update messages whenever changes occur.
Terminating a Connection
If a condition occurs that causes a BGP speaker to terminate a peer-to-peer
connection, the BGP speaker issues a Notification message, specifying the reason
(see “Notification Message” on page 5-15). The connection is immediately
terminated.
Site Manager allows you to specify how often the BGP speaker issues a Keepalive
message on a peer-to-peer connection. For instructions, see the Keepalive Timer
parameter on page 5-43.
Site Manager allows you to specify how often a BGP speaker issues Update messages
and how long the BGP speaker waits for an Update message (or a Keepalive message)
before terminating the connection. For instructions, see the External Advertisement Timer
parameter on page 5-42 and the Holdtime parameter on page 5-43.
Komentarze do niniejszej Instrukcji