Unimus forum

Posted: **Wed Jun 25, 2025 4:18 am**

Hi All,

I'm currently working to evaluate the Unimus tool for a use case in which we wish to centralize the configuration of MikroTik RemoteAPs globally. Currently, my thought was to instruct the RemoteAPs to download a .rsc file, which they can then proceed to run. My question is, if the script should trigger a reboot of the device, I would assume the Mass Config Push is going to report failure. What sorts of options do I have to work around this dependency? Does Unimus have a concept of trying to reconnect upon disconnect? The only thing I saw was to use wait-reply=no, but this would never give me the confirmation that the configuration from the script was completed successfully. Thank you, and I look forward to getting some input!

Posted: **Fri Jun 27, 2025 4:00 pm**

David,

I am pretty sure that there isn't a way for Mass Config Push to re-login to a device once it closes the Telnet/SSH session. I am talking to the devs about this, but I don't see a way around the SSH session being automatically terminated by the MikroTik during the reboot process.

You can get around some of your issues with the "$(wait-reply no)" command. This would at least get you the output up to the point of the device rebooting.

Note, here's my testing script that allows me to not get the "INTERACTION_ERROR" message and no output.

Code: Select all

interface print
/sys reboot
y$(wait-reply no)

gives me:

Code: Select all

<prompt> interface print

Flags: R - RUNNING
Columns: NAME, TYPE, ACTUAL-MTU, MAC-ADDRESS
#   NAME    TYPE      ACTUAL-MTU  MAC-ADDRESS
0 R ether1  ether           1500  BC:24:11:2B:0D:C2
1 R ether2  ether           1500  BC:24:11:7D:B3:3C
2 R ether3  ether           1500  BC:24:11:CD:0C:44
3 R lo      loopback       65536  00:00:00:00:00:00
<prompt> /sys reboot
RReboot, yes? [y/N]:

I think the best option currently is to have a second Mass Config Push that you run after the first that will check the config once the .rsc has run.

We are working on a configuration validation add-on to Unimus, but it isn't quite ready for prime time yet. Basically you would run your Mass Config Push, and then the next backup that would be run for the devices Unimus could verify the configs against a rule set that you create. This would give you a yes/no on if the devices are matching your intended end configuration.

Unimus forum

Unimus Mass Config Push Handling Reboot

Unimus Mass Config Push Handling Reboot

Re: Unimus Mass Config Push Handling Reboot