Table of Contents

General Main Release 10.5.0 CU17

Note

For known issues with this version, refer to Known issues.

Important

Before you upgrade to this DataMiner version:

Tip

Changes

Breaking changes

DataMiner Agents will now translate the primary key to the display key when receiving timeline data requests from a client [ID 45579]

When a client requests timeline data using a GetReportTimeLineDataMessage, it sends the primary key when referencing display column tables. However, for this type of table, the DataMiner Agent has to retrieve the data from the database using the display key.

From now on, when a DataMiner Agent receives a timeline data request, it will first translate the primary key to the display key before returning the requested data.

See also: Dashboards/Low-Code Apps: State timeline component will now use the primary key when requesting timeline data [ID 45600]

Enhancements

Exception.Source field will now be added to ErrorLog.txt when a managed process stops unexpectedly [ID 44722]

When a managed process stops unexpectedly, from now on, the contents of the exception's Source field will now be added to the ErrorLog.txt log file. This should provide more debug information.

GQI will now throw an exception when data is requested from a mediated table parameter [ID 45539]

Currently, because of server limitations, GQI is unable to retrieve parameter table data from DataMiner when that table is a mediated parameter. As a result, when you select a table of a mediated protocol in a client UI, that table will not contain any data, and will also not provide any details on why it does not do so.

From now on, when a query using the Parameters for elements where data source attempts to retrieve data from a mediated table parameter, GQI will throw an error. That error will indicate that the request is not valid because mediated tables are not supported, and will also mention the table or table columns involved.

SLElementInProtocol.txt log file entries will now be added by SLLog instead of SLProtocol [ID 45578]

Up to now, the SLElementInProtocol.txt log file entries were added by SLProtocol.

From now on, these log file entries will be added by SLLog instead.

SLLogCollector will now retrieve the value of the Windows security policy 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' is enabled [ID 45592]

From now on, SLLogCollector will also retrieve the value of the Windows security policy System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

DataMiner does not support having this policy enabled. Having this option enabled will prevent DataMiner from starting up properly.

BPA test 'Cube CRL Freeze': Enhanced performance [ID 45712]

Because of a number of enhancements, overall performance of the Cube CRL Freeze BPA test has increased.

This BPA test will identify client machines and DataMiner Agents without internet access where the DataMiner Cube application experiences a significant freeze during startup. This freeze is caused by the system attempting to verify the application's digital signatures with online Certificate Revocation Lists (CRLs).

Fixes

Up to now, history set trending would show gaps where no gaps were expected.

From now on, trend records with the following iStatus values will no longer cause gaps in trend graphs:

Value Description
-1 Element is starting up.
-2 Element is being paused.
-3 Element is being activated.
-4 Element is going into a timeout state.
-5 Element is coming out of a timeout state.
-6 Element is being stopped.
-9 Trending was started for the specified parameter.
-10 Trending was stopped for the specified parameter.

Visual Overview in web apps: Problem when creating a new window [ID 45517]

Because of the way Cube sessions are loaded in the SLHelper process when creating visual overviews, up to now, Windows could throw an exception creating a new window. This would cause the SLHelper process to crash, affecting all active Cube sessions.

From now on, the system will attempt to recreate the Cube session when the initial creation fails, and will handle any failures gracefully to ensure other sessions remain unaffected.

Cassandra Cluster / STaaS: 'Alarm events' graph on 'Reports' page of service card would incorrectly be empty [ID 45533]

When, in a DataMiner Cube connected to a DataMiner System using Cassandra Cluster or STaaS, you opened the Reports page of a service card, the Alarm events graph would incorrectly be empty, showing "Alarm data not found in the current time range".

SLWatchDog: Problem when restarting DataMiner after SLDataMiner had stopped working [ID 45543]

When SLDataMiner had stopped working, up to now, any attempt made by SLWatchdog to restart the DataMiner Agent would fail.

From now on, when SLDataMiner or any other critical DataMiner process stops working, SLWatchdog will be able to correctly restart the DataMiner Agent.

AssemblyResolveHelper now returns already loaded fallback assembly if it was already loaded [ID 45567]

When the AssemblyResolveHelper in SLCompilationEngine cannot find the exact version of the assembly it has to load, by default, it will try to load an assembly with the same name but a different version.

Up to now, when the assembly with the different version was already loaded in the application domain, the AssemblyResolveHelper would incorrectly return null.

From now on, when the assembly with the different version is already loaded in the application domain, the AssemblyResolveHelper will again correctly return the already loaded assembly.

SLSNMPAgent: Problems due to a locking issue [ID 45586]

Because of a locking issue in SLSNMPAgent, up to now, in DataMiner 10.5.0 Main Release versions starting from DataMiner 10.5.0 [CU8], problems could occur in the following scenarios:

  • When resending (pending) active alarms for stopped/paused elements.
  • When reloading SNMP managers after their configuration had been updated.
  • When handling trap logic when the receiving end was not responding, resulting in a Not acknowledged or Not responding response.

SLWatchDog: Log entry describing a process restart would incorrectly not include the names of the restarted processes [ID 45614]

When SLWatchDog had queued a process restart after having detected that one or more non-critical processes had stop working, up to now, the associated log entry would incorrectly not include the names of the affected processes: Queueing Process Restarts in 1 minute ()

From now on, this log entry will correctly include the names of the processes being restarted. For example: Queueing Process Restarts in 1 minute (SLProtocol.exe)

NATSRepair.exe would incorrectly no longer work on new DMAs installed using DataMiner Installer v10.6 [ID 45636]

The NATSRepair.exe tool would incorrectly no longer work on new DataMiner Agents that had been installed using a DataMiner Installer v10.6.

MessageBroker would not be able to connect to the NATS bus of a DMA when the server name of the DMA was an invalid DNS name [ID 45640]

Up to now, MessageBroker would not be able to connect to the NATS bus of a DataMiner Agent when the server name of that Agent was an invalid DNS name.

From now on, NATSRepair.exe and NATSMigration.exe will now make sure the default MessageBrokerConfig.json file points to localhost instead of the server name.

SLASPConnection could stop working when it failed to retrieve the local IP address [ID 45656]

In some cases, the SLASPConnection process could stop working when it failed to retrieve the local IP address.

Problem when forwarding SNMPv3 traps [ID 45660]

When, within a DataMiner System, a DataMiner Agent receives an SNMPv3 trap for an element hosted by another DataMiner Agent, it will forward that trap to the other Agent. However, in some cases, when the Agent that received the trap did not have the correct credentials needed to decrypt the trap, it would fail to forward the trap to the element.

APIGateway: Problem with reverse proxy feature [ID 45688]

The reverse proxy feature in APIGateway would no longer work.

Whenever a DxM registered itself for reverse proxying, APIGateway could throw an exception.

Problem when synchronizing files in the C:\Skyline DataMiner\Webpages\Public folder [ID 45694]

Up to now, it would no longer be possible to synchronize any files in the C:\Skyline DataMiner\Webpages\Public folder among DataMiner Agents in a cluster because the path name would incorrectly be compared case sensitively.

Improve this page
Advanced search syntax