RB2011UiAS-2HnD (ROS 6.17/6.18) crashes often

Hardware MikroTik hardware general
1

Hi everyone,

I’m using a RB2011UiAS-2HnD with ROS 6.18. I’m using it to load-balance between to WANs, which works quite fine if the router does not crash (sometimes every 10 minutes):

aug/06/2014 19:36:32 system,error,critical router was rebooted without proper shutdown by watchdog timer
aug/08/2014 19:02:15 system,error,critical router was rebooted without proper shutdown by watchdog timer
aug/08/2014 19:04:28 system,error,critical router was rebooted without proper shutdown by watchdog timer
aug/08/2014 19:10:48 system,error,critical router was rebooted without proper shutdown by watchdog timer
aug/08/2014 19:16:23 system,error,critical router was rebooted without proper shutdown by watchdog timer

Preinstalled was ROS 6.17 but I updated in the hope this would fix things. Without configuration the router does not crash (and doesn’t have much use). But after anything useful is configured (even only an AP) it crashes. Sometimes it’s working for a day, but often not so much.

It’s not in a hot or special place, power looks ok (no POE).

Any idea?

Regards
Sebastian

2

Another thing: It seems to crash less often if there are no WLAN clients and not much traffic over ethernet.

3

I love how nobodies questions get answered in this forum. I posted a few now…and nothing…

4

What is your problem? Do you know if he got into contact with MikroTik/Routerboard and maybe just got faulty hardware exchanged? Or it was in his config, or an actual bug? Did he contact support to find out?

Or maybe his problem still exists and we’d be happy to provide some help. :slight_smile:

5

I sent the hardware back to the seller, they checked it and said it was fine running their tests. I got it back, set up a simple AP and it crashed after 4 minutes, again and again…

I contacted the seller and requested they replace the hardware, which they did after some weeks. I got the new router one week ago.

So far it’s stable with the exact same configuration if I use 6.15. I won’t make the error again and update to a newer version.