Date: Thu, 28 Mar 2024 23:05:43 +0200 (EET) Message-ID: <2100233623.19.1711659943526@help.mikrotik.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_817747553.1711659943522" ------=_Part_18_817747553.1711659943522 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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 the same way, as upgrading within v6 rel= eases. Please follow the Upgrade manual for more detailed steps. If you are currentl= y running RouterOS version 6 or older, we first suggest upgrading to the la= test stable or long-term release in v6.
In most RouterOS setups that run fine with the aforementioned v6 version= s, no extra steps are required. Upgrading to v7 will automatically convert = the configuration and your device will function right away.
Note: We do not recommend running v7 on hardware that does not have at least 64 MB of RAM.=
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 so= me features, where extra steps may be required:
Feature | Status |
---|---|
CAPsMAN | OK |
Interfaces | OK |
Wireless |
OK |
Bridge/Switching | OK |
Tunnels/PPP | OK |
IPv6 |
OK |
BGP |
OK, but attention is required *= |
OSPF | OK, but attention is re= quired ** |
MPLS | OK, but attention is re= quired *** |
Routing filters |
OK, but attention is req= uired **** |
PIM-SM |
See notes |
IGMP Proxy |
OK |
Tools | OK |
Queues |
OK |
Firewall | OK |
HotSpot | OK |
Static Routing | OK |
User Manager | See notes |
The routing protocol configuration upgrade is triggered only once. This =
means that if a router was downgraded to ROSv6, the configuration was modif=
ied and the router got upgraded back to ROSv7, then the resulting configura=
tion is the one that was present before the downgrade. To re-trigger v6 con=
figuration conversion, load ROSv6 backup with the option force-v6-to-v7-configuration-upgrade=3Dyes=
.
All known configurations will upgrade from 6.x to 7.x successfully. But =
keep in mind that there is a 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 gro=
up of peers. Most of the parameters are similar to the previous implementat=
ion except that some are grouped in the output and input section making the=
config more readable and easier to understand whether the option is applie=
d 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 possi=
ble that in setups where peer uses the multi-hop connection local.address
must be configur=
ed too. Peer role is now a mandatory parameter, for basic setups, you can j=
ust use ibgp, ebgp.
Now you can monitor the status of all connected and disconnected peers f=
rom /routing bgp session
<=
/span> menu.
Other great debugging information on all routing processes can be monitore=
d from /routing stats
menu.
Networks are added to the firewall address-list and referenced in the BG=
P connection
configuration.
OSPF
All known configurations will upgrade from 6.x to 7.x successfully.
OSPFv2 and OSPFv3 are now merged into one single menu /routing ospf
. At the moment there are=
no default instances and areas. To start OSPF you need to create an instan=
ce and then add area to the instance.
RouterOSv7 uses templates to match the interface against the template an=
d apply configuration from the matched template. OSPF menus interface
and neighbor
contains read-only entries=
for status monitoring.
MPLS
=
Upgrade MPLS setups with caution, and make sure to backup configuration = before the upgrade.
Routing filters
All supported options are upgraded without any issue, in the case of an = unsupported option - an empty entry is created. The routing filter configur= ation is changed to a script-like configuration.
The rule now can have "if .. then" syntax to set parameters or apply act= ions based on conditions from the "if" statement.
Multiple rules without action are stacked in a single rule and executed = in order like a firewall, the reason is that the "set" parameter order is i= mportant, and writing one "set"s per line, allows for an easier understandi= ng from top to bottom on what actions were applied.
More RouterOSv7 routing filter examples are here.
PIM-SM
Upgrading RouterOS to v7 will not preserve PIM-related configuration. Af=
ter the upgrade, multicast routing configuration will be available under th=
e /routing/pimsm
m=
enu and an additional "multicast" package is not required anymore. More inf=
ormation is available here.
User Manager
RouterOSv7 provides the new and redesigned implementation of User Manage=
r, configuration is now integrated into RouterOS WinBox and console (WEB ad=
min configuration interface is not available), more information is availabl=
e here. Direct migration from older User Manager is not pos=
sible, it is possible to migrate older database from /user-manager/database/migrate-legacy-db
=
However, it might be a good idea to start configuration from the scratch.<=
/p>
A New Kernel is implemented in RouterOSv7, which leads to performance ch= anges due to route cache, as well some tasks might require higher CPU and R= AM usage for different processes.
In RouterOS v7 has been dropped support for: