Hey, We offer it when customers request it, though demand for it is pretty low. We also use it on multi-homed managed CEs.
Just make sure that your platforms ( some can offload it ) and links can handle the amount of sessions and timers you're using. Depending on your use case and link speed, you may want to set up a bandwidth reservation for BFD packets, or even put them inside a LLQ . Remember that unless business requirements call for super-fast convergence, making a network notice and react to failures as fast as possible isn't the best of ideas. Some IGP/BGP timers might be a bit on the high side, but just because you're deploying BFD, it doesn't mean you have to be really aggressive with the timers. Looking at IP event dampening of BFD dampening ( if your gear supports it ) might also prove useful. My thoughts and words are my own. Kind Regards, Spyros -----Original Message----- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Eric Louie Sent: Thursday, October 6, 2016 12:48 AM To: CiscoNSP <cisco-nsp@puck.nether.net> Subject: [c-nsp] BFD on customer-facing interfaces - experiences We're looking for any ISPs who have experience with BFD configured on customer-facing interfaces (OSPF or BGP). Was it reliable? Did it cause too many false positives for down routing sessions? What about re-establishing the routing protocol when BGD recovers? Did you have issue with root cause analysis when the sessions dropped (as in explaining to the customers why their routing session went down or flapped)? thanks, Eric _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ This e-mail and any attachment(s) contained within are confidential and are intended only for the use of the individual to whom they are addressed. The information contained in this communication may be privileged, or exempt from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and delete the communication without retaining any copies. Connecticore SA is not responsible for, nor endorses, any opinion, recommendation, conclusion, solicitation, offer or agreement or any information contained in this communication. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
