Unimus 2.6.2 & Unimus Core 2.6.2 release

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

Tue Feb 25, 2025 3:10 am

Unimus-release-banner-262.png
Unimus-release-banner-262.png (158.93 KiB) Viewed 56244 times

Unimus 2.6.2 is being released today! This is a minor feature and bugfix release in the 2.6 code branch.

Release highlights:
- Added option to unlock DB and retry on failed upgrades
- Added a progress bar to the DB upgrade procedure
- Improved DB upgrade speed and resource usage on large deploys
- Support for 4 new device types
- 10 other minor improvements
- 13 bugs and issues fixed

If you missed the 2.6 Release Overview on our blog, please check it out for a summary of what is new in the 2.6 branch.
Links at https://unimus.net/download have been updated with the newest version.

Full Changelog:
= Version 2.6.2 =
Features:
Improved Dashboard load speeds on large deployments
Optimized disk usage of large-scale DB upgrade procedures
Optimized memory usage of large-scale DB upgrade procedures
Added a column to the Users table to show if MFA is active for an account
Various minor UI / UX improvements and tweaks
Improved credential discovery to support devices that disconnect the SSH session on wrong credentials instead of reporting auth failure
Improved handling of virtual environments on CheckPoint Gaia-based devices
Multiple improvements and optimizations to the Discovery logic and algorithm
Added a configuration option to allow security handlers in more than just the 1st page of device output
Added support for pagination on Fulcrum switches
Improved built-in dynamic filters for Netgear devices

Substantial speed improvements to the DB upgrade procedure:
- when upgrading from 2.5 (or older), the DB upgrade could take a very long time on large deploys
- we have substantially improved the DB upgrade duration, in some cases it's decreased by 60%
- please note on very large deploys, the DB upgrade can still take up to an hour

Added a progress bar to the DB upgrade procedure:
- since upgrade from 2.5 (or older) to 2.6 can take longer time, we have added a progress bar
- during the startup, you will see both the number of migration steps, as well as actual progress of each step
- number of steps out of total steps for the upgrade is reported
- for steps that take longer, a progress bar of the step's internal progress will be shown as well

Added an option to unlock the DB and retry an upgrade directly in the GUI:
- when a DB upgrade was interrupted (such as restarting Unimus during an DB upgrade), a stale lock would be left in the DB
- we added a button that will allow you to free the lock directly from the GUI instead of having to go to the DB manually

Improved handling of multi-context Cisco ASA backups:
- if logging in to a multi-context ASA as non-admin, and can't switch to system, just backup the current context
- if transition to the system context is possible, all contexts will automatically be backed up
- single-context ASAs will be backed up as before, the config will just be retrieved

Added support for:
- Fiberstore (FS.com) S2800 series
- Fiberstore (FS.com) S3200 series
- Planet GS switches
- Planet SG switches

Fixes:
Fixed Unimus could consume too much memory when searching if a change happened on devices with large backup histories
Fixed Unimus could consume too much memory (and run out of memory) during DB upgrades on large deployments
Fixed errors in the log when attempting to visit invalid URIs
Fixed closing the Device CLI (new in 2.6.0) could not close the backend session to the device in some cases
Fixed Discovery would fail on devices which disconnect SSH on wrong credentials rather than properly report auth failure
Fixed Discovery failing on Netgear switches with specific firmware versions
Fixed Discovery failing on specific models of Palnet switches
Fixed Discovery failing on 6Wind devices
Fixed Discovery failing on Wi-Tek switches with newer firmware versions
Fixed Backup could fail on Accedian NIDs with specific firmware versions
Fixed jobs failing on Aruba AOS / ProCurve / Provision with enabled security prompts
Fixed jobs failing on Fulcrum switches with enabled pagination
Fixed jobs failing on Positron GAM when hostname was not set
Fixed jobs failing on Grandstream GWN switches

Security fixes:
Disabling MFA now requires the user to enter their password
Added log messages when MFA for user is enabled or disabled
Added log messages when an MFA backup code is used
We have a few minor known issues to be aware of in Network Scan:
Known issues:
ISSUE: During a running Network Scan, the UI within the Scan Preset can be slow to respond
WORKAROUND: none
STATUS: issue scheduled for fixing

ISSUE: Running a Network Scan (even on schedule) with a Zone using a Remote Core that is offline doesn't generate a History Job
WORKAROUND: none
STATUS: issue scheduled for fixing

ISSUE: "Re-discover affected devices when Ports or Connectors change" Advanced Settings option does not work
WORKAROUND: none
STATUS: issue scheduled for fixing

ISSUE: Some screens in Unimus show time in server's time zone, others in client's (browser's) time zone
WORKAROUND: none, issue only relevant if client has different time zone than server
STATUS: we are debating on how to fix this - will likely create a setting to select which TZ should be used
Let us know if you have any feedback / questions on this release, or if you run into any issues!
Post Reply