Hi @ All
we use a RB1200 as BGP Corerouter and noticed, that the board reboot randomly about once a day.
We also contacted MT Support and they pleased us to wait for version 5.5 (but that didn’t help so far)
Yesterday evening I replaced the board with a new RB1200 and today it started to reboot.
Can this be an issue with BGPv6 ???
Best Regards,
Martin
It’s crazy to use 5.x this early as corerouter. We just upgraded one of our
corerouters to 4.17.
Very true, i would expand that to production networks even it makes Normis jump.
tell me the support ticket number and I will investigate why the upgrade didn’t fix your problem
same problem here (we don’t have bgp) it reboots once a day with this msg in logs system rebooted because of kernel failure (even with clear config)
we sold 3 units to customer all 3 have same problem.
5.5 version does not help.
Hello agaon, the ticket number was #2011061266000288, can I downgrade the board to 4,17 until you have fixed this problem ?
Best Regards,
Martin (mySYS Telekom)
i guess you cann’t, see this Mr. Janisk posted.
http://forum.mikrotik.com/t/rb1200-downgrade-to-4-17-issue/48190/1
NO you cannot!
RB 1200 is not supported by ROS 4.17.
Trying to downgrade will effectively brick the Router, and
you will have to netinstall it again with ROS 5.5
There is a thread somewhere in the General section where someone tried to do that and failed.
Does this problem resolved?
it crashes every 2-4 hour - after I changed my RB493 ин 1200
Same problem here RB1200 reboots randomly, ticket number [Ticket#2011071266000188].
Need to mention that after 2 days of working another RB1200 died. Just died, i’ve opened it up and the power addapter is fine, the LED is on untill plugging into board, then goes off…
not very happy with the new kit…
Have this problem solved?
I have bought 4 devices
And I am to change my 493 by 1200 - but I cant do this due it reboots
I have the same problem with two RB1200 routers - I temporally substituted them with RB493G with the same 5.5 firmware and problem has been gone. So my guess is that the problem is in particular RB1200 hardware or 2.33 firmware that runs the router.
BTW - one of the routers was used to connect branch office with central through an IPSec tunnel where is quite active crypted traffic and this one was crashing each 30sec!!! Second router just once a day.
One interesting thing that I found was that after a crash I can see in winbox - system\routerboard field “current firmware” is empty!! and deeper in settings - CPU frequency was 666Mhz (lowest possible)..
MikroTik gave me RouterOS v.5.6, but there were no change in crashing - still the same timings between crashes.
one more update - I moved one RB1200 to the test location and without hi workload through it (there are just one client that goes through IPSec and browse web directly), there are no more crashes within 2 days. So I would say that frequency of crashes are dependent on the load.
We have the same situation here, six RB1200 running as PPPoE ACs - 5 of them reboots randomly each 1-2 days, sometimes even few times a day. One was running constantly for 13 days and rebooted today, load (cpu / bandwidth) was comparable on each one of them.
Two other RB1200 that are running as plain routers with some bgp/ospf and bandwidth utilization about 10-20 Mbps (CPU 2-5%) are running normally - 4 weeks of constant uptime…
As we’re dealing with this problem for some time we’ve ruled out some possible causes. First was overheating - as our RB are placed in rack without any gaps between them, and that the top one was running stable for 13 days, but graphing of temperature sensor showed that there were no anomalies before reboot.
Second suspicion was about proper grounding of board, but this also hadn’t helped.
Now we’re running out of ideas…
Could anyone from MikroTik can tell whats happening with these routers and how to fix that?
if it helps, I logged the serial port output and in the crash form there looks like this:
MikroTik Login: Oops: Exception in kernel mode, sig: 5 [#1]
RB1200
last sysfs file: /sys/devices/plb.0/opb.3/gpio-leds.6/leds/user-led/max_brightness
NIP: a90be8d8 LR: a90be8bc CTR: 8000dae8
REGS: 9fff3de0 TRAP: 0700 Tainted: P (2.6.35-440)
MSR: 00029000 <EE,ME,CE> CR: 44b50928 XER: 20000000
TASK = 80300300[0] ‘swapper’ THREAD: 80318000
GPR00: 806fed22 9fff3e90 80300300 9f8a0240 efe0e03b 00000000 1e26927a 00000250
GPR08: 00000001 00000001 efe0a000 0000003c 1e269000 bfbffea9 03712f90 00002000
GPR16: a90bf5c8 8032688c 80294438 9fff3ea4 80300000 00000000 9fff3ea0 9e29b348
GPR24: 9f012890 9fff3ea8 9fff3e9c 9fff3eb8 9fff3e98 9f012840 00000000 00000214
NIP [a90be8d8] 0xa90be8d8
LR [a90be8bc] 0xa90be8bc
Call Trace:
[9fff3e90] [a90be9b4] 0xa90be9b4 (unreliable)
[9fff3f00] [a90bf594] crypto4xx_pd_done+0x358/0x498 [crypto4xx]
[9fff3f30] [a90bf64c] crypto4xx_pd_done+0x410/0x498 [crypto4xx]
[9fff3f50] [8003ec68] run_timer_softirq+0xf8/0x1dc
[9fff3fb0] [80038ad0] __do_softirq+0xb8/0x134
[9fff3ff0] [8000de38] call_do_softirq+0x14/0x24
[80319e80] [80003b7c] do_softirq+0x74/0x80
[80319ea0] [80038c14] irq_exit+0x60/0x70
[80319eb0] [8000aac0] timer_interrupt+0xf8/0x118
[80319ed0] [8000eab4] ret_from_except+0x0/0x18
— Exception: 901 at ppc44x_idle+0x10/0x20
LR = cpu_idle+0x84/0xd4
[80319f90] [800075ac] cpu_idle+0xd0/0xd4 (unreliable)
[80319fb0] [800019d8] rest_init+0x64/0x74
[80319fc0] [802d972c] start_kernel+0x2a4/0x2b8
[80319ff0] [80000060] _start+0x60/0x9c
Instruction dump:
419e0014 39000001 39200000 7c0903a6 4e800421 80010028 2f800000 419e00fc
80170000 70090002 418200f4 39200001 <0f090000> 418200f8 3ae00000 409efef0
Kernel panic - not syncing: Fatal exception in interrupt
5.6 version doesn’t change anything
Any news, somebody from Mikrotik can tell something - such faulty equipment makes really bad reputation to your new flagship called RB1200 
What can we do more, change power supply, install extra cooling on cpu?
Hello,
we have the same problem.
We tried to upgrade to v.5.7 but the result is the same.
What can we do?
Thank you very much.
have you checked firmware upgrades?
/sys routerb print
Random reboot I have the same problem with version 5.7 with a patch that MikroTik current-firmware: 2.36.1 with the same problem.