After almost a month of troubleshooting with Mikrotik, our 2004’s have been RMAd. I would strongly encourage all of you with 2004s that are rebooting, freezing, etc to open support tickets with Mikrotik. They need data to solve this problem and the more data, hopefully the faster it can be solved.
I opened a ticket with Mikrotik and sent a support file and have not heard back. Did they require that you upgrade to the beta before RMA?
We did not go to ROS 7 beta but we did run a couple different version 6 betas as part of the test prior to RMA.
Experienced our second crash in one week today. No autosupout.rif was generated, sent manual supout.rif to support@mikrotik.com.
Hi,
Right now we have one 2004 not reachable by winbox, but routing works. It runt 6.48beta48.
The same box dropped ospf last time it had issues.
Previously is rebooted when it had issues and I think that was actually better.
We swapped this with another 2004 so its either a general hardware issue or a software isssue.
Did any of you get improvements after swapping for RMAd boxes as this might have been an issue with early production?
/Mikael
Hi!
Did anyone here get any more updates from MT on this? We are seeing processor hangs in the beta and reboots in stable still. We have a lot of 2004s waiting to go to production, so its frustrating 
/M
Nothing with us. RMA’d two of ours and bought CCR 1036s to go in their place. My gut tells me it’s going to be a while.
We have been having similar issues, our previous 2004 just rebooted randomly, we also had problems with PPPoE accounts connecting showing Dynamic but not Running, we then replaced it and it went well for about two weeks. We just had the same issue with the PPPoE accounts again and had to do a reboot to get it working.
Reading this topic, i am on hold, before buying… I need 6 of them
We were told the new beta solved the issue, but we did some fast testing and the whole router behaves strange and becomes unreachable even with mac telnet and romon when OSPF is running.
So test very carefully…
6.47.8 (stable) also includes the fix for the freeze/reboot issue and I can confirm that it installs fine and no issues with OSPF/BGP.
We are now testing it on 3 units starting today.
Same here, we started with two units (doing OSPF and BGP).
regards,
Glueck
We have rolled out on a couple too.
I did see this in the release that someone seems to have experienced a reboot even with the new software.
I got the feeling also that BGP convergece with full tables was much slower, but dident time it. Ill try to get some time in the lab to reproduce if possible.
/M
I need to upgrade the CCR2004 in my lab and see if the stability improves. We’ve used them for several clients but have also had some stability issues.
I think this router will be amazing after a few more months of bug fixes from MikroTik. This is pretty typical of a new router release…it takes a little while to get stable.
4 months since the issue started - so im hoping the “amazing” starts now
So far its been stable for us since upgrade.
/M
I have two 2004s (and a few spares on the shelf), which are neighbors to each other in a small (mid 20s) mpls network, not a lot of throughput, not a lot of firewall rules(typical usage ~1%). Started with 6.47, tried 6.47.7 (which was better) but every so often they would just reboot. And typically within 12 hours of each other. I cant have them doing that, so Ive also ordered a few 1036s as well, and some should be here tomorrow. I also hadnt previously seen when I chose them, the limitations with using rj01 sfps (close proximity and power issues within sfp chassis).
Before the one rebooted this morning, I had logged into it ( I had made a few changes just prior) and saw that overall cpu utilization had jumped to 25% (one of the cores was maxed). It did finally crash and reboot, which seemed to take about 5 minutes for it to come back. Quite honestly I thought I was going to have to netinstall. Before it crashed, I tried to get a support file, but it crashed before it could complete. I had sent in autosup files into them, and they suggested newer versions for debug reasons. Chalk it up to experience I guess, and hang on to them until they become a better work horse.
Hi this seems to have been fixed in latest stable - 6.47.8
Hi,
Our CCR2004 has rebooted without proper shutdown during night with 6.47.8. Not fixed yet. It’s not a power problem because this device is in a rack with dual power circuit.
Reboot happens after 3.8 days of running time the 04 December
Thanks for the update, but with the old version it would last up to ~20 some days before it would quit. Sometimes as quick as 8 or so.I do hope they figure it out soon, I have about 10 of these now that will hold paper down, until they are proven again.
Thats what I was afraid of. Were you able to log into it shortly before it rebooted? Or do you keep cpu statistics? If so were they higher than normal before reboot?
Hi this seems to have been fixed in latest stable - 6.47.8
Thats what I was afraid of. Were you able to log into it shortly before it rebooted? Or do you keep cpu statistics? If so were they higher than normal before reboot?
Yes, of course, nothing really special. It’s not related to trafic, because it happens during night when it’s much lower.
