MikroTik System Operations
Reboot a MikroTik router and check or install RouterOS updates from the monitor
Reboot a MikroTik router and check or install RouterOS updates from the monitor
On this page
The System Operations panel can reboot the selected router and query or install RouterOS package updates. Group Admin and Developer users can use it for routers in their group. NOC users also need manage-router-devices.
See MikroTik Device Management for all prerequisites and permission rules.
Reboot and update operations drop active sessions and make the router temporarily unreachable. Use an approved maintenance window, notify affected staff, preserve a current configuration backup, and confirm an alternate recovery path.
Reboot the router
- Open Device Management → System Operations.
- Click Reboot Now.
- Approve the confirmation, which warns that active sessions will drop and estimates about 60 seconds of unreachability.
ISPbills immediately sends the RouterOS reboot command. It does not wait for the device to return or verify recovery. A successful request is recorded in the device access log.
Check for a RouterOS update
Click Check for Updates. ISPbills reads the current system version, asks RouterOS to check its configured package-update channel, waits about half a second, and reads the update status.
The panel displays:
- Current RouterOS version
- Configured update Channel
- Latest version reported by RouterOS
- Whether the exact RouterOS status reports that a new version is available
This operation does not change the update channel. Set the desired channel in RouterOS before checking.
Install an update
The Install Update button appears only when the check reports an available version.
- Click Install Update.
- Approve the warning about download, automatic reboot, and dropped sessions.
ISPbills sends /system/package/update/install and returns immediately. RouterOS handles the download and reboot; the page does not track download progress, confirm the installed version, or roll back a failed update. Run Check for Updates again after the router is reachable.
A successful install request is recorded in the device access log. The read-only update check is not logged as a configuration change.
Troubleshooting
| Symptom | Response |
|---|---|
| The router goes offline after reboot/update | This is expected temporarily. Wait for RouterOS to boot, then test API reachability and live status. If it remains offline, use the alternate management path. |
| Install Update does not appear | The last check did not return the exact “new version available” status. Retry the check; then inspect update status and channel directly in RouterOS. |
Version or channel shows N/A |
RouterOS did not return that field. Verify API permission for system resource and package-update commands. |
| The check fails or times out | Verify API reachability, DNS/default route as applicable to the router, update-server access, and the RouterOS API account’s policy. |
| The command was accepted but recovery is uncertain | The response confirms command submission, not successful boot or upgrade. Verify the running version and service health after reconnection. |