Unimus 1.1.0 release

Official news and announcements
Post Reply
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Thu Aug 24, 2017 4:16 pm

We are happy to announce that version 1.1.0 is being released today.
This version brings a new and updated 'Diff' view implementation, and better handling of 'enable' mode in all supported devices.

Links at https://unimus.net/download.html have been updated with the newest version.



Direct upgrade from 1.0.0 and 0.3.x is supported, simply deploy the new version of Unimus, and everything will work.
Direct upgrade from 0.2.x or 0.1.x is not supported, please see this link for more details.

Full changelog:
= Version 1.1.0 =
Features:
Improved performance when running many concurrent discoveries
Device import now updates descriptions for existing devices that don't yet have any description
Support for devices which disconnect the CLI after CTRL+C - Unimus will now properly discover and backup such devices
Unified the selection model in tables - all rows select on click, rows with checkboxes can still use checkboxes, or selection on click

New and improved configuration 'Diff' functionality:
- support for cross-device config diff (diff backups of 2 different devices)
- added 'Split' (side-by-side) diff mode
- added option to squash unchanged lines ('Show only changed lines')
- newer backup now always properly considered as new revision in the diff view (selection order of backups no longer matters)

Improved handling of 'enable' (privileged-exec) mode
- improved discovery speed for devices which support 'enable' (privileged mode) switching
- devices that use 'enable' (privileged mode) will no longer attempt to 'enable' if already in 'enable' mode after login
- added support for devices which require username and password to switch to 'enable' mode
- all supported devices that use 'enable' (privileged mode) will work properly if in 'user' (user-exec mode) or 'enable' mode after login

Added support for:
- Arista switches
- VyOS
- Zyxel MGS switches

Fixes:
Fixed high CPU usage by the discovery process in rare conditions
Fixed discovery timing out and never completing in rare conditions
Fixed scheduled NMS import failing

Known issues:
Application startup times can be long (up to 2 minutes on slow hardware)
Post Reply