Dear Team,
When we upgraded the configured router from OS version 6 to OS version 7 we cannot find some configurations in the router,But the configurations work fine.As a example BGP networks can’t show the router after we configured the Router OS version 6 to OS version 7.The issue is the when we need to change that configurations we cannot do it because the configuration can’t find on that router.Is there any solution for this issue?
Problem explained very badly, we don’t understand anything.
Configuration of quite a few functions is different in v7 … and configuration place has changed. So I’m with @rextended: describe the problem with due detail and only then somebody would be able to help you.
There is an internal process call crossfig that automatically migrates configuration from V6 to V7, so that’s why it works.
OP mention BGP – that has change a lot: https://help.mikrotik.com/docs/display/ROS/BGP. BGP has new engine and new config system, but still should be under Routing>BGP and Routing>Filter – that later has change more radically since there new rules language (https://help.mikrotik.com/docs/display/ROS/Route+Selection+and+Filters).
Hello lankacom,
When upgrading from RouterOS version 6 to version 7 on a MikroTik router, it’s possible that some configurations might not be visible or accessible due to changes in the software. Here are a few steps you can take to address this issue:
Review the MikroTik documentation Check the official MikroTik documentation, release notes, and upgrade guides for version 7. These resources often provide information about changes in configuration syntax, deprecated features, and any specific considerations when migrating from version 6 to version 7.
Check for configuration compatibility Verify that the configurations you are looking for are still supported in RouterOS version 7. It’s possible that certain features or configuration options have been modified, removed, or replaced. Cross-reference your configurations with the documentation and ensure they align with the syntax and requirements of RouterOS version 7.
Use the terminal or command-line interface Try accessing and modifying the missing configurations using the terminal or command-line interface (CLI) of RouterOS version 7.
Sometimes, certain configurations may not be visible in the graphical user interface (GUI), but can still be accessed and modified through the CLI.
Contact MikroTik support or community If you are still unable to locate or modify the configurations after following the above steps, reach out to MikroTik support or consult the MikroTik community forums.
They can provide guidance, insights, and potential workarounds for specific configuration issues encountered during the OS upgrade.
Configuration migration In some cases, a direct migration of configurations from RouterOS version 6 to version 7 might not be possible due to substantial changes in the software. You may need to manually adapt and reconfigure the settings to align with the new version’s syntax and capabilities. Taking backups of your existing configurations before the upgrade is highly recommended to facilitate the migration process.
That will help you .
Thanks.
After upgrading the firmware of my MikroTik router from version 6.48.4 to 7.2, I encountered an issue. Although the previously advertised networks are still being propagated through BGP without any problems, I am unable to view or export the network list that I had previously advertised under BGP network. It’s important to note that there is no issue with the BGP itself; the BGP session is up and the networks are being advertised correctly. However, I’m unable to add new networks without creating an address list and associating it with the BGP peer. When I do add new networks in this manner, only the newly added IP addresses are advertised, while the old IP addresses that were advertised before the firmware upgrade continue to be propagated.
I would appreciate assistance in uncovering the hidden configuration for these networks. I have verified that the BGP configuration is correct and the session is established. Additionally, I have reviewed the release notes for the new firmware version and there are no specific indications of changes affecting the behavior of BGP network advertisements or address lists.
what you write makes no sense:
switch from 6.48.4 to 7.2…
Why didn’t you stay at v6 by updating to 6.48.7, or 6.49.8 at least…
and why if you really wanted to put the v7 did you put the 7.9.2 instead or, for example, the 7.7?
why you to upgrade something that is working?
Known problems when upgrading systems that have BGP:
Hi All!
This is crazy and very disappointing on Mikrotik’s part!!
Mikrotik is the developer and knows everything about every version and its functionality inside out and upside down!!! they are only people that can write a conversion toll in the upgrade process that 100% converts 6 to 7 with all changes in the 7 functionality automatically accounted for and correctly converted!!! it should then provide a report of the unconverted that is impossible to convert (and i dont believe there should be any) and report on it and make real world suggestions on how to accommodate them!!!
Why is this so hard Mikrotik???
this is called customer support, specially when its a major version upgrade!!!
If you reply Mikrotik we dont want to hear any excuses as ther should be NON!!! you guys wrote it!!!
if there’s elements that have been removed or drastically changed then the tool should look at the config and upgrade 6 to the working equivalent in 7!!!
Sorry for sounding pissed off as i obviously am!!! i keep seeing ongoing post of people having issues in upgrading.
Mikrotik plz provide a conversion tool to not only maintain or even improve your credibility but more important provide a proper customer support!!!
Desperately waiting…
Snowman
p.s I’ve been using MT sinse 2001, i’ve seen this over and over again, i know you can do it!
snowman62 what are you talking about? this is some really old topic.
do you have any issue and need help?
Hi Normis,
It dosent matter if its an old topic the fact still remains that Mikrotik has failed to provide a clean 100% upgrade from 6 to 7 with all relevent functionalities of 6 upgraded to 7!! thats what i’m talking about!
I have numerous routers with close to 1000 vlans and mpls/vpls and bgp connections and i have to manually configure because the upgrade is not 100% !! Thats not including any other features of 7 thats changed from 6.
Normis: why hasent Mikrotik provided a proper comprehensive 100% upgrade function from 6 to 7???
Normis,
Do you think the conversion issues I described above are resolved in recent v7?
I have never seen change notes in versions claiming that they were.
Do I need to setup a test v6 and convert to v7.12.1 and reproduce them or can you show any other evidence?
snowman62 it should not be like that. If you have specific example, just make a report to support.
99% of people upgraded seemlessly. that’s why I’m asking.
Normis, your own documentation states the upgrade dosent 100% upgrade OSPF, MPLS,VPLS etc!!
I recently upgraded on of our main routers and OSPF, VPLS and MPLS didnt upgrade to 7 and any vlans associated with the relevant VPLS links also didn’t even transfer/convert/upgrade!! whats the point of an upgrade when we have to do a lot of additional work and testing for Mikrotik to get things working???
We all expect an upgrade to be fully 100% functional as it was in v6 in v7 without any exceptions!! after all Mikrotik wrote all of it and knows what and how things need to convert and function as they did in v6!!! 100% If default templates or instances in any configuration is is required then you need to implement this in the upgrade process and leave the finished states as it was functioning in v6.
https://help.mikrotik.com/docs/display/ROS/Upgrading+to+v7#Upgradingtov7-bgp This page should all be green and have no user required modifications to complete a 100% compatible upgrade!
Sorry for being brutally honest but this has been going on for over 20 years and its become a joke!!! we all know that feature releases dont function properly because they haven’t been tested properly by Mikrotik, its gotten a bit better these days but still its not good enough when were trying to run a business and support our customers and you guys!
In past few years, support has gotten much better at responding to issues. I suspect if you took Normis up on filing support case — including a supout.rif from V6 that works, and V7 where it doesn’t work — they’d take a look at whatever is wrong.
Understand the frustration, but there is a reason the pricing is different than cisco/etc. And there are big changes between V6 and V7, so not everything perfectly maps — especially in BGP — so some decision need to be made when upgrading. I used to use “dynamic-in” rules in V6, but those are “gone” (depricated) in V7…so while system upgrade okay — it does removes them & scripts have to be used in their place…but it was a “one time” annoyance. RouterOS is still pretty stable — once upgraded/configured — same as it always was.
Hi Amm0, i get that but if any scripts or whatever is required to accommodate the upgrade then Mikrotik upgrade should produce the scripts and upgrade accordingly!! i’ve been developing software as part of my career in IT/Telecom for over 40 years and as the author of any given SW you have full control of what an upgrade does and take action to upgrade any deprecated feature in the new version, if the functionality still exists then the upgrade needs to make it work no excuses! I’m sure anyone that has a comprehensive ROS router configuration in a production environment dosent want to deal with the Mikrotik upgrade process from 6 to 7!!! and in most cases they dont upgrade to 7.
I’d rather pay for a major version upgrade that does a complete 100% upgrade, in fact ROS needs a feature where if you buy a MT router with version 7 or any other major version you should be able to import any ROS config with an Import/upgrade command into the new Router 7 product (obviously with the same number of ports, even port discrepancies can be accommodated for) and have it work 100%. Mikrotik: take this as a new feature request please.
your own link to the documentation has the line “BGP: All known configurations will upgrade from 6.x to 7.x successfully.”
Like I said, concrete specific examples are needed. What was wrong?
Read my posting above from Mon Jun 12, 2023 1:11 pm
That is what came out of my own tests of existing standard configuration for our clients. Maybe there is more.
Do you claim these were fixed?
When did you attempt those migrations? Have you reported the issues to support?
It was earlier in the v7 releases. I have reported some to support, they were acknowledged to exist.
But I have never seen (or do not remember seeing) release notes lines that mention improvements.
When I have time I will attempt another conversion of v6.49.10 to v7.12.1 with these config items and see what happens now.
(I need to setup a test environement because when I do these on a production device I lock myself out)