BGP active vs connect state question

...the heck is the difference? 

Active: "In this state, the BGP process is waiting for the TCP connection to be completed."

Connect: "In this state, the BGP process is trying to initiate a TCP connection with the neighbor."

It would seem as if one end is initiating the TCP connection..but active/connect are states..so it would seem to me as if one would go through the active and connect states.

Thoughts?

Comments

  • Hi Kyle,

     

    RFC 4271

     

      IDLE :

      BGP FSM refuses all incoming BGP connections for this peer. No resources are allocated to the peer. 

    CONNECT :
    In this state, BGP FSM is waiting for the TCP connection to be completed.
    ACTIVE : 
    In this state, BGP FSM is trying to acquire a peer by listening for, and accepting, a TCP connection.
    OPENSENT :
    In this state, BGP FSM waits for an OPEN message from its peer.
    OPENCONFIRM :
    In this state, BGP waits for a KEEPALIVE or NOTIFICATION message.
    ESTABLISHED :
    In the Established state, the BGP FSM can exchange UPDATE, NOTIFICATION, and KEEPALIVE messages with its peer.
    debug ip bgp command outlines the BGP setup.
    
    
    
    
    
    



  • So there is a state where it is trying to initiate and a state where it is listening, basically?

    I've read some places where active is like...a state when a TCP connection isn't made..but ..just doesn't make much sense.

     

Sign In or Register to comment.