Thanks for the reply. I have been able to reproduce this on kvm too.
This is the output from running in debug mode. Highlighted part is where
we stop seeing RX's. I've added some additional debugs in the io loop
and running a simultaneous packet capture. I'll report back when I have
more.
Jun 13
-alives coming in from .11, but the bird instance
responds with hold timer expired. This was about after 12 hours in
established state.
Connection opens right back up again.
I don't see the same issue on upping the timers to 3/9 seconds.
Anyone see anything like this before?
Thanks,
Sa
bird using a lot of CPU:
2205 root 20 06924780560 R 26.2 0.0 0:06.14 bird6
Since my configuration will never make use of these entries, is there a way
to disable this scanning behaviour in bird?
Thanks!
--
Saksham Manchanda