Table of Contents

General Feature Release 10.5.3 – Preview

Important

We are still working on this release. Some release notes may still be modified or moved to a later release. Check back soon for updates!

Important

Before you upgrade to this DataMiner version, make sure version 14.40.33816 or higher of the Microsoft Visual C++ x86/x64 redistributables is installed. Otherwise, the upgrade will trigger an automatic reboot of the DMA in order to complete the installation.

The latest version of the redistributables can be downloaded from the Microsoft website:

Tip

Highlights

No highlights have been selected yet.

New features

No new features have been added yet.

Changes

Breaking changes

Protocols: Separate SLScripting process for every protocol used [ID 41713]

From now on, DataMiner will by default start a separate SLScripting process for every SLProtocol process.

Up to now, if you wanted to have separate SLScripting processes created for every protocol being used, you had to explicitly configure this in ProcessOptions element of the DataMiner.xml file. See the example below.

<DataMiner>
  <ProcessOptions protocolProcesses="protocol" scriptingProcesses="protocol" />
</DataMiner>

If you only want a single SLScripting process for all protocols that are used, then set the scriptingProcesses attribute to "1".

Enhancements

Security enhancements [ID 40632]

A number of security enhancements have been made.

Protocols: New 'overrideTimeoutVF' option to override the timeout for a Virtual Function [ID 41388]

Up to now, when the overrideTimeoutDVE option was enabled in a protocol.xml file, the timeout would apply to DVE elements as well Virtual Functions.From now on, this option will only apply to DVE elements.

In order to override the timeout for a Virtual Function, you will now be able to specify the new overrideTimeoutVF option in a Functions.xml file.

Enhanced error and exception handling when updating or clearing correlation alarms [ID 41675]

Error and exception handling has been enhanced in order to prevent duplicate or sticky correlation alarms due to errors or exceptions thrown when updating or clearing correlation alarms.

Amazon Keyspaces Service is now end-of-life [ID 41874] [ID 41914]

Support for Amazon Keyspaces Service is now officially end-of-life.

When you run the DataMiner installer or install a DataMiner upgrade package, the VerifyNoAmazonKeyspaces prerequisite will check whether the DataMiner Agent is configured to use a database of type Amazon Keyspaces. If so, the upgrade process will not be allowed to continue.

We recommend using Storage as a Service (STaaS) instead. If you want to use self-hosted storage, install a Cassandra Cluster database.

For more information, see Amazon Keyspaces Service

SLLogCollector now collects data regarding the GQI DxM [ID 41880]

SLLogCollector packages now include the following data regarding the GQI DxM:

  • appsettings.json
  • Log file
  • Version

SLLogCollector packages now also contain the ClusterEndpoints.json file [ID 41887]

SLLogCollector packages now also include the ClusterEndpoints.json file.

Fixes

Elements no longer visible after having been swarmed [ID 41635]

In some rare cases, when an element had been swarmed, it would no longer be visible in client apps like DataMiner Cube.

Missing DATAMINER_NOTIFICATION_QUEUE thread [ID 41699]

When DataMiner was restarted, an issue could occur, causing the DATAMINER_NOTIFICATION_QUEUE thread not to be registered in processes like SLDMS, SLElement or SLDataGateway. These missing threads could then lead to a number of symptoms like empty element data cards or not being able to swarm back elements.

Problem with incorrect virtual element states [ID 41705]

In some rare cases, the element state of a DVE or Virtual Function element would end up incorrect in the SLNet cache, causing some caches to not be initialized correctly.

Problem when trying to swarm an element back to its original DataMiner Agent [ID 41709]

In some cases, it would not be possible to swarm an element back to its original DataMiner Agent due to a caching issue in the SLDataMiner process.

Problem with SLDataMiner when a DMS with swarming enabled had a database connection issue at start-up [ID 41714]

When, while starting up, a DataMiner System with swarming enabled experienced a problem with its database connection, the SLDataMiner process would incorrectly shut down.

Service & Resource Management: Problem when a previously deleted booking was created again [ID 41718]

When a previously deleted booking was created again with the same ID, up to now, that booking would incorrectly not be retrieved.

GQI: Min and Max aggregation of a datetime column would incorrectly result in a number column [ID 41789]

Up to now, when a Min or Max aggregation was performed on a datetime column, the aggregated column would incorrectly be a number column instead of datetime column.

Uploading the same version of a DVE connector twice would incorrectly cause the production version of DVE child elements to be changed [ID 41798]

When the same version of a DVE connector was uploaded twice, the production version of all DVE child elements using another version of that connector as production version would incorrectly have their production version set to the newly uploaded version.

SNMP managers would incorrectly receive some or all active alarms at DMA start-up [ID 41878]

When a DataMiner Agent was started, in some cases, the configured SNMP managers would incorrectly receive some or all active alarms.

Fixes made with regard to the management of locally-stored element documents [ID 41882]

A number of fixes have been made with regard to the management of locally-stored element documents that are not synchronized among the DMAs in a DataMiner System.

Problem when swarming elements between two DMAs with a time difference [ID 41910]

When elements were swarmed between two DataMiner Agents, in some rare cases, a problem could occur when there was a time difference between both agents.

Propose changes