I am having one issue, having one ccr1036 and version 6.49.7 and want to change it to 2116, but on 2116 minimum is 7.2
What is recommendation in this situation, because i can't do export-import because of syntax.
Is it way to put 6.49.7 and then update it or should i just update to 7.2 and then export it. From routing point of view, i have bgp,ospf

upgrade CCR 1036 to 7.2 and export

Do not use old 7.2, on new version have fixed some bad impor from previous version and almost correctly convert bgp and filters.
Use 7.7.

But do not expect trouble-less experience on migration.

My CCR2116-12G-4S+ (with 2 BGP 2G + 2G) where I'm forrced to use v7.7 still up and do not crash for months (94d 01:40:53)

Do not use old 7.2, on new version have fixed some bad impor from previous version and almost correctly convert bgp and filters.
Use 7.7.

But do not expect trouble-less experience on migration.

My CCR2116-12G-4S+ (with 2 BGP 2G + 2G) where I'm forrced to use v7.7 still up and do not crash for months (94d 01:40:53)

i tried first time, bgp had some problems. Looking into what happening.
ccr1036 is on latest stable version. I tried to get it on 7.2 and export -import to ccr2116 but with huge problems, first names of interfaces, why dtarts from 13, not from 1? Even if I change it and then import .backup it revert it to ether13-ether25 and all interfaces are unknown (cause ofc from backup is 1-12, not 13-25).

Please try to avoid using old versions for new installations. Upgrade your new router to the latest stable (at the moment 7.8 ) and your old router to the same version. Then transfer configuration. Of course, first, read this article:


https://help.mikrotik.com/docs/display/ ... ding+to+v7

Also remember, that router converts configuration from v6 to v7 only once. So you can not upgrade, downgrade, change configuration, and then upgrade again.

Please try to avoid using old versions for new installations. [...]

Please stop rolling out OLDER MODELS, which WORK PERFECTLY with 6.48.6+, forcing us to use v7 from the factory.

It is a cursed arrogance that denotes carelessness and a frightening indifference towards historical customers,
who do not want to use the v7 in production IN THE OLD MODELS.

Please give us a way to continue using v6 on models THAT ALREADY SUPPORT IT.
Of course I'm NOT talking about new models not compatible with v6.

Routers are made of hardware, if new chips, for example, NAND, are used in order to manufacture routers, then the minimal supported RouterOS version must be bumped up since support for that chip can be added only in the latest releases. MikroTik has never bumped up the minimal supported RouterOS version just like that - that has been always done due to hardware parts used for manufacturing. In any other case, we do increase the installed version, not the minimal supported one.

Routers are made of hardware, if new chips, [....]

I understand that, no problem... but...
For example, new RB4011 come with preinstalled v7, and on the past are on v6.
Call that model in another way, don't leave the same name, or whoever buys it has a big rip-off when it arrives.

have you compared the 4011 v6 and v7 boards side by side?

have you compared the 4011 v6 and v7 boards side by side?

When you buy something from the distributor, the distributor do not give a component list contained inside the board.
I see only a code: RB4011iGS+RM
No indication if is with v6 or forced v7, or if is logically needed for components change the v7.

I repeat: I understand, no problem, I'm not silly...
The problem is that from the same official name I expect the same product.
If there is an r2/r3/r4 etc. in the serial number, I can't see it from the product name...
And I don't even see that I'm forced to use v7...

More correct is call it something like RB4011iGS-r3v7+RM

I write this with an open heart...
The truth is that I'm afraid of what could happen in production with v7 given the constant problems I read.
Replacing a version that's been stable for years with another that's a leap in the dark is a big risk for me.
Currently I admit that with v7.7 I'm getting along well with the CCR2116-12G-4S+,
but starting to use the wireless part and starting to have problems with customers is not a good prospect.
With this job, I support my family and the families of the employees.
If for some reason problems on the new v7 version start to discredit me, of course that is unacceptable.

I would prefer to gradually switch to v7 after various tests, not be forced to switch because on the same machines as before (***) I can't put v6.

i now buy a new route r2116 and cant put it new version, its just a hard work to do it. I will try to manually upgrade it to v7 like you propose.

i now buy a new route r2116 and cant put it new version, its just a hard work to do it. I will try to manually upgrade it to v7 like you propose.

If I had to migrate from CCR1036 v6.48.6 to CCR2112 v7.7 (I would not choose other versions)

1) I would take another CCR1036 which I already would have as a spare.
2) I would configure it with v6.48.6 identical to the one I have to replace (so I would also have an immediate backup)
3) I would upgrade from 6.48.6 to 7.7
4) I would export the configuration with show sensitive (no backup)
5) I would netinstall CCR2112 with 7.7
6) using the export generated by CCR1036 updated to 7.7 I would configure CCR2112 section by section.
7) I would test the device by placing it in an unimportant part in production, with a backup rig already ready.
After a month of testing, I would replace the CCR1036.

i now buy a new route r2116 and cant put it new version, its just a hard work to do it. I will try to manually upgrade it to v7 like you propose.

