Unimus forum

Example of issue: 192.168.1.0 192.168.1.1 192.168.1.10 192.168.1.2 192.168.1.205 192.168.1.3 Can we have an additional option or parameter added that would order this differently? It's painful to parse through a lot of devices when you simply want to sort by IP address and the order is a jumbled me...

I'm standing Unimus up to test against Oxidized. I am having no issues with Cisco devices... but I cannot get our Moxa devices to work. I have a newer switch (eds-g4014) that I'm trying to add/discover. I get an error stating that the device is unsupported. Unimus is able to connect via ssh, and lo...

We just pushed out 2.4.0-Beta4. The complete Changelog was updated in the first post. New since 2.4.0-Beta3: Features: Improved support for logins to JunOS in BSD mode Fixes: Fixed discovery would fail on JunOS devices with specific BSD prompt format Fixed Remote Core would not be able to reconnect ...

We just pushed out 2.4.0-Beta3. The complete Changelog was updated in the first post. New since 2.4.0-Beta2: Features: Added support for devices which don't respond to the none SSH auth method. Added support for output termination in newer versions of VyOS Added support for Linux shell login on netE...

Hi! I checked our OpenGear driver, and we currently support IM, CM / CS and ACM / RMG. It seems OM is different enough where our current driver doesn't pick it up. I will follow up in the ticket on what we need from you to make OM work

We just pushed out 2.4.0-Beta2. The complete Changelog was updated in the first post. New since 2.4.0-Beta1: Features: Added a built-in backup filter for new timestamp format in MikroTik RouterOS v7.10 Improved handling of errors for Zones which use a NetXMS Agent as the Zone's proxy If a DNS lookup...

Is there a way that i can have Unimus ignore this and not keep making new backups when that is the only difference? MikroTik changed the format of the export header in RouterOS 7.10. You can add a Regex Backup Filter in "Backups > Configuration > Ignored data filters". You can use this re...

how do i fix it ? This happens when a database upgrade is interrupted - for example when after an update, Unimus starts the DB upgrade procedure, and the service is restarted / killed during the update. This is easily recoverable, but how to recover it depends on which DB type and OS you are using....

Hi, which version of Unimus are you running?

The behavior you are seeing is due to a change MikroTik did on their CLI, but I think we fixed that (added handling for this in our Tik driver) in one of latest Unimus versions.

rustyjarz wrote: ↑

Tue Jun 13, 2023 10:48 pm

We're on v2.2.4 and the latest is v2.3.3, so can we jump direct or there's an upgrade path?

Hi, you can upgrade directly to the latest version, the installer will take case of all the updates.