06-14-2016 10:52 AM - edited 03-05-2019 04:13 AM
Hi Why does one bgp neighbor always remain Active status instead of Idle? Some other bgp neighbors always remain Idle. I think after Active status for a while, it should go into Idle status. Thank you
Solved! Go to Solution.
06-14-2016 12:34 PM
Hi,
Any BGP speaker will try to establish the session to the configured neighbors. When it try to trigger the session, it moves to "ACtive" state and wait till a local timer expires or if it receives a response from the neighbor (does not accept teh TCP request).
If the neighbor is reachable but the port is not reachable (neighbor is not confgured with BGP), it is common to see the neighbor marked as "Idle" most of the time. This is because, the timer is very negligble while it tries to move from Idle to Active to Idel.
But if you have someneighbors unreachable, you might see it stuck in Active state for a long time (depending on local timer).
-Nagendra
06-14-2016 12:34 PM
Hi,
Any BGP speaker will try to establish the session to the configured neighbors. When it try to trigger the session, it moves to "ACtive" state and wait till a local timer expires or if it receives a response from the neighbor (does not accept teh TCP request).
If the neighbor is reachable but the port is not reachable (neighbor is not confgured with BGP), it is common to see the neighbor marked as "Idle" most of the time. This is because, the timer is very negligble while it tries to move from Idle to Active to Idel.
But if you have someneighbors unreachable, you might see it stuck in Active state for a long time (depending on local timer).
-Nagendra
06-14-2016 01:52 PM
You are right. Thank you so much for your explanation.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide