<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Hi,<br></div><div dir="ltr"><div>I have the following configuration on one of my servers ("10.1.0.1"):<br><br><i>protocol bfd {<br> interface "eth0" {<br> min rx interval 200 ms;<br> min tx interval 1000 ms;<br> idle tx interval 1 s;<br> multiplier 5;<br> };<br><br> neighbor 10.1.0.2;<br> neighbor 10.1.0.3;<br> neighbor 10.1.0.4;<br> </i><b> ..... (here about 1000 records)</b><br><i> neighbor 10.1.3.251;</i><br><i> neighbor 10.1.3.252;</i><br><i> neighbor 10.1.3.253;</i><br><i> neighbor 10.1.3.254;</i><br><i>}</i><br><br><br>And I configured the second server ("10.1.0.2") as a neighbor with the following config:<br><br><i>protocol bfd {<br> interface "eth0" {<br> min rx interval 200 ms;<br> min tx interval 1000 ms;<br> idle tx interval 1 s;<br> multiplier 5;<br> };<br><br> neighbor 10.1.0.1;<br>}</i><br><br>For some reason I have random session expire events on the second server and BFD sessions get UP -> DOWN, DOWN -> UP events.<br><i>bird: bfd1: Session to 10.1.0.1 expired<br>bird: bfd1: Session to 10.1.0.1 changed state from Init to Down<br>bird: bfd1: Session to 10.1.0.1 changed state from Down to Init<br>bird: bfd1: Session to 10.1.0.1 expired<br>bird: bfd1: Session to 10.1.0.1 changed state from Init to Down<br>bird: bfd1: Session to 10.1.0.1 changed state from Down to Init</i><br><br><br>This happens only if I specify a lot of neighbors in the config. For example the following config on first server ("10.1.0.1") works fine:<br><br><i>protocol bfd {<br> interface "eth0" {<br> min rx interval 200 ms;<br> min tx interval 1000 ms;<br> idle tx interval 1 s;<br> multiplier 5;<br> };<br><br> neighbor 10.1.0.2;<br> neighbor 10.1.0.3;<br>}</i><br><br>Looks like all BFD sessions are handled on a single thread. Could someone, please, confirm that BIRD isn't designed to handle a huge amount of BFD sessions simultaneously? Or possibly I can enable some options to handle this case in my env? <br></div></div>
</div></div>