Thanks Bernd, really good advice, I will try. -----Original Message----- From: Bernd Naumann <be...@kr217.de> Sent: Friday, February 10, 2023 3:34 PM To: LIU Chris <chris-zq....@urbanandmainlines.com>; bird-users@network.cz Subject: Re: Bird bfd configuration
[You don't often get email from be...@kr217.de. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On 10.02.23 16:58, LIU Chris via Bird-users wrote: > Anyone comment this issue ? Hey Chris, I can not say much on your case, just general "advise"/recommendations... first: I have not encountered a case where I needed to "tune" or explicit set BFD settings/parameter. Just enable BFD on the protocol, and on the BFD protocol the interfaces. (To start with. On high latency links of course there is a need, but on local? Keep it simple and use defaults till you encounter issues...) second: No need to set neighbor and local (as far as I'm aware of). Like with the other point; just set the interface on the bfd protocol. I don't know the specific implementations details, but source address selection and stuff are just set "correct" and bird "is clever enough" to sort out the rest. (which is btw a big prop to the core team that this "just works"(tm)!!) I.e. on protocol ospf, enable bdf and on the proto bfd set the same interfaces. You just get bfd awareness on ospf for each neighbor. No need to configure any neighbors. Maybe this somehow helps you... Bernd Thales is in the process of carving out its Transportation activity (GTS) from other Thales’ activities. In order to prepare this internal restructuring, a new e-mail address has been adopted and your GTS contacts now use urbanandmainlines.com. Please note that their Thales e-mail address remains also valid.
