This is a beta release of version 1.8.0-beta4 intended for testing purposes.
In this release, we have rewritten and upgraded our device discovery implementation.
It will be much faster, consume less CPU, and be more reliable in general.
Another new feature 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.
We test the beta releases as best as possible, but bugs may be present.
For general usage, we recommend customers run current STABLE release.
You can download the Beta build here:
https://goo.gl/PZK4gR
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
Fixes:
Fixed some Brocade, Foundry and Ruckus ICX devices not working when user logged into user-exec mode
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
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 then 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