11-16-2006 06:12 PM - edited 03-05-2019 12:52 PM
11-16-2006 06:45 PM
There could be a number of reasons for this. The following document details those reasons quite well:
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080093fb8.shtml
Paresh
PS. Pls do remember to rate posts
11-16-2006 07:59 PM
Paresh
You have provided an interesting link about problems with BGP neighbor relationships. But the original post asked about "neighbor stuck in active" and that is not a concept that I recognize in BGP. The only protocol I know that has neighbor stuck in active is EIGRP.
In EIGRP stuck in active means that some router has lost a route and has transitioned to the active state for that prefix. The router has sent query requests for routes to that prefix and some neighbor has failed to respond within a time limit imposed by EIGRP.
HTH
Rick
11-16-2006 08:17 PM
Hi Rick,
I don't believe the original poster was referring to the Stuck-in-Active (SIA) condition which manifests itself in EIGRP. I took that to mean that a BGP neighbor was staying in a BGP Active state...
But we probably need the original poster to clarify :-)
Thanks anyway,
Paresh
11-17-2006 02:57 AM
Paresh
I quite agree that the original question was not entirely clear and that we need the original poster to clarify.
HTH
Rick
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: