Introduction · Topic 5 of 8

Upgrading RouterOS and RouterBOOT Firmware

Learn the RouterOS package types, the main ways to upgrade a router, and how the RouterBOOT firmware is upgraded as a separate step after a reboot.

  • 4 min
In a nutshell
  • RouterOS is delivered as packages, and the main package carries the core features.
  • A package must match the architecture of the router.
  • /system resource print shows the architecture.

What it is

Upgrading means replacing the RouterOS packages on a router with newer ones, and then updating the boot loader.

RouterOS is delivered as packages. A router needs the right package for its CPU type, and a few optional packages add extra features.

The RouterBOOT firmware is separate from RouterOS. It is upgraded in its own step, after RouterOS has been upgraded and the router has restarted.

Check for updateschanneldownloadPackagenpk filerebootNew RouterOSrunningfirmware upgradeRouterBOOTnew version

How it works

You pick a package, choose a method to deliver it, reboot, and then upgrade the firmware.

Package types

RouterOS features are grouped into packages. The main package carries the core system, and extra packages add optional features.

Package ideaMeaning
Main RouterOS packageCore features and the common services
Extra packagesOptional features, installed on demand
ArchitectureEach package is built for one CPU type, so it must match the router

In version 6, some features, such as IPv6, hotspot and MPLS, are separate packages that you can enable or disable. In version 7, more features are included in the main package, and the list of extra packages is different. Check the package list of your version before you plan an upgrade.

You can see the installed packages and the CPU type of the router with these commands.

/system package print
/system resource print

The resource output shows the architecture name. Download the package that matches it, because a package for the wrong architecture cannot be installed.

Ways of upgrading

WayHow
Check for updates in the consoleThe router downloads the package from MikroTik
Upload a package fileCopy the package file to the router, then reboot
WinBox or WebFigUse the package menu or Quick Set, and the router downloads it
NetinstallReinstall from a PC, which normally resets the router configuration

The easiest way is to let the router fetch the update itself. It needs a working Internet connection and a chosen release channel.

/system package update check-for-updates
/system package update download
/system package update install

check-for-updates asks the update server for the latest version. download fetches it, and install applies it. The router then reboots by itself to finish the install.

The second way is to download the package file to a PC and upload it to the router. You can drag the file into the Files window of WinBox, or send it over FTP. When the router reboots, it installs every package file it finds in its file list.

Exam tip

When the router has no Internet access, uploading the package file by hand is the reliable way to upgrade.

Netinstall is a heavier way, and a later page explains it. It is used for recovery, not for routine upgrades.

Release channels

RouterOS releases are published on channels. The stable channel is the normal choice for production routers. The other channels carry newer or testing builds.

Choose the channel before you check for updates, and read the changelog first. A major version jump, such as version 6 to version 7, can change behaviour, so test it on a spare router when you can.

RouterBOOT firmware upgrade

RouterBOOT is the boot loader of a RouterBOARD. A RouterOS upgrade does not change it automatically, so the firmware must be upgraded as a second step.

/system routerboard print
/system routerboard upgrade
/system reboot

The print command shows the current firmware and the upgrade firmware, which is the version bundled in the installed RouterOS. If they differ, run the upgrade and reboot, because the new firmware only takes effect after a restart.

The firmware upgrade applies to RouterBOARD hardware. An x86 PC or a CHR has no RouterBOOT to upgrade.

What to remember for the exam

Seven facts cover this topic.

  • RouterOS is delivered as packages, and the main package carries the core features.
  • A package must match the architecture of the router.
  • /system resource print shows the architecture.
  • The router can fetch updates itself, or you can upload a package file and reboot.
  • The router installs uploaded packages during the reboot.
  • RouterBOOT is upgraded separately with /system routerboard upgrade, followed by a reboot.
  • A RouterOS upgrade does not upgrade RouterBOOT by itself.
Watch out

Do not power off the router during an upgrade, because an interrupted install can leave it needing Netinstall.

Common mistakes

These four mistakes are common.

Uploading the wrong architecture. The package must match the CPU type shown in the resource output.

Forgetting the firmware step. After the RouterOS upgrade, check /system routerboard print and upgrade the firmware too.

Skipping the reboot. Packages are applied and firmware takes effect only after a restart.

Upgrading blindly across major versions. Read the notes first, because version 6 and version 7 differ in several features.

Check yourself

Work through these three questions.

  • How do you find the package that suits a router?

    Run /system resource print to read the architecture, then download the package built for that architecture.

  • What are two ways to upgrade RouterOS without Netinstall?

    The router can check for updates and download the package itself. Or you upload a package file and reboot, and the router installs it.

  • Why is a separate firmware step needed?

    RouterBOOT is separate from RouterOS, so a RouterOS upgrade does not change it. Run /system routerboard upgrade and reboot.

Topic 5 of 8 in Introduction

Test yourself on Introduction

The full MikroTik MTCNA question bank has 558 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by MikroTik. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.