See this post…
http://forum.mikrotik.com/t/2-9-13-bgp-broken/5279/1
If you extensively use BGP do not bother with 2.9.14 …. Stick to 2.9.12. It’s the last known version with BGP working. That being said, at some point in time MT has to change default settings of keepalive and hold timers to something else than 0. Its not good practice and we use it with different settings. We are still testing an optimum combination for our network but going by the book it seems that keepalive-timer=10
hold-timer=30 seem to work ok..
Due to the large network we have over here (see http://wind.awmn.net ), and with extensive use of BGP and OSPF we are in position to discover bugs in the routing packages in a matter of hours if not much less.
2.9.13 and 14 have a weird problem leaving you with all peers at an “unknown” state when links around start to flap or wireless links on a router are administratively shutdown or they are just shut down from the other side due to errors or maintenance. It looks like the BGP kicks off, calculates shortest paths ok, but when something goes wrong somewhere in the network it falls in a loop or something and it crashes??…
Most of the above are speculations of buggy behavior but the fact remains that the BGP package, even the stable one has hick ups whereas at this point the package can not be called stable at all.
During the update, one of the routers had some warnings on screen after the update and did not reboot at all. It needed a manual switch off/on.
Another one crashed completely… but for that one I have advised it’s admin to post his comments, troubleshooting files and details.
We will be very glad to help (IF we can at any way) and resolve issues as fast as possible…