Unimus forum

I would recommend trying the 1.7.0 Beta.

There were a bunch of improvements to both backup and discovery mechanisms.
Error logging for jobs was also improved, so now it will show you more details about a job failure, rather than just "backup failed".

There were 2 failures on 29th of April: 1st a scheduled backup failed. This cause Unimus to do a re-discovery, which succeeded. After that, a re-backup failed again. Meaning there was something wrong with the device at that time which prevented Unimus from backing it up (but discovery succeeded). Un...

Could you please post the output of:

Code: Select all

cat /etc/unimus/unimus.properties | grep "database.path"
ls -l /etc/unimus/hsql
cat /var/log/unimus/unimus.log | grep "Connecting to database" -B 3 -A 3

We have a blog article on automating RouterOS upgrades: https://unimus.net/blog/network-wide-mikrotik-routeros-upgrade.html The article shows how to setup a local RouterOS Package Source "server". Unimus is then used to push package source configuration to the network, and tell the MikroTi...

Could have sworn the 1.6x had that. If this is a feature request, I'll pop the request/question in the right forum. On the Dashboard, there is a failed jobs log. That will have a list of all devices that failed, and the reason the job failed. Is that sufficient, or should we do something more in th...

We released 1.7.0-Beta3 today that has a bunch of fixes and improvements to Config Push.
Testing would be very welcome

More info in the Beta thread:
viewtopic.php?p=1056#p1056

1.7.0-beta3 is released today. Original post updated to reflect this. Changes from beta2: Features: "Network scan" feature upgrades: - fixed scanning IPs even after a scan has been stopped - fixed not showing "Last run:" when a scan was stopped - fixed ping result not being corre...

Sorry for the late reply, was waiting for fixes to a few of these issues in Beta3, which is now available. (so a few of these issues should already be fixed) One enhancement that would be AWESOME is if when you select devices that you could pick NetXMS container names and then it would maintain that...

The one device that came back with COMMAND_NOT_SUPPORTED was the same ROS version as the other devices and indeed when we logged into the device the configuration was setup properly. There must have been some output from the device that Unimus recognized as an error. I think the best approach would...

I am trying to use one mikrtik backup as a template for another. Do I have to remove the mac addresses from the backup before restoring to the new router? This new router will be used at a new location, not replacing existing unit There is no need to strip anything to restore to a new unit. Only re...

Unimus forum

Search found 1221 matches

Re: Backup failure - Maybe false positive

Re: Backup failure - Maybe false positive

Re: [Solved] Migrate Unimus across platforms?

Automating MikroTik RouterOS updates

Re: [BETA] 1.7.0 beta thread

Re: Network automation

Re: [BETA] 1.7.0 beta thread

Re: [BETA] 1.7.0 beta thread

Re: [BETA] 1.7.0 beta thread

Re: Restore to a different model routerboard