-
Notifications
You must be signed in to change notification settings - Fork 40
Description
Hello,
I am trying to scale the OpenBFDD usage to 1400 neighbors/sessions, but I can only go up to 1143.
I was trying to split 700 + 700 but I could not open bfdd-beacon with 2x different ports, for example:
sudo /usr/local/bin/bfdd-beacon --control=127.0.0.1:957
bfdd-control --control=127.0.0.1:957 connect remote 172.16.0.1 local 172.16.0.0
Opened connection from local 172.16.0.0 to remote 172.16.0.1
sudo /usr/local/bin/bfdd-beacon --control=127.0.0.1:959
bfdd-control --control=127.0.0.1:959 connect remote 172.16.0.1 local 172.16.0.0
Error connecting to beacon on 127.0.0.1:959: Connection refused
The error I get after 1143 on the same control port:
changed: [rocky3] => (item=1143)
failed: [rocky3] (item=1144) => {"ansible_loop_var": "item", "changed": true, "cmd": "/home/rocky/.ehgc1053/bfdd-control allow 172.16.8.241\n/home/rocky/.ehgc1053/bfdd-control connect remote 172.16.8.241 local 172.16.8.240\n", "delta": "0:00:00.235220", "end": "2025-10-02 09:09:13.823943", "item": 1144, "msg": "non-zero return code", "rc": 1, "start": "2025-10-02 09:09:13.588723", "stderr": "\nConnection failed. Partial completion may have occurred: \n: Connection reset by peer\nError connecting to beacon on 127.0.0.1:957: Connection refused", "stderr_lines": ["", "Connection failed. Partial completion may have occurred: ", ": Connection reset by peer", "Error connecting to beacon on 127.0.0.1:957: Connection refused"], "stdout": "", "stdout_lines": []}
Please, could you help me on this? Thanks for your time.
Best regards,
Joao.