Tag Archives

2 Articles


BGP Neighbor States – IDLE – CONNECT – ACTIVE From this explanation we might understand that a BGP process remains in ACTIVE state is due to TRANSPORT ERROR means the BGP process is unable to initiate a TCP Connection to the Neighbor. Refer the below flow chart where it explains the FSM transitions of three states IDLE, CONNECT and ACTIVE. In real-time BGP never remain in an particular state other than ESTABLISHED. Actually it flaps between IDLE, CONNECT and ACTIVE. BGP Stuck in IDLE Input Events 1 & 13 causes the IDLE state remain in IDLE state. IE1 is BGP START event and IE13 is BGP Notification Received. Also IE 2, 4, 6, 8, 9, 13 causes other BGP states to transit back to IDLE. So the possible reason for a BGP router remain in IDLE is mentioned below. BGP Stuck in ACTIVE Input Event 5 cause the ACTIVE state […]

 bgp bgp-fsm bgp-stuck-in-active bgp-stuck-in-idle 

BGP Message Types & FSM

In this tutorial we will discuss about different message types of BGP, BGP Peer Connection, BGP Finite State Machine. Before establishing BGP Peer Connection, two neighbor must perform TCP Three-Way-Handshake and open a connection to Port number 179. BGP is a Transport Layer Protocol, hence TCP provides fragmentation, acknowledgement, sequencing functions necessary for reliable connection. BGP Peer must be statically configured and a route must present in the routing table. All the BGP Messages are unicast over TCP Connection. BGP Uses five basic message. BGP Messages All BGP Messages have a common header and encapsulated into a TCP Fragment. Header consists of Marker, Length and Type of the BGP Messages. A Keepalive message is nothing but a BGP Header. Open Message consists of version number of bgp, autonomous system number of the originating router, hold time, bgp identifier and optional parameters for capabilities negotiation. A Update Message consists of withdrawn […]

 bgp-fsm bgp-input-events bgp-message-types bgp-stuck-in-active