← ClaudeAtlas

routeros-cmrlisted

Configure or debug MikroTik CMR on RouterOS 7.26beta1: the optional cmr controller package, built-in /cmr/client, routed controller-addresses or neighbor discovery, TCP/54321, independent pairing requirements, labels, fleet scripts, alerts and HTTP webhooks, topology, upgrade rules, package directories and backup/export limitations. Use for a CMR controller or client, waiting-for-pairing, CMR alert or upgrade rules, fleet run-script, or the /cmr menus. Use routeros-tikoci-quickchr for a disposable CMR lab and routeros-tikoci-centrs for validated device operations. CMR monitors RouterOS clients; it is not a general SNMP/ping replacement for The Dude.
tikoci/routeros-skills · ★ 91 · API & Backend · score 82
Install: claude install-skill tikoci/routeros-skills
# RouterOS CMR Grounded on **RouterOS 7.26beta1, x86 CHR**, with four disposable routers and three quickchr socket links. The controller, a transit client, a remote client reachable through OSPF, and a direct discovery client exercise different paths. The [runnable example][example] and [evidence report][report] are the reproduction surface. No later beta, arm64 CHR or WiFi radio was verified by this lab.[^lab] CMR manages RouterOS devices: inventory, resource/availability/log alerts, fleet scripts and upgrades, topology, and WiFi/VLAN provisioning. It does not provide general ping/SNMP/HTTP monitoring of non-RouterOS equipment.[^docs] ## Versions and packages CMR first appeared in 7.26beta1. Pin that version for reproductions and record both the controller and client versions. The lab installed the optional `cmr` package only on the controller; clients used the built-in `/cmr/client`.[^lab] The manual lists arm, arm64 and x86 for the server package. Clients exclude smips and powerpc. A mipsbe client was observed in the earlier hardware session; that architecture was not re-tested in the CHR lab.[^docs][^prior] ## Server, service and client discovery ```routeros /cmr set enabled=yes track-topology=yes fetch-comments=yes auto-labels=all ``` The controller lists its own built-in client in `/cmr/device`. A dynamic service named `cmr` listens on TCP/54321. Scope this service with the input firewall. In the lab, CMR was blocked on each host-management NIC so pairing used o