Hello,
Recently we have began receiving CCR2004-1G-12S+ with V7 pre-installed. This is a problem due to the many changes, incompatibilities, and entirely removed functions in V7.
Is there any known way to downgrade these to V6.xx? I reached out to Mikrotik support and their answer was a broken record “This device is only supported on V7” which I know is bullshit because I have over 100 deployed that shipped with V6.47 and V6.48 on them.
We are not deploying V7 any time soon and this will force us to stop purchasing MT all together as we cannot ensure continuity when MT disregards wishes in this way. Sounds like much larger company also starting with the letter M… forcing people to use some version 11 of their product and ignoring their customers.
People told me not to use MT and I thought they were wrong, but this may have just been a very expensive lesson.
I appreciate your reply but unfortunately it doesn’t appear to be helpful.
I have been doing this a very long time and searched before I posted.
Please note this is a CCR2004-1G-12S+, not a CCR2004-16G. Am well aware V6 is not supported on the CCR2004-16G.
I am also aware that you can downgrade back to V6 from a device that you upgraded to V7, via netinstall.
I have about 40 CCR2004-1G-12S+ in my warehouse that shipped with v7.1.1 installed on them. (I also have >100 deployed with v6.48) I need to be able to downgrade these to v6.47/48/49
Otherwise they’re going to have to be returned and that will be last purchase of Mikrotik routers my company ever makes.
Which is very sad because their price for performance can’t be beat, but I can’t build a business on someone changing the rug under my feet.
You can’t downgrade to lower versions than the factory installed ones.
BTW; What kind of company policy is that… V7 is coming to you in one way or another, not to mention other vendors who do exactly the same…
We will certainly upgrade to V7 at some point (if we are not forced to move away from MT before), but not until our team has the knowledge and tools to work with it, and not before it’s no longer broken and missing functions.
Right now V7 still has many bugs and missing major functionality such as (top of my head…not meant to be an exhaustive list. I am really not too excited to discover how many undocumented features or lack thereof exist):
BGP max-prefix-limit (according to mikrotik, this is currently classified as wontfix as they don’t understand the need for it)
View BGP advertisements to a specific peer (practically exists in every routing platform on this planet except RouterOS V7). The workaround is apparently to capture the BGP packets into a PCAP file and then view the capture? (https://wiki.mikrotik.com/wiki/Manual:BGP_HowTo_%26_FAQ#Question:_How_to_seen_routes_advertised_to.2C_and_routes_received_from_a_particular_peer.3F ) does not work in V7
Just go look at the release postings for all the things “fixed” from 1 “stable” version to another. Until V7 reaches a point of maturity, we as a company won’t be moving to it. And since it’s now being forced on us, we will now look for another solution that is a bit more considerate if we cannot resolve.
BGP max prefix is a will fixit. There was a riot on the forum and they listened. Sometime in an upcoming release. The other one is a big guess but via cli “routing route …” But nevertheless, I understand the pain.
Found it http://forum.mikrotik.com/t/ros-7-1-bgp-max-prefix-limit-missing/155371/1
Thank you for providing the direct link. I am aware that is the official line, however, here is an example of a device that had 6.47.10 from the factory but is running 6.44.6.
Now I’m also aware this was a downgrade from 6.x to 6.x, and that a downgrade from 7.x to 6.x may not be possible. But I’m asking Mikrotik and the public in general before I give up hope. Because it doesn’t make sense that they would change functionality mid-production. Generally you can expect a given device/model to always perform the same. I would not expect a Cisco or Juniper device with the same model number to have different features based on when it was made. So for a CCR2004-1G-12S+2XS to have different features based on when it was made just doesn’t seem like something that should be true.
The problem is that we already use CCR2004 with v6, the v7 it’s not stable enoght to put in a datacenter, or to handle critical applications, so believe that we can trust on a release that crashs a lot using the same features that we already used on v6 it’s not possible.