Links at https://unimus.net/download have been updated with the newest versions.
This release brings quality-of-life features to Mass Config Push, together with a few bug and security fixes. We have added the ability to use Tags with Config Push and a new universal search for push results. Also included are a few bugfixes and a couple of security fixes.
We have also released a blog article that shows the new Config Push features: https://unimus.net/blog/new-config-push ... nimus-2011
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.= Version 2.0.12 & 2.0.13 =
Fixed DB migration failing when upgrading from 1.x.x directly to latest 2.x.x version
Fixed DB migration failing on HSQL if specific Allied Telesis (AlliedWare) devices were present in the system
Fixed jobs failing on Palo Alto and PA Panorama in specific cases
= Version 2.0.11 =
Added support for _ (underscore) as part of hostnames for devices
Updated NetXMS client library to latest version (3.8.166)
Improve system stability when using HSQL database
Free allocated but no longer used disk space on shutdown when using HSQL
New features for Mass Config Push:
- new Omni-Search feature for push results (searches devices, descriptions and / or all push outputs)
- Config Push can now be used with Tags
- New "Targets" feature allowing to specify Tags and / or Devices for Push Preset
- Push Preset will be in read-only mode if user doesn't have access to all devices in the preset
- https://unimus.net/blog/new-config-push ... nimus-2011
Added support for:
- A10 Networks AX series
- Aruba Mobility Conductor
- Aruba Mobility Controller
- more variants of Aruba WLC (7xxx / 72xx / 9xxx)
- Cisco FirePower for VMware
- Datacom routers
- Datacom switches
- more variants of Eltext switches
- Fortinet FortiExtender
- Netgate Appliances with pfSense Plus
- pfSense Plus
Fixed Config Push could pick a wrong device in Output Group "Rerun push" if multiple devices with same address existed in different Zones
Fixed formatting issues with Palo Alto and Panorama output in long lines (200+ characters)
Fixed discovery failing on newer Aruba WLAN controllers
Fixed discovery failing on Eltex MES1xxx series
Fixed a few specific Exinda devices that were failing discovery
Fixed some versions of Cisco Firepower / FTD not being supported
Fixed wrong Config Change Notifications on specific configurations of F5 BIG-IP / BIG-IQ
Fixed users with limited Device Access being able to start a Push even if they didn't have access to all devices in the Push Preset
Fixed deleting a user would not invalidate the user's session if currently logged in, and the deleted user could use some (but not all) features of Unimus until logout or timeout
Alternatively, you can watch the Release Overview video below:
If you are migrating from Unimus v1, please note these migration warnings:
Finally, there are a few low-impact known issues to be aware of: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.
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
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.
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 in progress
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