Erik Romijn wrote:
I heard from Arife that we don't do that now, to prevent polluting our dump files with loads of keepalives.
My recollection is that running without keepalives was to remove extra activity caused by underlying network instability for long distance multi-hop peerings. Apart from rrc00 this shouldn't be an issue anyway since all peers are a single hop away. Research has suggested that single-/multi-hop peering and keepalive/no keepalive settings make little difference to collected data (See Alex Tudor's presentation from ripe46: http://www.ripe.net/ripe/meetings/ripe-46/presentations/ripe46-routing-bgp-m...) Given the general level of BGP activity, there should be sufficient Update messages being sent by each peer that the number of additional Keepalive messages needed to keep the session up should be low.
As far as I can see, there is no option to skip keepalives in the dumps, but I was thinking we should be able to write a patch to do so, or ask quagga-users whether someone did something like it already.
So my idea is: - get quagga to stop dumping the keepalives - set all peerings to a hold time of 180
Personally, I'd go for the latter. This would also remove the problems we have with the RRCs peering with Juniper routers which appear not to accept the 0 hold-time but bring the session up anyway (with their standard timings), only to flap the session after they don't receive the keepalives they were expecting. With some full feeds this has resulted in ENORMOUS dump files and very long database insertion times. James