OpenConfirm

Nov 30,2008 00:00 by alperen
OpenConfirm state In the OpenConfirm state, the BGP speaker is waiting to receive a
KEEPALIVE message from the remote BGP speaker. Once the KEEPALIVE message is
received, the BGP speaker resets the hold timer and transitions to the Established state. At
this point, the peer relationship has been formed. If a NOTIFICATION message is received
instead of a KEEPALIVE message, the BGP speaker changes its state to Idle. In the case of
the hold timer expiring before the KEEPALIVE message is received, the BGP speaker sends
a NOTIFICATION message to the remote BGP speaker, ends the TCP session, and changes
its state to Idle. The BGP speaker may receive a disconnect message from TCP. If this happens,
the BGP speaker will change its state to Idle. The BGP speaker will also change its
state to Idle if a stop event is initiated automatically or by the system administrator. If any
other types of events cause an error, the BGP speaker closes the TCP connection and transitions
its state to Idle. All BGP start events are ignored in the OpenConfirm state.