Maintenance workflow

RouterOS Firmware Upgrade Checklist for WISPs

Firmware drift is invisible until it isn't — a known bug finally bites, or a security advisory lands on gear you forgot was still on an old build. Here's how to keep it under control without breaking production links.

Try it in the live demo →

Why version drift creeps in

Every new site gets whatever firmware shipped on the radio that week. Every replacement unit from a truck stock gets whatever was flashed last time someone updated the image. Multiply that across MikroTik, Cambium, Mimosa and other gear over a few years, and a fleet of a few hundred radios easily spans a dozen-plus firmware versions — most WISPs genuinely don't know their own spread until they go looking.

Before you upgrade anything

Inventory first. Get a single view of every radio's running version against the latest known build, grouped by vendor. You can't plan a rollout you can't see.
Back up configs. Pull a fresh export (.rsc for RouterOS, equivalent for other vendors) immediately before touching anything.
Read the changelog, not just the version number. A jump across major versions (e.g. RouterOS 6.x → 7.x) can change default behaviors, not just patch bugs.
Open a maintenance window for the site so the upgrade's expected blip doesn't page the whole team.

Staged rollout, not fleet-wide

Upgrade a small, low-risk batch first — a backhaul-only site with no customer CPEs, or a single sector at a site with redundant coverage. Watch it for 24–48 hours before expanding. This is the single biggest lever against a bad firmware build taking down more than it had to.

During the upgrade

Confirm the maintenance window is active for that site before starting — you want the real device state tracked, just the alert noise suppressed.
Upgrade one device at a time per site where possible, so a failed boot doesn't take the whole site dark.
Verify the device re-registers and polls cleanly post-reboot before moving to the next one.

After: track drift going forward

A one-time cleanup doesn't stay clean. The useful version of this is continuous: a firmware/config drift view across the whole fleet, showing running vs. latest known version per device with a one-click scheduled upgrade, so new drift gets caught the week it appears instead of the year after. That's what TowerLens's 🧩 Firmware panel is for — it ties directly into the backup system, so every scheduled upgrade has a pre-change config export sitting right next to it.