25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 5-23 shows the flow of these message types between two autonomous<br />

systems.<br />

ASX<br />

BGP<br />

Figure 5-23 BGP message flows between BGP speakers<br />

Opening <strong>and</strong> confirming a BGP connection<br />

After a <strong>TCP</strong> session has been established between two peer nodes, each router<br />

sends an OPEN message to the neighbor. The OPEN message includes:<br />

► The originating router's AS number <strong>and</strong> BGP router identifier.<br />

► A suggested value for the hold timer. We discuss the function of this timer in<br />

the next section.<br />

► Optional parameters. This information is used to authenticate a peer.<br />

An OPEN message contains support for authenticating the identity of a BGP<br />

peer. However, the BGP st<strong>and</strong>ard does not specify a specific authorization<br />

mechanism. This allows BGP peers to select any supported authorization<br />

scheme.<br />

An OPEN message is acknowledged by a KEEPALIVE message. After peer<br />

routers have established a BGP connection, they can exchange additional<br />

information.<br />

Open<br />

Keep Alive<br />

Update<br />

Notification<br />

Maintaining the BGP connection<br />

BGP does not use any transport-based keepalive to determine if peers are<br />

reachable. Instead, BGP messages are periodically exchanged between peers.<br />

If no messages are received from the peer for the duration specified by the hold<br />

timer, the originating router assumes that an error has occurred. When this<br />

happens, an error notification is sent to the peer <strong>and</strong> the connection is closed.<br />

BGP<br />

ASY<br />

BGP<br />

Chapter 5. Routing protocols 221

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!