A summary of what is new:
- Initial multi-language support, added Japanese localization
- Added new APIv3 endpoints, allowing you to get full details of Config Push, NMS Sync, Network Scan presets
- Added a job queuing system for Config Pushes (MCP)
The biggest feature is the new queue mechanism for Config Push / Pull (MCP) jobs. Previously, if multiple Config Push Presets wanted to push to a single device, overlapping jobs to a device were rejected (only a single job can run on a device at a time).
This caused issues with scheduled Push / Pull Presets, if all triggered on the same schedule, all but one were rejected on overlapping devices. Now, instead of rejecting, Unimus will queue any Config Push on a per-device basis, and will execute them on overlapping devices in sequence.
Essentially, only a single job at a time will still run on a device, but concurrent jobs on devices will now be queued rather than rejected. This improves scheduled Config Push / Pull jobs significantly, makes it easier to use run-time state Compliance based on Pull jobs, and much improves the Automation functions of Unimus.
Builds are available for download here:
https://unimus.net/download-dev
Let us know if you have any feedback / questions on this release, or if you run into any issues!= Version 2.10.0 =
Features:
Added bulk Tag management to the Device screen, enabling you to Tag or Un-Tag multiple devices at once (in addition to existing multi-devices tagging in Tags)
Implemented a coordinated job queuing system that prevents collisions between scheduled device-facing operations, which could have caused job rejections previously
Improved manual Retention execution, it will no longer block the UI session, and a proper in-progress visualization was added
Added detailed failure information for failed .csv imports, with exact line numbers for lines that failed to import
Improved Object Access Policy creation by enabling tag assignment during the initial creation process, eliminating the need for a separate edit step
Added "High-security mode" to Credentials in Config Push / Pull (MCP) "Override credentials"
Added "High-security mode" to Credentials / API Keys in all NMS Sync Presets
Improved prompt detection and recognition globally, solving rare ege-cases that could cause issues in jobs or Config Push
If no Notification Sender is enabled, the "Download file" action is now selected by default for Export windows (Backup, Config Search, Compliance)
In NMS Sync, the Panopta / FortiMonitor Aggregator URL can now be edited directly in the GUI
Added support for switching into the Cisco-like CLI (cli / icli) on Ubiqiti UniFi switches (US / USW)
Improved command echo detection globally, solving rare edge-cases in Discovery and Config Push when devices switched modes (user exec -> priv exec -> configure)
Improved model / type detection for Brocade FOS / NOS devices
Improved detection of failed commands with "too many parameters" errors
Added new "Matching mode" settings for Compliance
- New Loose, Sequential and Strict Matching modes for Compliance Conditions
- These allows you to exactly specify what part of config should match / not match your Compliance Condition
- The Strict mode allows you to validate entire configuration blocks
- More information: https://wiki.unimus.net/display/UNPUB/C ... atch+modes
Added options to select Notification granularity for Compliance:
- 3 new settings to select when notifications for Compliance are sent
- You can select between notifications on each Compliance recalculation or only on Preset change
- You can also choose to receive notifications on per-device changes rather than Preset changes
Added initial multi-language (i18n localization) support:
- You can select your language on the Dashboard
- Default language is selected based on Browser locale
- Added Japanese localization, more translations to come soon
New API endpoints and API improvements:
- Added 3 new APIv3 endpoints, allowing you to get full details for Preset-based features
- You can get full details on each Config Push (MCP), NMS Sync and Network Scan preset
- Added per-API-token security toggles for hiding Config Push and NMS Sync credentials in API responses
Multiple concurrent Config Pushes (MCP) to the same device are now queued instead of rejected:
- Previously, if multiple Config Push Presets wanted to push to a single device, overlapping jobs to a device were rejected (only a single job can run on a device at a time)
- This caused issues with scheduled Push / Pull (MCP) Presets, if all triggered on the same schedule, all but one were rejected on overlapping devices
- Now, instead of rejecting, Unimus will queue any Config Push on a per-device basis, and will execute them on overlapping devices in sequence
- Essentially, only a single job at a time will still run on a device, but concurrent jobs on devices will now be queued rather than rejected
- This improves scheduled Config Push / Pull jobs significantly, makes it easier to use run-time state Compliance based on Pull jobs, etc.
Added support for:
- Belden / Hirschmann industrial switches
- Celestica DX010
- Fiberstore (FS.com) GPON OLTs
- NetGear M-series switches (FSM7xxx)
- Yamaha RTX series routers
- Yamaha SWR series switches
- Yamaha SWX series switches
- Zyxel Rugged Switch (RGS) series
Fixes:
Fixed if a .csv file contained UTF-8 BOM characters at the start, it was not possible to import it
Fixed if no Backups existed in Unimus, you could save a Config Search, but could not then modify it
Fixed Config Search with a specified time-range would throw errors if no results existed in that time-range
Fixed a sorting bug when using HSQL DB that cause incorrect column ordering across multiple tables / screens
Fixed changed text reappearing / reverting when expanding Condition text windows in Compliance Conditions
Fixed Basic Import "In progress" state would be lost if changing screens and returning to Basic Import
Fixed could not set Targets in Config Push from Config Search results if the Push was scheduled
Fixed Output Grouping could not properly work in Mass Config Push in specific edge-cases
Fixed extremely long device names would cause Compliance Export HTML to be visually broken
Fixed discovery could fail and report a connection issue instead of UNSUPPORTED_DEVICE in certain edge-cases
Fixed Discovery and Config Push failing on specific BDCOM OLTs