Unimus 2.0.8 & Unimus Core 2.0.8 release

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

Thu Nov 12, 2020 7:25 pm

Unimus & Unimus Core version 2.0.8 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 originally planned 2.0.6 to be the last release in the v2.0 code branch, but after some internal discussion we are releasing one more version in the 2.0 branch. 2.0.8 should be very stable, and we recommend all customers update to this release.

Full Changelog:
= Version 2.0.8 =
Hotfix release - Fixed jobs failing on HP/HPE/Aruba ProVision/ProCurve/ArubaOS

= Version 2.0.7 =
Failed and successful login log messages now include the IP of login attempt
Login log messages now support proxy headers to properly report login attempt IP address
Added support for devices which ask "Press any key to continue" twice in a row during login
Added support for devices which expect a key press to continue ("Press CTRL+Y to continue"), and then output a banner
Added support for devices which output a custom message and ask for confirmation ("Accept (y/n)?")
Added support for devices which ask "Do you want to change expired password?" during login
Default inter-connection delay value increased to 500ms

Added support for:
- Aviat WTM4200 Radios
- Dell X series switches
- Fortinet FortiWLC
- FreeNAS
- IBM RackSwitch
- InfoBlox
- Mellanox InfiniBand switches
- Perle IOLAN
- TrueNAS
- Ubiquiti EdgeSwitch 10X

Fixed Unimus stuck on "License synchronization error" screen, which required Unimus restart
Fixed Unimus not reconnecting to the DB if the DB server went down until a user tried to log in
Fixed newly imported devices not being scheduled for jobs if there were not devices in Unimus before import
Fixed newly created credentials not being used in discovery when "Rediscovered unknown devices when new credentials are added" is enabled
Fixed unprintable characters in email notifications
Fixed wrong config change notifications on Nokia TimOS/SROS with bof ("show bof" possible)
Fixed more possible wrong Config Change notifications on FortiOS (FortiGate, etc.)
Fixed minor UX issues in the Deployment Wizard, Config Search and NMS Sync
Fixed Telnet credential discovery not testing any other credentials after the first failed credential
Fixed 3COM/HP/HPE ComWare devices not being discoverable if prompt contained only numbers
Fixed specific unprintable characters being saved as part of backups
Fixed OPNsense not discovering under specific circumstances (prompt contained tab)
Fixed more Foundry/Brocade switches not discovering on specific hardware types
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:
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
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
STATUS: we are investigating

ISSUE: special characters can be replaced by '?' under specific circumstances
STATUS: currently no ETA, framework limitations
User avatar
Posts: 1239
Joined: Sat Jun 25, 2016 12:33 pm

Mon Nov 16, 2020 7:51 pm

Small update:
We have released a hotfix for issues with HP/HPE/Aruba ProVision/ProCurve/ArubaOS as 2.0.8
Post Reply