UPDATE: 2.2.3 has been released, and this topic has been locked.
2.2.3 release announcement: viewtopic.php?f=3&t=1508
Unimus 2.2.3-Beta3 is being released today!
The main new feature in this release is a new SSH client library, which brings many new cryptographic algorithms, as well as improving support for new SSH key types and formats. Since this new SSH library affects pretty much everything Unimus does, we wanted to release it into Beta for public testing before we promote it to a Stable release.
Builds are available for download here:
https://unimus.net/download-dev
[BETA] 2.2.3 beta release thread
We just pushed out 2.2.3-Beta2. This includes bugfixes and a few new minor features.
New since 2.2.3-Beta1:
New since 2.2.3-Beta1:
Fixes for issues in Beta1 (none of these apply to current stable builds):Features:
Added a new tooltip which will display all text for text field contents which are shortened when containing very long text
Improved long text label behavior with text fields in "Network Scan", "Config Push" and "NMS Sync"
Performance optimization for "Retention > Keep only last x backup(s)" - the retention cleanup is now much faster
Improved Config Search regex fallback for regex unsupported by the DB engine on PostgreSQL
Improved remote Core connection management and remote Core connection state detection
Added support for:
- Accedian Metronids NIDs
- Transition Networks NIDs
Fixes:
Fixed Config Search with some specific regex modifiers not working on PostgreSQL
Fixed deleting a device while Discovery was running would print errors into the log
Fixed "Admin" user with Device Access restrictions not able to access the System screen
Fixed adding additional entries into the "Network Scan > Subnets" field would reorder entries randomly
Fixed "Add to Unimus" button in "Network Scan" not disabling itself after device was added
Fixed "Network Scan" screen would hang when extremely large data was pasted into the Search box
Fixed missing spinner in resources
Fixed jobs failing with "Timed out" error when very large job requests were submitted to a remote Core
Fixes:
Fixed Config Push not working in 2.2.3-Beta1
We just pushed out 2.2.3-Beta3. This has a larger change-set (changes since Beta2) and we are aiming for 2.2.3 to go to GA by the end of the month.
New since 2.2.3-Beta2:
New since 2.2.3-Beta2:
Full Changelog for 2.2.3 is updated in the top post.Features:
Added support for syncing device manage state from Zabbix ("status" field)
Improved search behavior (search triggering will now be less aggressive and not stop you during typing)
Improved the input behavior for the "Subnets" input box in "Network Scan"
Credentials and CLI Mode Change Passwords are now searchable by "Used by" counts
Improved explanation text in Config Push output groups when devices failed to switch to Enable / Configure mode
Added support for devices with "User ID:" prompt during login
Added support for config sections on ArubaOS-CX
Performance improvements:
- added additional new thread pools to multiple parts of the system
- improved thread management, threads are now reused where possible instead of spawning new threads
- this improves performance, decreases total lifetime threads spawned by Unimus
- also solves issues in environments where the OS thread and/or PID limits are low
Added support for:
- 6Wind Virtual Service Router (VSR)
- netElastic vBNG
Fixes:
Fixed some Cisco SMB switches could not be discovered (reported as Unsupported Device)
Fixed Configure Mode could not have been discovered on devices during Discovery in rare cases
Fixed during SSH negotiation only LF would be sent in ID string, some devices would complain about this
Fixed Config Push results could fail to send to server from Core in rare cases
Fixed Config Push could require escaping "$" even when it was not being used for a variable declaration
Fixed a trailing prompt could be present in a MikroTik RouterOS backup
Fixed a trailing prompt could be present in Config Push output for a MikroTik RouterOS device
Fixed Config Push output grouping could not work for MikroTiks in multiple cases
Fixed discovery failing on Arista switches when specific prompt was used
Security fixes:
Fixed wrong IP address reported for user at login (only login was affected, all other screens reported IPs for user correctly)
Fixed currently opened "Device Tags > Tag devices" and "Device Tags > Un-tag devices" window still working if user lost access to the device