This isn't the problem we recently encountered. One of our upstream providers went down. The local interface between them and us never dropped. We believe because the initial BGP Session was setup at "0" Hold Time and "0" Keep Alive Time this upstream never stopped announcing our routes even though their routers knew the circuit was offline.It is not the hold time. I noticed mikrotik waiting / connecting / trying to connect to the upstreme router even though the link/router were down. ONce we disabled the interface it showed up "not connected" and announced to the other upstreme. I agree with you that the bgp is limited. Somebody has to get in and disable an interface or remove the rule so that announces are done to the other upstreme.
I think it should be easy to write a script for this if someone can come up with this it would atleast fulfil the failover issue.
OpenBGPD on OpenBSD is also good (atleast it was for our tests).Although your waiting for 2.9 there will/ may be a lot of bugs in it when it is released. Maybe not good immidiately for production use. I dont know whether this is a possibility but I guess we can run a machine with zebra behind MT and have MT learn its routes from the zebra box. The zebra box can be configured to do ONLY bgp with your upstremes . Zebra is more configurable right ?
no such command or directory (hold-timer)routing bgp
hold-timer - if nothing is received from peer for this amount of
time, then router considers peer dead and closes the conection.
keepalive-timer - interval between keepalive messages sent to
Command "/routing bgp peer add" adds a new bgp peer. Try /routing bgp peer set 0 hold-timer=90/routing bgp peer add hold-timer=90 sent my system to 100 cpu load a nd added a 0.0.0.0 peer which is not getting removed
I believe you want an option sometimes referred to as "weighing" AS Numbers. With this option you can announce ASN information in a way that will favor one backhaul over another. For example let's say you have an AT&T (7018 ASN) backhaul and a Sprint (1239 ASN) backhaul coming into your MikroTik (9999 ASN), but you would prefer more traffic come into your network over the AT&T backhaul.Is there now a way to mark certain traffic so we advertise it to take a particular peer as path ? (More control over incoming?)