[BETA] 2.4.0 beta release thread

[Tomas]

UPDATE: 2.4.0 has been released, and this topic has been locked.
2.4.0 release announcement: viewtopic.php?f=3&t=1701

Unimus 2.4.0-Beta5 is being released today! This is a release of the 2.4 code branch intended for testing purposes. More info on what's to come next on the Roadmap.

This Beta contains the changes to Config Push behavior modifiers, and introduces new behavior modifiers and actions into Config Push. Full info available in this forums post. A a near-complete rewrite of NMS Sync is also ready, which was one of the most complex features we have in a long time. A few bugfixes for issues found since 2.3.3 are also included.

Builds are available for download here:
https://unimus.net/download-dev

[Tomas]

We just pushed out 2.4.0-Beta2. The complete Changelog was updated in the first post. New since 2.4.0-Beta1:

Features:
Added a built-in backup filter for new timestamp format in MikroTik RouterOS v7.10
Improved handling of errors for Zones which use a NetXMS Agent as the Zone's proxy
If a DNS lookup for a device hostname fails, this will now be reported as an exact job failure reason
Added support for session restoration prompts after login (for example on Cisco ISE)
Added the possibility to override the SSH version validation timeout (new "unimus.core.ssh-version-validation-timeout" setting)
Improved handling of quoted string on MikroTik RouterOS v7
Improvements to the CLI mode change algorithm (better handling of specific edge cases)

Added support for:
- more variants of the Aruba Mobility Controller
- TRENDnet TI switches

Fixes:
Fixed for Zones which use a NetXMS Agent as a proxy all tasks within a job would fail if a single tasks failed
Fixed various minor UI and UX issues and inconsistencies
Fixed jobs on specific Moxa switch types could randomly fail
Fixed discovery would fail for specific versions of the Aruba Mobility Controller
Fixed sporadic config change notifications on MikroTik RouterOS v7

Migration warnings:
On MikroTik RouterOS v7, you can get a single config change notification due to changes in how quoted strings
are handled in our ROSv7 driver. This config change should only happen on the first backup job after upgrade
and can be ignored.

[Tomas]

We just pushed out 2.4.0-Beta3. The complete Changelog was updated in the first post. New since 2.4.0-Beta2:

Features:
Added support for devices which don't respond to the none SSH auth method.
Added support for output termination in newer versions of VyOS
Added support for Linux shell login on netElastic vBGN
Added support output termination in paged output on netElastic vBGN

APIv2 improvements:
- add optional query param to select zone for "api/v2/devices/findByAddress" endpoint
- add option to specify Zone for the "createDevice" endpoint at "api/v2/devices"

Added support for:
- Cambium cnPilot
- improved netElastic vBGN support
- Radware Alteon

Fixes:
Fixed elements in combo box sometimes appearing multiple times in multiple screens across the application
Fixed elements in combo box sometimes missing in multiple screens across the application
Fixed jobs using Telnet could randomly fail
Fixed jobs on newer versions of VyOS failing
Fixed login failing on specific Palo Alto devices

Fixes for issues in Beta2 (none of these apply to current stable builds):

Fixes:
Fixed MikroTik backups being corrupted

[Tomas]

We just pushed out 2.4.0-Beta4. The complete Changelog was updated in the first post. New since 2.4.0-Beta3:

Features:
Improved support for logins to JunOS in BSD mode

Fixes:
Fixed discovery would fail on JunOS devices with specific BSD prompt format
Fixed Remote Core would not be able to reconnect to the Server in specific cases
Fixed Remove Core connections could be considered still alive even after the connection was closed

Fixes for issues in Beta3 (none of these apply to current stable builds):

Fixes:
Fixed jobs on HP(E) ProCurve / ProVision / ArubaOS would fail
Fixed more cases where MikroTik backups could be corrupted

[Tomas]

2.4.0-Beta5 is finally out! This includes a near-complete rewrite of NMS Sync, which was one of the most complex features we have in a long time.

Current plan is to focus on stability testing and minor improvements only, with 2.4.0 going stable in around 3 weeks (most likely 1st week of December).

The complete Changelog was updated in the first post. New since 2.4.0-Beta4:

Features:
Updated NetXMS client library to latest version (4.4.3)
Added filtering of log messages inside Cisco SMB switch backups
Improved login banner recognition logic, more banner types are now supported
Added support for multi-partition backup on F5 devices
Improved support for Adtran NetVanta devices
Added support for paginated output on Accedian devices
Added support for backup multipliers in the Cisco WLC driver

Major improvements to NMS Sync:
- Devices no longer present in NMS can now be automatically Unmanaged / Deleted in Unimus
- Improved tracking of which local device corresponds to which NMS device, allowing to move devices locally when they are moved in the NMS
- If a device is not found locally in the target Zone, you can now specify if Unimus looks for a candidate to move into a Zone, or creates a new device
- Allow specifying what scope Unimus searches in for move candidates when trying to move devices across Zones
- Fixed multiple issues that arose in setups where multiple NMSes were being imported into the same Zone
- more info soon on https://blog.unimus.net

Improvements to the Zabbix NMS Sync connector:
- Added support for importing from Templates and Tags on top of existing options
- Introduced new prefixes for various import sources: %template_name; @tag_name
- existing Sync Presets should be migrated automatically, and continue working as expected
- full documentation: https://wiki.unimus.net/display/UNPUB/Zabbix+importer

Added support for:
- Adtran NetVanta chassis
- ADVA FSP 1xx series
- AricentOS devices
- Casa vCCAP
- Cisco Catalyst 1200 series switches
- Cisco ISE
- ComNet Switches (based on CNGE11FX3TX8MS)
- EdgeCore 7316
- EdgeCore CSR320
- Ericsson IPOS (SSR series)
- Ericsson SGSN
- F5 multi-partition
- Grandstream GWN7800 series switches
- Opengear Operations Manager
- Westermo L110
- Westermo Lynx-5512
- Westermo RedFox-5728
- Westermo WeOS

Fixes:
Fixed inter-connection delay was not applied for Telnet service availability check
Fixed logs present in backups on Cisco SMB switches (would trigger new change-points and change notifications on every backup)
Fixed inter-connection delay was not applied for NetXMS TCP proxy connections
Fixed Credential usage could be counted twice if a credential was used for both for SSH and Telnet (Credential > Usage screen)
Fixed CLI Mode Change password usage could be counted twice if a credential was used for both for SSH and Telnet (Credential > Usage screen)
Fixed login to devices could fail if certain login banners were used
Fixed specific commands on Aruba Mobility Controller (ArubaMM) could cause a Config Push to fail
Fixed backups could fail on Cisco WLC under heavy load, or with very large configs
Fixed jobs on Cambium 450i would always fail
Fixed jobs on specific Accedian devices would fail
Fixed jobs on specific Adtran NetVanta devices would fail