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 in devices-on and the dashboard until it clears.
  • An event alert (interface-change, upgrade-done, upgrade-job-done, rebooted, unpaired-device-connected, or a log message matched by log-topics and log-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-done is a system alert that reports a whole upgrade job without device context.
  • show-devices lists the devices on which a rule's state alert is active. It lists no devices for an event alert, whose fired value counts the occurrences instead.
• CMR, CMR-Client: Corrections to connecting and pairing clients:
  • Clients connect to the server over TCP port 54321. Allow it in the server's input chain and in any firewall between the clients and the server. The client troubleshooting for status: searching now points to the port and the firewalls.
  • The client's pairing-requirement supports none and password. confirm exists only on the server, where /cmr/device/pair approves the pairing. The client-side confirm case is gone from the troubleshooting list.
  • The client is not supported on the mipsel, smips, and powerpc architectures. The pages named only smips and powerpc.

CLI Reference

• /cmr/alert, show-devices: Descriptions follow the state and event split. connected is a state condition, rebooted and the log conditions are event conditions, devices-on counts only active state alerts, and reset-on-disconnect applies to state alerts. show-devices lists the devices on which the rule's state alert is active.

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).