The goal is to hold onto routes in the event of a failure at the remote route servers (hosted over the internet). Id prefer to stay with what I have as this particular network prefers to "fail broken" than to drop routes and use alternate paths... I can hold for 3600(1hour) or 0(infinite). I am not sure if the peer will come up with the remote end being so far different from mine. Guess Ill find out tonight :) Curious difference with RouterOS as ive never seen a limit on this on any other platform. On 2014-08-05 15:39, Mike Everest wrote:

Hi Daniel,

That's a pretty high timeout value - is remote keepalive really that long? Seems like that would only be useful for a very VERY stable peer!

Cheers, Mike.

...

-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Daniel Hoffman Sent: Tuesday, 5 August 2014 2:26 PM To: MikroTik Australia Public List Subject: [MT-AU Public] BGP hold time limitations

Hi All.

Does anyone have a solution/work around to the BGP hold timer for a peer being locked to below 3600.

At the moment I have Juniper/Cisco nodes running a role im trying to put some CCR's in for but I need to run the BGP holdtime more in the 64800 range.

CCR 1016 - v6.18

Any thoughts?

Daniel