Unimus 2.0.9 & Unimus Core 2.0.9 release

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

Wed Dec 23, 2020 1:43 am

Unimus & Unimus Core version 2.0.9 are being released today - this is a minor feature & bugfix release.
Links at https://unimus.net/download have been updated with the newest versions.

We had a bunch of new drivers ready and a few easy to merge fixes to the current stable branch, so we are pushing out another release instead of postponing the new drivers until 2.1. This release (2.0.9) should be very stable, and we recommend all customers to update to this release.

Full Changelog:
= Version 2.0.9 =
Features:
Improved debug logs when a job fails due to a runtime error
Updated NetXMS client library to latest version (3.6.314)

Added more detailed logging to Config Push
- available in "debug" level
- https://wiki.unimus.net/display/UNPUB/D ... +Push+jobs

Added support for:
- ADVA MasterOS switches
- Avaya ERS
- Extreme ERS
- Meinberg LANTIME
- MRV MasterOS switches
- Palo Alto Panorama
- Perle IOLAN STS series

Fixes:
Fixed Config Push could not work with Remote Cores (issue introduced in 2.0.6)
Fixed Config Push would sometimes not properly remove pagination (--More--) from outputs
Fixed incorrect config change notifications for dynamic hashes on Aruba Wireless Controllers
Fixed incorrect config change notifications for dynamic hashes on F5 BigIP / BigIQ
Fixed rare incorrect config change notifications for Comware-based devices
Fixed debug options (Debug Mode) not properly resetting to default after restart
Unified formatting of all notification messages (fixed minor inconsistencies)
Fixed some models of Planet Switches not being discovered
Fixed some models of ZyXel IES DSLAMs not being discovered

Resolved issues with special characters being replaced by '?' under specific circumstances
- we fixed various Unimus components which could not properly render special characters
- the DB used by Unimus must also properly support special characters
- https://wiki.unimus.net/display/UNPUB/C ... characters
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.
Alternatively, you can watch the Release Overview video below:



If you are migrating from Unimus v1, please note these migration warnings:
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.

Migration warnings:
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
schedule configuration.

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.
Finally, there are a few low-impact known issues to be aware of:
Known issues:
ISSUE: unable to set Unimus connection timeout in Core - this doesn't influence Core functionality in any way
WORKAROUND: none
STATUS: framework limitation, update to newer framework planned in Q4 2020

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
WORKAROUND: none
STATUS: we are investigating
Post Reply