<<<If A is flapping THAT much, time to get another provider, or another local loop. If it <<<only flaps occasionally, not a big deal, the routers will handle it.
It isn’t so much that one of our links are flapping all of the time, but in our enterprise we have over 1000 locations, which can be 10 or 15 circuits flapping at one given time. This is more for management/administration reasons, other than just wheather or not the router can with stand the torture. Each location is its own AS, and we are running EBGP between all of our ASs, internally inside our global AS, if that makes sense. If it were just a couple of cirucits dying on us, that would be fine, but we are trying to come up with some sort of dynamic solution so if our primary circuit is flapping, we won’t be flopping back in forth, from our primary to our secondary, from BGP routes, to default route, and vice-versa, keeping our network stable .
<<<That said, I would not use flap dampening for this.
If you don’t recommend BGP dampening to fix our problem, what else is there, that I have not found or thought of yet. Is there a true dynamic solution to our problem?
<<<yes, you can do what you want with flap dampening. Your router will penalize the <<<announcements from A for every time it flaps, and will wait until it has stopped <<<flapping for a user definable time before sending packets to A again.
So you could still use dampening successfully, even though the bgp session keeps resetting. Does your peering session have to remain stable, with you just dampening some routes, or can your session keep bouncing, and it will still know to store these routes in either their history state, or dampening state?