Currently which one is the best or the “more stable” version of ROS 6.X for a CCR1036-12G-4S, currently running 6.7 but we have had some issues, router became unresponsive one time, other day all interfaces, queues, firewall rules disappeared from winbox and console, we rebooted but the running configuration started to do weird things, so we had to restore from a previous backup … 6.7 sucks on our CCR router.
Sent supout.rif file to Mikrotik support, they suggested to use 6.8RC1 I’m no fan of using RC versions but it looks “ALL” are RC now …
This router has PPPoE, MPLS, OSPF, VPLS, BGP, several Mangle and Firewall rules, Queuetree for customer’s bandwidth shaping, On ROS 6.7 unreliable, we used to have a Dell x86 with the same configuration with ROS 5.xx not a problem ever …
CCR + current ROS 6.x very disappointing so far. May need to go back to old x86 router.
My router is an x86 PC with 6.6, and it’s working fine so far, but it doesn’t use most of the aforementioned features. Previous versions had a few minor issues that affected my setup, and were fixed at that version.
There was a vrf bug in ccr until 6.5, After this has been solved, i have not seen anny problem.
However i dont like to have to much in same Box. It seems like we have almoust the same setup, but i run my pppoe in a standalone 1100Ah2x (Connected directly to the CCR) or a x86 Box (centraliced) Firewall rules i have at a Core router, Connected to the vrf Distributed to the pppoe terminators via MPLS (BGP between CCR(MPLS) and 1100(pppoe)) and dont run to many mangle. Do you have one per pppoe? This can be bad for router. Run one to “all” instead of one each.
Do you have a Clue to whats “unstable”?
I have 10 CCR MPLS routers today, and about 30 1xxx and some CPE 2011 MPLS routers. no problem to Anny of this.
We attempted 6.7 in our cloud cores yesterday and the results were a rolling disaster.
Our core router locked up twice today requiring a power cycle and dns responses were erratic throughout our network.
3000 unhappy customers. Its been a long day. We rolled all the routers back to 6.3 and everything is stable again.
Not a fan of 6.7 in the CCR. Seems ok in the X86 and 400 series boards.
I think I will go play Eve tonight and kill things
The router becomes unresponsive, in the log it shows around 10 times the following error : script error: action timed out - try again, if error continues contact Mikrotik support and send a supout file (13)
That was NOT happening with version 5.xx on the x86
Yesterday I downgraded this CCR to ROS 6.6, because we have another CCR with a similar config running without issues for 60 days.
Do you have some Scheduled scripts running?[/quote]
Yes, a few the ones that send by email auto-backup , export, export compact, a DNS cache cleaner … exactly the same scripts that I have in 20 more routers, exactly the same scripts that have been running for the last 3 yrs. on the ROS 5.xx x86 router without any issues, this CCR is a copy (manually export line by line) of the x86 router … ROS 6.6 seems to have been stable since yesterday … 12hrs up and running without issues so far.
It depends on the platform… What I can tell you is, that on the CCR there is no Version, which is really stable.
We had a lot of issues with flapping ports, Negotiation problems and unresponsive routers. Just yesterday we had a “locked up” CCR1016 again.
+1 we have also experienced a lot of issues on CCR with flapping ports and negotiation, both on copper and fibre. The issues with copper seem to be related to the port running at a speed NOT 1Gbps, it will randomly reset from whatever it has negotiated/been set at to 1Gbps. The only way to fix it is to reboot.
The issues we have had with SFP modules have been working with gear from Lightpointe and Cisco, where the Mikrotik will say the link is UP, but the other end reports it as down.
Saying that, all the CCR1036-8S-2S+ connected via SFP+, and CCR1036-12G-4S running connected via copper, all running RouterOS 6.5 have been completely reliable so far, 81 days uptime.
Basically if you need to connect via copper at non-gigabit speeds, or via fibre with SFP modules, YMMV…
Issues again… Queue tree presented issues … limiting at erroneous values, reboot the router now everything is back OK again… but not acceptable behaviour for our main router, thinking to put our CCR back to the shelf and setup back our old and reliable Dell x86.
It’s a shame…
Mikrotik your CCR + ROS 6.x sucks now, will wait to a reliable version.
CCR collecting dust for now until a reliable ROS version … our good old Dell Poweredge x86 ROS 5.25 back on duty … no more issues no more angry customers …
It’s a shame such a nice piece of hardware not being used …
Our main CCR which is the gateway for our entire network has now been in production for around 1.2 years. We used 6.0 RC6, RC11 and 6.3 only. All were stable. We have 6.7 on our backup CCR and haven’t seen any issues with it… however, it’s hardly used.