BGP States

You might also like

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 1

>> IDLE

Initiates a TCP connection to its configured BGP peers.


Listens for incoming TCP connections.
ConnectRetry timer starts (60 seconds — cannot be changed).
>> Connect
Waits for the TCP connection to complete.
If TCP is successful:
Sends an OPEN message to its peers.
Changes the state to OpenSent and clears the CR timer.
If TCP is unsuccessful:
ConnectRetry timer is reset.
BGP goes into the Active state.
>> Active
The BGP speaker tries to acquire its peer by initiating another TCP
connection.
If TCP is successful:
ConnectRetry timer is cleared.
Sends an OPEN message to peer and changes state to OpenSent.
If TCP is unsuccessful:
ConnectRetry timer is reset.
BGP goes into Idle state.
>> OpenSent
Waits to receive an OPEN message from its peer and verifies all the fields.
The message contains the BGP version, AS number, fold time, and BGP ID.
BGP Versions must match.
The source IP address of the OPEN message must match the IP address
that is configured for the neighbor.
The AS number in the OPEN message must match what is configured for the
neighbor.
BGP Identifiers (RID) must be unique. If a RID does not exist, this
condition is not met.
Security Parameters (Password, TTL, and the like)

If successful:
BGP starts sending keepalives and sets its hold and keepalive
timers.
If unsuccessful:
ConnectRetry timer is reset.
BGP goes into Idle state.
>> OpenConfirm
BGP waits to receive keepalives from its peer.
If successful:
State is changed to established.
If unsuccessful:
ConnectRetry timer is reset.
BGP goes into Idle state.
>> Established
Exchange of update, notification, and keepalive messages take place with the
peer.
Each update or keepalive results in hold time reset. Default keepalive is 60
seconds, and the hold time is 180 seconds.

You might also like