Introduction
This document describes the recommended steps for upgrading RouterOS to v7 major release and the possible caveats when doing so.
Upgrading from v6 to v7 happens exactly the same way, as upgrading within v6 releases. Please follow the Upgrade manual for more detailed steps. If you are currently running RouterOS version 6 or older, we first suggest upgrading to the latest stable or long-term release in v6 (currently 6.48.6 Long-term or 6.49.5 Stable).
In most RouterOS setups that run fine with the aforementioned v6 versions, no extra steps are required. Upgrading to v7 will automatically convert the configuration and your device will function right away.
Feature list compatibility
As previously stated, nearly all RouterOS systems can use the "Check for updates" functionality and upgrade to v7 in a few clicks, but there are some features, where extra steps may be required:
| Feature | Status |
|---|---|
| CAPsMAN | OK |
| Interfaces | OK |
Wireless | |
| Bridge/Switching | OK |
| Tunnels/PPP | OK |
| IPv6 | OK |
BGP | OK, but attention required * |
| OSPF | OK, but attention required * |
| MPLS | OK, but attention required * |
Routing filter | OK, but attention required * |
| Tools | OK |
Queues | OK |
| Firewall | OK |
| HotSpot | OK |
| Static Routing | OK |
| User Manager | See caveats |
| Dude | |
Caveats
BGP
All known configurations will upgrade from 6.x to 7.x sucessfully. But keep in mind that there is complete redesign of the configuration. v7 BGP implementation provides with connection, template and session menus.
Template contains all BGP protocol-related configuration options. It can be used as a template for dynamic peers and apply a similar config to a group of peers. Most of the parameters are similar to previous implementatiob except that some are grouped in the output and input section making the config more readable and easier to understand whether the option is applied on input or output.
BGP connection minimal set of parameters are remote.address, template, connect, listen and local.role
Connect and listen to parameters specify whether peers will try to connect and listen to a remote address or just connect or just listen. It is possible that in setups where peer uses the multi-hop connection local.address must be configured too. Peer role is now a mandatory parameter, for basic setups, you can just use ibgp, ebgp.
Now you can monitor the status of all connected and disconnected peers from /routing bgp session menu.
Other great debugging information on all routing processes can be monitored from /routing stats menu.
Networks are added to the firewall address-list and referenced in the BGP connection configuration.
OSPF ROSv7 Basic Routing Examples
MPLS
Routing filter - all supported options are upgraded without any issue, in case of an unsupported option - an empty entry is created.
User Manager