Probably this has already been requested but I can’t find the thread.
I think I am not the only one needing BGP flap dampening. It’s required by almost any internet exchanges. Expecially now that we have CCR, I think it would be really useful. Is there any hope to find it in ROS 6.x ?
hello
i would also like to see bgp dampening handling but were do you see any internet exchanges requiring this
dampening is protecting your infrastructure not the others from your BGP announces ?
a+
If your customers flap (which is something quite common, expecially when they change configurations), with dampening active, you avoid to propagate flaps to the peers.
this is a common “miss understanding” coming from the way we all write posts
- initial post was about BGP exchange points
- my answer stated it was about BGP on PEERING POINTS ( exchanging traffic ) as of TOP-IX
- answer trying to demonstrate it is a must have for BGP connectivity
in any case BGP dampening is a “MUST HAVE”
++1
We would also need this feature, especially as the CCR BGP-updates are so slow and frequent flaps are causing continous instabilities…
Totally agree! This is the desired function!
Agreed that it would be useful to have especially when peering in IXes so as not to propagate route flaps to other peers.
+2
+1 we also need this.
+1 This would be very welcome.
Do consider ;
4.0 Recommendation
This Routing Working Group document proposes that with the current implementations of BGP flap damping, the application of flap damping in ISP networks is NOT recommended. The recommendations given in ripe-229 and previous documents [2] are considered obsolete henceforth.
If flap damping is implemented, the ISP operating that network will cause side-effects to their customers and the Internet users of their customers’ content and services as described in the previous sections. These side-effects would quite likely be worse than the impact caused by simply not running flap damping at all.
5.0 Conclusion
With current vendor implementations, BGP flap damping is harmful to the reachability of prefixes across the Internet. We would like to encourage more work to correct some of the issues highlighted by the work of Mao et al [3], to allow the viewing of prefix flap statistics without applying flap damping, and permit more flexible per eBGP neighbour damping configuration features for network operators.
Going to that link shows: “This document is obsoleted by ripe-580.” Following the link to ripe-580:
“In the work by Pelsser et al [3], it is shown that 3% of all prefixes cause 36% of BGP updates, and just 0.01% of the prefixes cause 10% of the BGP updates. The aim is to only penalise those prefixes with excessive numbers of updates.”
“This document uses experimental data gathered from an operational environment to suggest changes to the RFD parameters to suppress the prefixes that flap the most, while minimising the suppression of other prefixes.”
This is a feature that has been requested for several years now. Would it be possible to add a partial implementation which doesn’t allow modifying the parameters - either it is on or off? While not ideal, that would be preferable to not having the option at all, and a step in the direction towards full implementation which might not require too much development work.
Has this already been implemented by any chance? +1 for this feature.