Community discussions

 
cabijuan
just joined
Posts: 5
Joined: Mon Mar 12, 2018 12:49 pm

Re: CCR1072 watchdog reboot

Tue Feb 19, 2019 10:31 am

I have 3 CCR 1072 and in all the same thing happens to me, I'm pissed with Mikrotik, it can not be that your top-of-the-line router will pass this to you and do not say anything about it.
 
bradnz
newbie
Posts: 25
Joined: Mon Jan 22, 2018 4:34 am

Re: CCR1072 watchdog reboot

Mon Feb 25, 2019 3:03 am

I've just completed removing any connection tracking from ours. We had some DDoS issues and from what I've read connection tracking can be a big problem in that case. So I've rearranged my firewall rules and adapted things to run in the raw table as much as possible and turned off connection tracking. So far things seem good, but no real test to speak of yet. We really didn't need connection tracking on this router it was just not something I really considered much until the DDoS stuff started.
I have just removed all NAT and Mangle rules, which means that CT is actually not operating on the device at all. its behind a Transparent Fortigate Firewall, so shouldnt be an issue anyway. I have moved NAT and PAT services to a CISCO 3925 router now, and havent yet seen a reboot. I wondered if the CT turned off would have actually just been the answer rather than having to install another router for this purpose of NAT / PAT. A bit annoying. Do you think if I just turned off CT it would have been ok? How have you found things have been since you did this?
 
kos
newbie
Posts: 25
Joined: Mon Oct 31, 2016 11:51 am

Re: CCR1072 watchdog reboot

Mon Feb 25, 2019 10:34 am

Yes, when connection-tracking is disabled the device performs much better.

When I contacted Mikrotik support about device reboots they requested access to device. I provided them a test setup with one CCR1072 to act as traffic-generator and another one acting as DUT. No configuration on DUT, just routing and 4 FW rules to prevent unauthorized access.

After a few weeks of meaningless tests, the answer was - DUT is overloaded, you can't see it but it is.

With 1G?????? That is not even close to your test results published on your web site?????!!!!

- Our tests are performed with connection-tracking disabled!

That's all! You are ******!

I will say it again, CCR1009, RB1100x4 and RB4011 are working as expected in absolutely same test condition in which CCR1072 reboots it self!!!
Last edited by kos on Mon Feb 25, 2019 3:22 pm, edited 1 time in total.
 
cabijuan
just joined
Posts: 5
Joined: Mon Mar 12, 2018 12:49 pm

Re: CCR1072 watchdog reboot

Mon Feb 25, 2019 10:38 am

Another restart this Saturday, is desperate, I have the router at 400km, please Mikrotik say something about it.
 
cdemers
Member Candidate
Member Candidate
Posts: 184
Joined: Sun Feb 26, 2006 3:32 pm
Location: Canada
Contact:

Re: CCR1072 watchdog reboot

Mon Feb 25, 2019 4:28 pm

Email mikrotik support, they don't monitor the user forums for people having problems. Normus and a few others frequent here, but best just to email them with a support ticket and supout file.


Sent from my SM-A520W using Tapatalk

 
cabijuan
just joined
Posts: 5
Joined: Mon Mar 12, 2018 12:49 pm

Re: CCR1072 watchdog reboot

Mon Feb 25, 2019 5:32 pm

I always send it, and the only thing they tell me is update, I already have 5 different versions. It does not help to send it, they have no idea what the restarting does.
 
djdrastic
Member
Member
Posts: 305
Joined: Wed Aug 01, 2012 2:14 pm

Re: CCR1072 watchdog reboot

Wed Mar 27, 2019 11:54 am

Reading this thread as I have to upgrade a 1016 due to lack of SFP+ ports . Has worked 1y without skipping a beat barring the security updates.
Am I better off getting a EdgeRouter Infinity or building a cheap X86 box ?
 
doush
Long time Member
Long time Member
Posts: 616
Joined: Thu Jun 04, 2009 3:11 pm

Re: CCR1072 watchdog reboot

Sat Mar 30, 2019 4:34 pm

Dont upgrade to CCR1072. It is not a stable product to work with.
Frequent reboots etc..
 
