Re: BFD on back-to-back connected BGP-speakers

2016-11-29 Thread Saku Ytti
On 29 November 2016 at 20:23, Hugo Slabbert wrote: Hey, > - eBGP with peering to interface addresses (not loopback) > - no multi-hop > - direct back-to-back connections (no intermediate devices except patch > panels) > > Possible failure scenarios where I could see this helping would be fat > fi

Re: BFD on back-to-back connected BGP-speakers

2016-11-29 Thread Ryan L
Hugo, I think those are all valid potential reasons to use BFD. I use it for some of the same reasons even on direct connect peers. Only time I ever recall actively avoiding it if I had the capability was if I had NSF/SSO, since they didn't used to (still don't?) play very well together. On Tue,

Re: BFD on back-to-back connected BGP-speakers

2016-11-29 Thread jim deleskie
Hugo, I've used this configuration in a past line when I may of had multiple L2 steps between L3 devices. The only concern we had was around load BFD put on _some_ endpoint routers, if was handles on the RouteProcessor vs on line cards. -jim On Tue, Nov 29, 2016 at 2:23 PM, Hugo Slabbert wr

BFD on back-to-back connected BGP-speakers

2016-11-29 Thread Hugo Slabbert
Good morning, nanog, Is there any/sufficient benefit in adding BFD onto BGP sessions between directly-connected routers? If we have intermediate L2 devices such that we can't reliably detect link failures BFD can help us quickly detect peers going away even when link remains up, but what about