BGP local router ID |
ID of the BGP local router. If two ends have the same BGP local router ID, no BGP peer relationship can be established between them. In this situation, run the router id command in the BGP view on either end to change the BGP local router ID. Changing it to the IP address of a loopback interface is recommended.
|
State |
Status of the peer:
- Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP. Upon receiving a Start event, BGP initiates a TCP connection request to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection request initiated by the remote BGP peer, and changes its state to Connect.
- Connect: indicates that BGP is waiting for the TCP connection to be set up before it determines whether to perform other operations.
- If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent.
- If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection request initiated by the remote peer, and changes its state to Active.
- If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection request to the remote BGP peer, and stays in the Connect state.
- Active: indicates that BGP tries to set up a TCP connection. This is the intermediate status of BGP.
- If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent.
- If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect.
- If BGP initiates a TCP connection request with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state.
- OpenSent: indicates that BGP has sent one Open message to its peer and is waiting for the other Open message from the peer.
- If there are no errors in the Open message received, BGP changes its state to OpenConfirm.
- If there are errors in the Open message received, BGP sends a Notification message to the remote peer and changes its state to Idle.
- If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection request initiated by the remote peer, and changes its state to Active.
- OpenConfirm: indicates that BGP is waiting for a Notification or Keepalive message.
- If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle.
- If BGP receives a Keepalive message, BGP changes its state to Established.
- Established: indicates that BGP peers can exchange Update, Notification, and Keepalive messages.If BGP receives an Update or a Keepalive message, its state stays in Established.If BGP receives a Notification message, BGP changes its state to Idle.
- No neg: The address family is not enabled for the BGP peer. In this state, Update messages can be exchanged in other address families whose capabilities have been successfully negotiated.
If the address family is enabled for the BGP peer, the local BGP peer receives a Notification message, and the peer relationship is disconnected. Then, the BGP peer changes to the Idle state and re-establishes the peer relationship.
|