Hey Paul, Kernel failure is NEVER a good sign. It usually implies hardware problem like memory failure or similar. It can also suggest bug caused by 'unexpected datagram corruption', but that has never been confirmed by MT to be a possibility because (I suspect) that if word gets out that you can crash a router using some specially crafted data then.... you know ;) If it's a memory problem, the only way to fix it is netinstall - netinstall includes nvram format, so it will find and mark any bad blocks that have formed and fix the kernel crashes. If it is something else than memory, then the only way to fix it is with a factory repair or replacement unit. In both of those cases, you'll need a spare so I hate to say it but maybe you need to make sure that you have at least one unit on stand-by. That way, you can swap out the misbehaving unit and then work on it in the lab to make sure you are satisfied it is working properly before putting it back to work! One more thing: you say it's been running for 400 days - that is less than 15 months factory warranty period, so check with your supplier (whoever that may be ;) whether it is still under warranty period - if so, you can get the RMA process started so that even if the diagnostics take it past expiry, the reported date will be used for warranty eligibility purposes! Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Paul Julian Sent: Thursday, 4 February 2016 8:47 AM To: public@talk.mikrotik.com.au Subject: [MT-AU Public] CCR Kernel Failures
Hi guys, we have had a number of CCR's in use for quite a while now with no real problems to speak of.
In the last 3 days though we have had two routers reboot out of the blue and report kernel failures, these routers had been up for over 400 days without issue and just rebooted out of the blue at different times.
They were both running 6.22, I have upgraded one to the latest OS version and done a firmware update, I can't touch the other as it's a major router so will have to schedule an update to it, but I Was wondering if anybody else had experienced this fault and conclusively resolved it with updates ?
Regards Paul _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au