In some cases, we have used holdtimers to wait before setting up the interface, but never before setting down it (if it's down, it's down, there are technologies to fast reroute). But a link is not expected to flap in normal case. If it flaps, it's broken (and we all know it happens).
This being said, if you have a carrier explaining that you should expect only crap from them, you should: - name and shame ; - throw their services away ; because they are clearly playing you for a sucker. About the MX80: it doesn't lack buffer space, it lacks RAM and CPU. > On 16 aug 2018 at 01:01, Jonathan Call <lordsit...@hotmail.com> wrote : > > Anyone have experience with hold timers? > > For the first time in my experience I have a carrier asking me to implement 3 > second hold timers on their interface to deal with their link constantly > flapping. They're citing this document as proof that it needs to be done: > > https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/hold-time-edit-interfaces.html > > I'm extremely dubious of this requirement since I've never had a carrier ask > for this and our router is a pretty old MX80 which does not have a lot of > buffer space. But then again, maybe packet drops due to buffer overflow are > better than carrier transitions and the resulting BGP teardown and rebuild. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
