Unimus 1.8.0 release

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

Tue Jun 19, 2018 6:45 pm

Unimus version 1.8.0 is being released today!



This release brings 3 new major features:
- configuration change notifications
- multi-device edit
- Radius authentication improvements

Main new feature of this release are Configuration Change Notifications.
Unimus will now send you a notification when it detects a change in the config of any of your devices.

We have also added support for defining Access Roles and Access Tags to Radius accounts.

Last but not least, we have implemented multi-device edit, so binding credentials (or doing other bulk changes) is much easier.

MIGRATION WARNING:
Radius accounts must now be created in Unimus, and have their authentication method set to Radius.
If you are migrating from previous versions and use a Radius account to log in to Unimus, you must first create then account in Unimus and properly set its auth method. Use a local admin account to create this Radius account.

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

Direct upgrade from 1.x.x 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.8.0 =
Features:
Added multi-device Edit - edit schedule, bound credentials and enable/configure passwords on several devices at once
Added support for additional crypto / hashing / DH algorithms - adds compatibility with more devices
Improved handling of failed Enable / Configure mode switch during discovery
Improved model detection for Fiberstore / GCOM switches
Cosmetic improvements to "Access Tags" screen

Added configuration change notifications:
- a notification will be sent when Unimus detects a config change on a device
- enabled by default, configurable in the "Notifications" screen

Improvements to the "Mass config push" feature:
- Improved detection of yes / no ("[Y/N]") prompts in "Mass config push"
- Improved "Mass config push" compatibility with slow devices

Performance improvements:
- Improved the speed of Discovery, Backup and Mass Config Push processes
- General improvements and optimizations for connections to older / slow devices
- CPU utilization improvements - optimized many aspects of device communication

Changed how Radius user authentication is handled:
- Radius accounts now have to be defined as local application accounts, with auth method set to Radius
- Added support for specifying an Access Role for Radius accounts
- Added support for tagging Radius accounts with Access Tags

Added support for:
- Araknis switches
- Dell EMC OS10
- Dell switches (OS10)
- HP BladeSystem OA
- Huawei Quidway switches
- Ruckus standalone APs
- More variants of ZTE ZXR10

Fixes:
Fixed some Brocade, Foundry and Ruckus ICX devices not working over Telnet
Fixed not properly stripping pagination from backups of some Cisco WLCs
Fixed errors during Discovery in various edge-cases when using SSH
Fixed not setting reverse DNS as device description with automatic device addition from Network scan
Fixed failing discovery on devices that didn't exit out of "Password: " prompts after CTRL+C
Fixed re-discovery not being triggered in certain cases when connector configs change
Fixed wrongly showing a successful notification in the GUI when a backup actually failed
Fixed discovery could sometimes report wrong Vendor / Type for some devices
Fixed Audiocodes devices not being discovered / backed up when there was no previous login
Fixed a very rare case of discovery failing when adding/removing same device
Fixed unable to add schedules in the deployment wizard
Fixed echo messages being retrieved as a part of the backup on MikroTik RouterOS in rare cases

Tickets closed by this release:
UN-252, UN-299, 317, UN-328,

Migration warnings:
Radius accounts must now be created in Unimus, and have their authentication method set to Radius.
If you are migrating from previous versions and use a Radius account to log in to Unimus, you must
first create that account in Unimus and properly set its auth method. Use a local admin account
to create this Radius account.

Known issues:
Special characters can be replaced by '?' under specific circumstances
Post Reply