whoknew
Member Candidate
Member Candidate
Posts: 145
Joined: Wed Oct 13, 2010 8:51 pm

Re: CCR1072 watchdog reboot

Thu Apr 04, 2019 4:53 pm

SOLVED

We get after a lot of work and trouble solving the problem of CCR1072 no longer restart or freeze.

Solved the problem was relatively easy, after more than 3 months waiting for the mikrotik team to position on the problem, solved.

We traded the CCR1072 for an MX-80 Juniper.
So....you went from a $2,000 USD router to a $35,000 USD router?
A MX80 is not a $35000 router! Where the hell do you buy your gear from ?
Where are you buying them from. Distributor list price all show $19,000+ USD. I have a friend who works for a larger ISP and they can get them for around $6,800 directly from Juniper.
 
wildbill442
Forum Guru
Forum Guru
Posts: 1050
Joined: Wed Dec 08, 2004 7:29 am
Location: Sacramento, CA

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 12:56 am

Hey, guys

After upgrading CCR1072 and CRS317-1G-16+ to version 6.42.2, the kernel crashes have stopped. I hope they have really solved this great problem.

Best Regards,

Vagner Felipe Becker
Unfortunately they are not! Neither in ROS 6.42.2 nor in any other ROS version!!!

CCR1072 is not capable to handle 1Gbps bidirectional IMIX traffic and 25k sessions with conection-tracking enabled, due to watchdog timer reboots!!!

Five to ten times cheaper devices like CCR1009 and RB1100AHx4 are working fine in same test conditions!

The worst thing is that they are continuing selling this faulty device!

Contacting Mikrotik support is a lost of time!
Looks like I'm having a similar issue...

viewtopic.php?f=2&t=152192
William Burnett
Network Engineer
 
Fluke
just joined
Posts: 2
Joined: Wed Aug 02, 2017 1:46 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 6:45 am

Out of curiosity - what is the device temperature? (system health print)

I have a device that runs at ~53C and reboots occasionally, and another one that runs at ~39C and works OK.
 
Jeanluck
Member Candidate
Member Candidate
Posts: 271
Joined: Tue Apr 19, 2011 7:07 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 11:17 am

My CCR1072 works at 37-39
 
cabijuan
just joined
Posts: 5
Joined: Mon Mar 12, 2018 12:49 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 12:00 pm

forget about the temperature, it is a problem in the kernel that mikrotik does not know how to solve, nor does it pay attention to us. Hopefully with the V7 this is solved, it is the only hope I have left. the top-of-the-range router does this happen, it's nonsense
 
User avatar
mac86
Member Candidate
Member Candidate
Posts: 118
Joined: Sat Nov 25, 2006 12:52 am
Location: bahia blanca - argentina
Contact:

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 4:51 pm

We've downgraded CCR1072 to 6.44.5 and no more reboots. :D
http://www.netpro-ar.com
MTINE - MTCWE - MTCRE - MTCTCE - MTCNA
Patagonia Argentina IT Consultant

Mikrotik user from V2.7.7 - Aug/2003
 
Jeanluck
Member Candidate
Member Candidate
Posts: 271
Joined: Tue Apr 19, 2011 7:07 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 6:08 pm

can anyone confirm that version 6.44.5 is stable with the CCR1072?
 
wildbill442
Forum Guru
Forum Guru
Posts: 1050
Joined: Wed Dec 08, 2004 7:29 am
Location: Sacramento, CA

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 6:21 pm

can anyone confirm that version 6.44.5 is stable with the CCR1072?
We’ve just downgraded to latest long term, I’ll update in 48hrs.
William Burnett
Network Engineer
 
Jeanluck
Member Candidate
Member Candidate
Posts: 271
Joined: Tue Apr 19, 2011 7:07 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 6:36 pm

Please let us know how it works in a few days
 
cabijuan
just joined
Posts: 5
Joined: Mon Mar 12, 2018 12:49 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 7:31 pm

I have 6.43.8, and I have reboots.
 
Jeanluck
Member Candidate
Member Candidate
Posts: 271
Joined: Tue Apr 19, 2011 7:07 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 7:57 pm

Thanks, 6.43 discarded then... let's see if there's luck with 6.44.
I have the 6.38.3 and only had one reboot in 3 years
 
