-----Original Message----- From: Raymond Burkholder [mailto:[email protected]] Sent: Wednesday, August 16, 2017 5:05 PM To: Vivek Srivastava V Cc: [email protected] Subject: Re: [ovs-discuss] BFD with 'option : remote_ip = flow'
> On 16 Aug 2017, at 07:54, Vivek Srivastava V > <[email protected]> wrote: > > No. I hadn't heard of multi-hop BFD before, so I looked around a bit and > found RFC 5883. That RFC, though, doesn't really provide a specification for > how to do this. Is there a detailed specification somewhere else? > > [Viveks] Unfortunately I also couldn't find any implementation > specific details about multihop BFD, other than RFC 5883 and some > configuration related info available on the net. What I could gather > is that it is mostly same as onehop BFD, with some additional > considerations- Out of curiosity, would you be able to explain what your use case is? I gather you don’t have a BFD partner on the ‘other end’ of the layer 2 link? And that you are going across some sort of layer 3 network? And if that is a multi-hop l3 network, don’t things get a bit dicey in terms of time-outs, possible changes in packet flows, etc? [Viveks] the use case is to monitor availability of DCGWs from computes in a DC with L3 fabric. There will be multiple (but limited) l3 hops in between. I believe BFD is still applicable in this scenario and it should be okay with possible change in packet flows/paths. Time-outs/false failure detections can be avoided with appropriate/tuned monitoring intervals. Do you see any other issues in this scenario? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
