BGP State
Idle The BGP process is either administratively down or awaiting the next retry
attempt.
Connect The BGP process is waiting for the TCP connection to be completed. You
cannot determine from this state information whether the TCP connection
can complete.
Active The TCP connection has been completed, but no BGP messages have yet
been sent to the peer.
Opensent he TCP connection exists, and a BGP Open message has been sent to the
peer, but the matching Open message has not yet been received from the
other router.
Openconfirm An Open message has been both sent to and received from the other router.
The next step is to receive a BGP Keepalive message (to confirm that all
neighbor-related parameters match) or a BGP Notification message (to learn
that there is some mismatch in neighbor parameters).
Established ll neighbor parameters match, the neighbor relationship works, and the
peers can now exchange Update messages.
Idle The BGP process is either administratively down or awaiting the next retry
attempt.
Connect The BGP process is waiting for the TCP connection to be completed. You
cannot determine from this state information whether the TCP connection
can complete.
Active The TCP connection has been completed, but no BGP messages have yet
been sent to the peer.
Opensent he TCP connection exists, and a BGP Open message has been sent to the
peer, but the matching Open message has not yet been received from the
other router.
Openconfirm An Open message has been both sent to and received from the other router.
The next step is to receive a BGP Keepalive message (to confirm that all
neighbor-related parameters match) or a BGP Notification message (to learn
that there is some mismatch in neighbor parameters).
Established ll neighbor parameters match, the neighbor relationship works, and the
peers can now exchange Update messages.
No comments:
Post a Comment