User avatar
mac86
Member Candidate
Member Candidate
Posts: 118
Joined: Sat Nov 25, 2006 12:52 am
Location: bahia blanca - argentina
Contact:

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 7:58 pm

can anyone confirm that version 6.44.5 is stable with the CCR1072?

Yes, I can confirm it.
4 weeks without reboots, and going on.....
http://www.netpro-ar.com
MTINE - MTCWE - MTCRE - MTCTCE - MTCNA
Patagonia Argentina IT Consultant

Mikrotik user from V2.7.7 - Aug/2003
 
Jeanluck
Member Candidate
Member Candidate
Posts: 271
Joined: Tue Apr 19, 2011 7:07 pm

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 8:16 pm

What reboot frequency did you have previously?
 
miltont
newbie
Posts: 48
Joined: Wed Nov 11, 2015 3:58 am

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 8:34 pm

Up 60+ Days
You do not have the required permissions to view the files attached to this post.
 
wildbill442
Forum Guru
Forum Guru
Posts: 1050
Joined: Wed Dec 08, 2004 7:29 am
Location: Sacramento, CA

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 10:49 pm

What reboot frequency did you have previously?
One to multiple times in a 24HR window.

Mikrotik support wanted me to turn off watchdog and log error / generate supout.rif once locked. The generated supout.rif files I provided after the watchdog reboot didn't yield any useful information. I opted to netinstall the latest long term release track (6.44.5). We also replaced all the SFP modules as a precaution during the maintenance window.

Mikrotik Support's Recommendation:
Before that, I suggest that you upgrade to the latest "stable" version (if there is an actual bug, then it might be already fixed). For example, v6.45.6 fixes a Watchdog reboot caused by h323 firewall helper. If your router did process voice call traffic, then the issue might be already resolved.

What's new in 6.45.6 (2019-Sep-10 09:06):
*) conntrack - improved system stability when using h323 helper (introduced in v6.45);


These are our edge routers and no NAT is being performed and we don't use h323 internally, but if some malformed h323 packet traversing these routers was causing the reboot then this may have been the cause behind the sporadic reboots. Again I'll post results of the downgrade to the Latest Long Term Release track after ample time has passed. So far ~15hrs and no reboot, this won't be conclusive until we make it past the 24-48hr mark. From what other users above have posted I'm feeling optimistic.
William Burnett
Network Engineer
 
wildbill442
Forum Guru
Forum Guru
Posts: 1050
Joined: Wed Dec 08, 2004 7:29 am
Location: Sacramento, CA

Re: CCR1072 watchdog reboot

Tue Sep 17, 2019 11:34 pm

Here's a sequence of events on how this issue started for us:

It began with a kernel failure on one of our edge routers, I'll call it EDGE A. To fix this we decided to do a netinstall on EDGE A and bring the router up to the latest stable release at the time (6.45.5) due to CVE fixes etc. Prior to the netinstall we were running 6.42.6 on both edge routers and other than the kernel failure on EDGE A we were not experiencing reboots. We also upgraded our other edge router, EDGE B, in the same maintenance window to 6.45.5. The reboots continued after the netinstall on EDGE A only the error changed from "reboot due to kernel failure" to "reboot by watchdog timer". At this time we were under the impression there was a hardware issue with the EDGE A router so we moved the BGP peer and other connections to EDGE B and overnighted new hardware. The reboots then started happening on EDGE B. We opened a ticket with Mikrotik support, but after going through the weekend and into Monday with no response and the routers rebooting sporadically we decided to netinstall the latest longterm release track (6.44.5). Mikrotik support responded after we were done with our downgrade and reaffirmed our suspicion that there was something wrong in software and to upgrade to latest stable release (6.45.6) due to a stability improvement relating to H323 and watchdog reboots. As we did not need any of the "new" features in the Stable Release tree, and receiving this information after downgrading to Long-Term Release tree, I think we're going to stay here unless the issue persists.

Again I won't know definitively if this was the root cause until ample time has passed, so I'll update after we get passed that 48hr mark.
William Burnett
Network Engineer

Who is online

Users browsing this forum: No registered users and 11 guests