This is a bugfix release for the 2.0 branch, with included support for LibreNMS.
Links at https://unimus.net/download have been updated with the newest versions for Unimus & Core.
In case you missed it, we have published a 2.0 Release Overview on our blog if you want to read up on this release.= Version 2.0.5 =
Added LibreNMS import connector (NMS Sync)
Swapped backup range dates in Backups for easier navigation
Historic Config Search now shows newest backups at the top
Email notification sender with enabled TLS/SSL now requires TLS/SSL
Added support for devices that include a command counter in device prompt
Fixed email notifications stopped working if email server didn't respond to outbound email
Fixed Config Push notifications not working when Network Scan notifications were disabled
Fixed broken pagination in Unimus API
Fixed historic Config Search not showing full backup range (only showed first backup retrieval time)
Fixed wrong Config Change notifications on Nokia TiMOS
Config Push will no longer force pagination on commands (fixes issues on Vyatta / VyOS and others)
Fixed Citrix NetScaler not discovering on certain OS versions
Fixed Cambium ePMP discovery not working (again...)
Fixed Nokia OmniSwitch backup failing
Alternatively, you can watch the Release Overview video below:
If you are migrating from Unimus v1, please note these migration warnings:
Finally, there are a few low-impact known issues to be aware of:Important:
Slack integration has been migrated from a Webhook to a Slack App. Your Slack notifications will not work without reconfiguration. Manual migration and reconfiguration is required.
Slack integration has been migrated from a Webhook to a Slack App. This is due to the addition of sending Configuration
Change Notifications over Slack. The Webhook API did not support sending Snippets, which Config Notifications require.
You will need to setup a new Slack App for Unimus, and reconfigure Unimus Slack sender in "Notifications > Slack".
Weekly schedules were running one day earlier than configured. We have migrated existing schedules to the day they were
running on - which was different than what was configured. If you were using weekly schedules, please review your
For some devices, there may be a single config-change notification after the first backup following the 2.0.0 upgrade.
This will show a change occurred inside a comment or a non-config line. This is expected due to changes to the dynamic
(runtime) backup content filtering mentioned in the "Features" section. This is caused by changes to what Unimus
considers as dynamic (runtime) data inside backups, and you can safely ignore this change notification.
ISSUE: unable to set Unimus connection timeout in Core - this doesn't influence Core functionality in any way
STATUS: framework limitation, update to newer framework planned in Q3 2020
ISSUE: when you delete the "Device Output Log" file in "Debug mode", any jobs that started before deletion, but finish after
deletion will recreate the file and write their output to the file
WORKAROUND: delete "Device Output Log" after all jobs finish / no jobs are running
STATUS: issue scheduled for fix in 2.0.6
ISSUE: with higher latency, when writing text into an input box, a desync may occur that causes a character to get lost,
and the cursor to jump to the start of the input box
STATUS: we are investigating
ISSUE: special characters can be replaced by '?' under specific circumstances
STATUS: currently no ETA, framework limitations