Table of Contents

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

BPA test 'Large Alarm Trees' will now run on a daily basis [ID 44565]

From now on, the Large Alarm Trees BPA test will run on a daily basis, and will now generate an error or a warning in the following cases:

  • It will generate an error when there is at least one alarm tree that consists of 5000 or more alarms. Only the alarm trees that have reached this size will be returned in the detailed result.

  • It will generate a warning when there is at least one alarm tree that consists of 1000 or more alarms, but all alarm trees have less than 5000 alarms. Only the alarm trees that have reached this size will be returned in the detailed result.

Also, no notice will be generated anymore when alarm trees are getting large. As a result, in the AlarmSettings section of the MaintenanceSettings.xml file, the recurring attribute of the AlarmsPerParameter element is now obsolete.

Security enhancements [ID 44579]

A number of security enhancements have been made.

SLDataGateway: StorageTypeNotFoundException will now always mention the StorageType that could not be found [ID 44603]

When SLDataGateway throws a StorageTypeNotFoundException, from now on, the message will always mention the StorageType that could not be found.

An updated parameter value will no longer be written to the database if it is equal to the old value [ID 44609]

When a user or a QAction updated a parameter value, up to now, the new value would always be written to the database, even when the new value was equal to the old value.

From now on, when the new value is equal to the old value, the value will no longer be written to the database. If any triggers or QActions are configured to be executed following a parameter update, these will still be executed.

Also, write parameters will no longer be saved as this would cause unnecessary load.

Enhanced distribution of SNMPv3 traps [ID 44626]

When a DMA receives an SNMPv3 trap that it cannot process (e.g., because the SNMPv3 user is unknown), and trap distribution is enabled, from now on, the trap will be distributed to the other DMAs in the cluster in an attempt to have it processed by one of those other DMAs.

Also, in some cases, traps could be forwarded to the wrong elements because the SNMPv3 USM ID was not validated correctly.

Enhanced performance when filtering history alarms using complex filters [ID 44664]

Because of a number of enhancements, overall performance has increased when filtering history alarms using complex filters.

Performance has especially increased using filters that consist of multiple equality conditions involving the following types of objects:

  • Element
  • Function
  • Protocol
  • Service
  • View
Note
  • Non-equality and wildcard/regex filtering has not been altered.
  • If more than 1,000 elements are affected, filtering will revert to the legacy behavior.

Enhanced performance when executing a full element update on STaaS systems with Swarming enabled [ID 44772]

Because of a number of enhancements, on STaaS systems with Swarming enabled, overall performance has increased when executing a full element update.

Fixes

Problem with SLNet when receiving a subscription with a large filter that contained wildcards [ID 44512]

When SLNet received a dynamic table subscription with a very large filter that contained wildcards, up to now, it would throw a stack overflow exception and stop working.

From now on, SLNet subscriptions will now be blocked when they contain a filter that exceeds 140,000 characters.

SLNetClientTest tool: External authentication would not work when the Microsoft Edge (WebView2) browser engine was installed on a per user basis [ID 44583]

When you connected to a DataMiner Agent, up to now, it would not be possible to use external authentication from a client computer on which the Microsoft Edge (WebView2) browser engine was installed on a per user basis.

Note

When the Microsoft WebView2 browser engine is installed on a per user basis, it will be automatically updated each time you open Microsoft Edge.

Caution

Always be extremely careful when using the SLNetClientTest tool, as it can have far-reaching consequences on the functionality of your DataMiner System.

Data would not show up in DVE child elements due to a problem with foreign key linking to logger tables [ID 44651]

In some cases, a problem with foreign key linking to logger tables would cause data to not show up in DVE child elements.

Alarm properties passed along by Correlation or SLAnalytics could get lost when an alarm was created [ID 44669]

In some cases, alarm properties passed along by Correlation or SLAnalytics could get lost when an alarm was created.

API Gateway would incorrectly add multiple routes with the same basePath when multiple registration requests were received for the same route [ID 44676]

When multiple registration requests were received for the same route, in some cases, instead of updating the route, API Gateway would incorrectly add multiple routes with the same basePath. As a result, the proxy would not be able to route the HTTP request.

Failover: Two Agents in a Failover pair could get stuck during startup [ID 44680]

In some cases, the two Agents in a Failover pair could get stuck during startup.

Scheduler: Windows task will no longer be recreated when only the actions of a scheduled task were changed [ID 44691]

When a scheduled task was updated close to its execution time, in some cases, the task would incorrectly not be executed. It would miss its execution window because, during the update, the Windows task would be deleted and recreated again.

From now on, when only the task actions are changed during an update of a scheduled task, the Windows task will no longer be recreated. The latter will only be recreated when the status, name, description, or timing of the scheduled task are changed.

Problem with SLNet when rolling over log files [ID 44711]

In some cases, SLNet could stop working when rolling over from one log file to another (e.g., from SLNet.txt to SLNet0.txt).

From now on, when an issue occurs when rolling over log files, an error will be logged in the Windows Event Viewer.

Note

Some logging may get lost because of this fix.

BrokerGateway installation could fail when the nsc.exe file was locked by an antivirus application [ID 44721]

Up to now, a BrokerGateway installation could fail when the nsc.exe file was locked by an antivirus application.

From now on, a locked nsc.exe file will no longer cause a BrokerGateway installation to fail.

Problem with SLAnalytics during the storage initialization routine [ID 44745]

In some rare cases, the SLAnalytics process could stop working during the storage initialization routine.

Problem with SLAnalytics when trying to process an invalid database record [ID 44748]

In some cases, SLAnalytics would stop working when trying to process an invalid database record after having serialized it.

Problem when an alarm was updated while a hysteresis timer was scheduled [ID 44749]

When an alarm was updated while a hysteresis timer was scheduled, in some cases, the timestamp of the alarm update would be more recent than that of the alarm generated by the clear hysteresis. As a result, the state changes timeline would no longer be correct.

Problem with SLProtocol when multiple connections of the same element went into a timeout state simultaneously [ID 44752]

In some rare cases, SLProtocol could stop working when multiple connections of the same element went into a timeout state simultaneously.

SLLogCollector: Problem when process dumps were triggered in parallel [ID 44780]

Up to now, when SLLogCollector tried to trigger process dumps in parallel, in some cases, certain dumps would not be added to the package.

From now on, in order to be able to include all dumps in the package, process dumps will no longer be triggered in parallel.

Incorrect error message would appear when a configuration mismatch prevented DataMiner Agents from being clustered [ID 44781]

When a configuration mismatch prevented DataMiner Agents from being clustered, up to now, the following incorrect error message would appear:

Cannot cluster Agents as remote Agent has an unsupported database type.

From now on, the following correct error message will appear instead:

Cannot cluster Agents as the agent configuration is incompatible. Please check SLNet logging for more information.

STaaS: Retrieving the active alarms of an element would incorrectly be limited to 10,000 [ID 44793]

Up to now, if an element had more than 10,000 active alarms, on STaaS systems, only the first 10,000 would incorrectly be retrieved.

From now on, all active alarms will be retrieved, even if the element in question has more than 10,000 active alarms.

Improve this page