Table of Contents

General Main Release 10.5.0 CU11 - 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!

Tip

Enhancements

Security enhancements [ID 43789]

A number of security enhancements have been made.

OpenSearch: Enhanced health monitoring [ID 43951]

A number of enhancements have been made with regard to health monitoring of OpenSearch databases.

Also, all logging with regard to OpenSearch health monitoring can now be found in SLSearchHealth.txt. Up to now, that logging was added to SLCassandraHealth.txt.

Note that, from now on, if not all nodes of the OpenSearch cluster are listed in the Db.xml file, a notice will be generated to warn operators.

Enhanced performance when upgrading DxMs [ID 44210] [ID 44211]

Because of a number of enhancements, overall performance has increased when the following DxMs are upgraded during a DataMiner upgrade:

  • BrokerGateway
  • StorageModule

Fixes

Not possible to export elements with logger tables on systems with Cassandra Cluster and OpenSearch [ID 44105]

On a system with Cassandra Cluster and OpenSearch, up to now, it would incorrectly not be possible to export elements with logger tables.

A Cassandra.InvalidQuery exception with message "No keyspace has been specified" would be thrown and logged.

Note

On a system with Cassandra Cluster and OpenSearch, it is currently not yet possible to export SLAs.

Problem when generating a default MessageBrokerConfig.json file [ID 44155]

When neither an SLCloud.xml file nor a MessageBrokerConfig.json file could not be found on a DataMiner Agent, up to now, any process using MessageBroker would fail to generate a default MessageBrokerConfig.json file. As a result, it would not be possible to connect to NATS.

From now on, when neither a SLCloud.xml file nor a MessageBrokerConfig.json file can be found, a default MessageBrokerConfig.json file will be generated.

Elements hosted on another DMA and under the root view would not be visible if you did not have full access to the root view [ID 44170]

In client applications like DataMiner Cube, up to now, elements hosted on a DMA other than the one you were connected to would incorrectly not be visible in the Surveyor if they were directly under the root view and if you did not have full access to that root view.

Uploading certain protocol versions would cause elements to no longer be able to execute QActions [ID 44172]

After you had uploaded a protocol with a version that was identical to the prefix of the version of a protocol that was already in use (e.g. a new protocol with version 1.0.0.1 versus an existing protocol with version 1.0.0.1_DEV), up to now, elements using the existing protocol (e.g. with version 1.0.0.1_DEV) would incorrectly no longer be able to execute QActions.

Problem with SLElement when loading elements that included matrix parameters [ID 44188]

In some cases, SLElement could stop working when loading elements that included matrix parameters.

Up to now, in some cases, issues related to certificates could cause TLS handshake error: remote error: tls: bad certificate errors to be added to the NATS log file and Could not connect to the local NATS endpoint on '<IP>'. Please make sure that the nats service is running without issues. notice alarms to be generated.

From now on, in order to prevent any issues related to certificates, in the following cases, the certificate authority will be either added or updated in the certificate store:

  • When adding an agent to the cluster.
  • When removing an agent from the cluster.
  • When calling NATSRepair.
  • When migrating to BrokerGateway.
  • When no certificate authorities can be found during BrokerGateway startup.

STaaS: Problem when migrating or importing elements with logger tables [ID 44196]

On systems using STaaS, when an element with logger tables had been migrated from one DMA to another, up to now, that element would no longer start up after it was migrated back to its original DMA.

Also, on system using STaaS, up to now, when importing a DELT package containing elements with logger tables, the logger table data would not be imported correctly.

No retries would incorrectly be attempted when retrieving DMS configuration info failed [ID 44240]

When a client application connects to a DataMiner System, it retrieves the configuration info of that DataMiner System.

Up to now, when retrieving that info failed, no retries would incorrectly be attempted. From now on, a retry will be attempted every 10 seconds.

Improve this page