why on earth when try to restore from 1036 (v7. to 2116 same version, on 2116 number of interfaces went from 13-25 omg

why on earth when try to restore from 1036 (v7.8) to 2116 same version, on 2116 number of interfaces went from 13-25 omg

Because obviously, like all other peripherals, backup is for restore to same machine, same version.

In your case ether1 etc. are already assigned to the previous MAC addresses.

Using the backup of any other machine as a starting point only causes problems,
now that you load the wrong backup, you should netinstall v7.7 for avoid any problem.

(7.8 is less stable, but don't you read the forum?)

we didn't figure it out. How knows why.

looks like after a little more than a year the time to mandatorily go to V7.X has come, is not pretty but It is what we have

Routers are made of hardware, if new chips, for example, NAND, are used in order to manufacture routers, then the minimal supported RouterOS version must be bumped up since support for that chip can be added only in the latest releases. MikroTik has never bumped up the minimal supported RouterOS version just like that - that has been always done due to hardware parts used for manufacturing. In any other case, we do increase the installed version, not the minimal supported one.

Thank you for clarifing that so I will avoid MikroTik hardware on my next big project (~100xRB4011). I know you don't care, but I have to mention it.

v7 is not production ready for my needs, so if you force v7 even on older hardware, then... this is the end of an era for me.
I have to look for other vendors. I am tired of waiting v7 to be on par with v6. You don't seem to listen to your core user base of almost 20 years... you abused our trust enough with v7 the last decade, so you lose us... enough is enough

have you compared the 4011 v6 and v7 boards side by side?

Yeah, that's lovely you have internal revisions of HW like v6 or v7... but why it's not on the box or sticker or in product name?!

Really, this is pretty stupid... at least add a letter to a product number or somewhere on the sticker that says it's a new revision.
I wanted to replace dead router, but guess what, product I bought with exact same product number is actually completely incompatible and can't be used without major configuration rework. GREAT! Back to dealer it goes...
Currently it's "Russian roulette" trying to buy new HW to replace old one just to find it will not run old ROS at all and can't be easily used as replacement.
Especially with state of v7 as it is now, it's not even feature-comparable to 6.x. I understand some components might be hard to get or have to be replaced, that's all fine
but PLEASE make sure we at least KNOW what we are getting when ordering new HW. Is this too hard to understand?

i bought new one 2116 for replacement of old one hw, but i encounter many errors even when i update old one to v7 and export it to new.
So, waste of money.

i bought new one 2116 for replacement of old one hw, but i encounter many errors even when i update old one to v7 and export it to new.
So, waste of money.

Want to have it fixed...give us a try to help you.
That means:

• what errors?
• what does your config look like? (you might want to share your config with us?)

Exporting and importing to another device can lead to errors...the hardware is not the same. Before importing you have to check the config manually.

v7 is not production ready for my needs, so if you force v7 even on older hardware, then... this is the end of an era for me.

May I ask why? Just curious what you are missing.

v7 is not production ready for my needs, so if you force v7 even on older hardware, then... this is the end of an era for me.

May I ask why? Just curious what you are missing.

What I don't understand is why, after all the times we have mentioned this, there still is not a published table of differences between v6 and v7
including the status (will not be fixed, will be fixed in v7.xx, will be fixed but still unknown when).

Dear All,

I have an issue at hand and i will wholeheartedly cherish a specific response addressing the issue and no story please.
The issue is that i purchased about 10 units of ccr2116 with v7.8 already on the device but most of my active ccr1036 are on v6.49.7 and am changing about 10 units of the ccr1036 to ccr2116 and i desire to downgrade the v7.8 on the ccr2116 to v6.49.7.but several efforts of downgrading the ccr2116 with v7.8 to v6.49.7 proved abortive and not yielding results. Can someone guide on how the downgrading can possibly be done?

No Mikrotik device can be downgraded lower than factory software version. No way around it.

Sometimes this limit is superficial, but sometimes it's very real. E.g. v6 doesn't contain device drivers for ax wireless cards (and likely for SoCs and switch chips as well). Some device families got newer hardware revision (which is not wildly publicized, but it's possible to find out if your devices are of different revisions) which again requires certain support in ROS.

...
The issue is that i purchased about 10 units of ccr2116 with v7.8 already on the device but most of my active ccr1036 are on v6.49.7 and am changing about 10 units of the ccr1036 to ccr2116 and i desire to downgrade the v7.8 on the ccr2116 to v6.49.7.but several efforts of downgrading the ccr2116 with v7.8 to v6.49.7 proved abortive and not yielding results. Can someone guide on how the downgrading can possibly be done?

As @mkx has written already what you want is not possible. Therefore the only way forward for you if you want to stay with MikroTik is back to the school and learn v7. Start with: Upgrading to v7 part of the documentation and follow the reading with Moving from ROSv6 to v7 with examples than go trough the rest of the documentation (including examples) with a fine comb.
Also you may want to read relevant parts of the forums that might prove useful in adapting v7, such as: How to: Edge router and BNG optimization for ISPs.

Also @rextended described the process of how to get rough guide to configure your new CCR2116s to which I would only add that for obvious reasons replace 7.7 with 7.13.1 wherever it is in that guide.

One of the problems is that there is no offline converter for configurations from v6 to v7.
When you have existing hardware running v6 you can upgrade that and it will mostly convert the configuration, but when you have bought a shiny new CCR2116 that can only run v7 you cannot paste the export of a router running v6 in there and have it converted for you.
Sometimes it is possible to do it in a CHR, but it is an extra hoop to jump through.
Would be nice when there was an item on mikrotik.com where you could upload your export.rsc or supout.rif, have it converted to v7 and then download the v7.rsc that can be used on a new device.

that for obvious reasons replace 7.7 with 7.13.1 wherever it is in that guide.

So, actually must be "If I had to migrate from CCR1036 v6.49.10 to CCR2112 v7.13.1...."