Cannot change back the CPU frequency

Confirmed reboot the router will make the change work. The temperature finally goes down, thanks for all the help.

Good. :slight_smile:

It is not at all clear (and actually not even the first reboot is often documented) which particular commands/changes actually need a reboot to be effective (most don’t of course), lately I came across a certain number of reports about this (or that) command that actually needs a reboot, hence I added the advice here as #23:
http://forum.mikrotik.com/t/gp-csa-for-mikrotik-devices/182176/1

In my perverted mind,.a reboot is going to happen before or later, so it is anyway good practice to test what happens when the device is rebooted while it is attended, but not having a definite list of which commands/settings actually need the reboot can easily confuse users that may think that their changes had no effect or - in some cases - a reboot cannot be performed if not after hours/with the network in maintenance mode, and you cannot be entirely sure of what will happen when it is performed. :frowning:

One question, after the command:

/system/device-mode/update routerboard=yes

Is there only : “turn off power” or reboot by pressing reset or mode button to make the change??

It’s very troublesome to power off, or press reset, can’t the developer team just allow user to reboot??

After routerboard=yes, my automatic backup&update script failed.

Bkp&Upd: config backup was not created, file does not exist: backup_v7.18.2_stable_2025-06-04-11-52-37.rsc
Bkp&Upd: Backup creation failed. Update process will be canceled if automatic update is enabled

I would like to turn routerboard=no and see if my backup&update script working, but it’s a rather annoying way to make the change…

BTW, what’s the mode button? where is it?

About automatic bacup&update, set up forceBackup to true solve the problem...

Additional parameter if you set scriptMode to osupdate or osnotify

Set true if you want the script to perform backup every time its fired, whatever script mode is set.

:local forceBackup true

Good to know about that “true” settings. :slight_smile:

The “mode” button is only on some devices, it is a programmable button to which you can “attach” a script or however an action/command that will be normally executed when pressed.

A very simple/basic example here:
http://forum.mikrotik.com/t/ledtoggle-simple-script-to-toggle-user-led-on-off/182527/1



It’s very troublesome to power off, or press reset, can’t the developer team just allow user to reboot??

The whole idea behind the setting (right or wrong as it may be) is that you cannot make that change without being physically present near the device (in order to push the button or remove power).
If you prefer it is a way to avoid that some changes can be made remotely by an attacker that managed to (remotely):

  1. get connected to the device
  2. access it (bruteforcing BOTH user name AND password)

Of course it is just fine for your home/lab or however “simple” setup, for remote devices, possibly mounted up a pole on top of a mountain, it is a huge PITA and - besides - while normally the device should reboot just fine if you remove power and re-apply it, there will always be the case when it won’t and you will need to climb up the pole or roof or whatever …

Good to know about that “true” settings. > :slight_smile:

Automatic backup&update failed again after i upgraded the RouterOS to 7.19.1, i thought changing the setting to true would solve the problem.
Unfortunately, even after i downgrade the RouterOS to 7.18.2, the script still failed to complete.

physically present near the device

CCR-1036 got NO power button. Each time pull out power cord will result in abnormal power off, risk to lose data. No need to say stick the reset hole risk to lose all data. The design is to punish users.

I used to maintain the trading workstaion for bank traders, the best say i heard is, the best security measure is to shutdown the workstaion and stop trading…

So will do any blackout (if you are not running an UPS, in which case it will be a UPS failure :wink: ) or limiter switch on that line triggered by anything, or someone tripping on the power cord .

While it is not a good idea to apply and remove power every (say) 5 minutes for a week, a few power off and power on won’t do much harm.