Documentation updates - October 6, 2026
Summary of documentation changes made on October 6, 2026.
Management Tools
- CMR: The Alert rules section now separates state alerts from event alerts, with a table that compares them:
- A state alert (CPU, memory, disk, and health thresholds,
connected,disconnected-more-than,upgrade-available) stays active while all its conditions match. It runs its actions once when it becomes active and counts indevices-onand the dashboard until it clears. - An event alert (
interface-change,upgrade-done,upgrade-job-done,rebooted,unpaired-device-connected, or a log message matched bylog-topicsandlog-regex) runs its actions for every occurrence and never stays active. A rule can combine several state conditions but has at most one event condition. - A new Device and system scope section: most alerts apply per device, and
upgrade-job-doneis a system alert that reports a whole upgrade job without device context. show-deviceslists the devices on which a rule's state alert is active. It lists no devices for an event alert, whosefiredvalue counts the occurrences instead.
- A state alert (CPU, memory, disk, and health thresholds,
- CMR, CMR-Client: Corrections to connecting and pairing clients:
- Clients connect to the server over TCP port
54321. Allow it in the server'sinputchain and in any firewall between the clients and the server. The client troubleshooting forstatus: searchingnow points to the port and the firewalls. - The client's
pairing-requirementsupportsnoneandpassword.confirmexists only on the server, where/cmr/device/pairapproves the pairing. The client-sideconfirmcase is gone from the troubleshooting list.
- Clients connect to the server over TCP port
- CMR, CMR-Client: Details of upgrades, reboots and alerts:
/cmr/device/upgradewithoutchannelupgrades each device on its own upgrade channel, and withschedule-timethe job waits for the next occurrence of that time. A job it starts for devices selected by number has nolabels, andrun-nextstarts a job scheduled this way itself.- Removing a scheduled job marks it
cancelledand keeps it in the list. Removing acancelledjob deletes it. - The server's log messages for device upgrade results, newly available versions and reboots are listed.
rebootreturns right away. - Alert variables:
[state]is empty for a paired device with nothing in progress, the usage values areunknownuntil the device reports them,[upgrade-error]is empty after a successful upgrade,[upgrade-state]is the final state of the device in the job, and the job times have the form2026.10.06-14:20:36. - When CMR restarts on the server, state alerts that still match become active again and run their actions.
- The REST API returns the WiFi passphrase to users with the
sensitivepolicy. - The client logs each change of its
statusand reconnects with its existing pairing when the connection to the server drops.
- CMR, CMR-Client: Defaults and server settings:
fail-policydefaults tostop, andstopwithstrategy=parallelno longer needsorder. Onlycontinue-orderrequires it.upgrade-check-intervaldefaults to10h.apptraffic-devicesdefaults to thegatewaylabel, andallselects every device.- The client's
pairing-requirementdefaults topassword. - Clients find the server through neighbor discovery or DNS: the client resolves
_cmr._tcp.lanand_cmr._tcp.followed by the domain name from DHCP option 15. DHCP alone does not announce the server. /cmr set !<setting>returns a setting to its default. Changingpackages-directory,upgrade-check-interval, orpairing-requirementrestarts CMR on the server, so every client reconnects and state alerts fire again.- Changing an enabled alert rule, even only its comment, makes its state alert fire again on the devices that match.
- In the
linksvalue of a layout link, a*before a port name marks a direct, physical link. It does not mark the PoE supplier.
- CMR: Node coordinates are relative to the layout center:
xincreases to the right andydownward, so a smalleryplaces a node higher on the map. - SSH: The page is reorganized around the SSH server, the interactive client, and scripted use. A new "Verify remote host keys" section explains the
known-hosts-validationsetting (enabled on new installations, kept as-is on upgrades), the interactive trust and key-update prompts of/system/ssh, and the ways to makessh-execand SFTP fetch work with validation on: pinning keys in/ip/ssh/known-hosts,known-hosts-ignore, orknown-hosts-trusted-subnets. The "Server host key" section documents the fingerprint, regeneration, and the export file names. Importing a client-side private key now lists the accepted PEM formats and notes that OpenSSH private keys are rejected. Thessh-execexample no longer contains a plain-text password and states its prerequisites.
CLI Reference
/cmr/alert,show-devices: Descriptions follow the state and event split.connectedis a state condition,rebootedand the log conditions are event conditions,devices-oncounts only active state alerts, andreset-on-disconnectapplies to state alerts.show-deviceslists the devices on which the rule's state alert is active./cmr:pairing-requirement=passwordtakes the username and password of a RouterOS user on the device, as in the CMR guide. CMR has no separate pairing password./cmr/device/upgrade,reboot,/cmr/upgrade/job,run-next: Descriptions of the channel andschedule-timeof a device upgrade, the emptylabelsandchannelof its job,run-nextfor a job scheduled this way, and the log message after a reboot./cmr,/cmr/client,/cmr/upgrade,/cmr/device/upgrade,/cmr/layout/link: Defaults forupgrade-check-interval,apptraffic-devices,fail-policyand the client'spairing-requirement, DNS discovery incontroller-addresses,orderrequired only forcontinue-order, and the*inlinks./cmr/client,/tool/apptraffic,/system/routerboard/usb: The MIPS-LE architecture (mipsel), which has no RouterOS 7 release, is no longer listed in the conditions of these pages or in the application traffic note of the CMR guide. The/system/routerboard/settings/keep-frequencypage is removed: the command exists only on MIPS-LE devices./ip/ssh,known-hosts,/system/ssh,/system/ssh-exec: All parameter descriptions are filled in, including the host-key validation settings and the previously undocumentedhost,key,portandvrfparameters.ssh-execnow documents what itsexit-codeandoutputcarry on remote command failure./interface/wifi/radio: References to the unreleased "meshpoint" mode are removed./ip/dns/adlist, DNS: Disabling an adlist does not free its cache memory.
Mobile Networking
- LTE/5G: New "Multi APN" section: check
max-apn-countwithshow-capabilities, create a slave LTE interface withmaster=for each additional APN connection, and the interface'sapn-profilesparameter is renamed toapn-profile(the old name is still accepted for single-APN configuration).
Firewall & QoS
- Packet Flow: The packet flow diagram is updated.
Hardware
- CRS310-8G+2S+IN: The reset button section lists its three functions. A configuration reset now waits for the PWR LED to flash instead of the USR LED, and Netinstall describes both the Regular Booter (press Reset 1–2 seconds after power-on) and the Backup Booter (hold Reset while powering on until the LED blinks, turns steady, and goes off).