Table of Contents

General Main Release 10.5.0 CU8

Note

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

Tip

Enhancements

Element replication: Replication buffer will now be read in chunks [ID 43281]

Up to now, when the connection to a replicated element was restored, the entire replication buffer would be read into memory at once. From now on, the replication buffer will be read in chunks.

DataMiner Object Models: Enhanced performance when filtering on FieldValues in memory via FilterElements [ID 43568]

When filtering on FieldValues in memory via FilterElements, the DomInstanceExposers.FieldValues exposer will no longer generate a JsonSerializableDictionary. Instead, it will now use a standard dictionary. This will enhance overall in-memory filtering performance.

STaaS: Enhanced exception logging [ID 43626]

A number of enhancements have been made with regard to the logging of exception messages on STaaS systems.

DxMs upgraded [ID 43642]

The following DataMiner Extension Modules (DxMs), which are included in the DataMiner upgrade package, have been upgraded to the indicated versions:

  • DataMiner SupportAssistant 1.7.7

For detailed information about the changes included in those versions, refer to the DxM release notes.

CPE: Enhanced performance [ID 43654]

Because of a number of enhancements in the aggregation module, overall performance has increased.

STaaS: A failure notice will now be returned immediately when an operation could not be sent to STaaS [ID 43667]

Up to now, when DataMiner was not able to send an operation to STaaS, it had to wait until the write operation timed out before it got confirmation that the operation had failed.

From now on, when DataMiner tries to send an operation of which the size exceeds the maximum package limit to STaaS, a failure notice will be returned immediately.

DataMiner upgrade: All but the Web.config file will be removed from the 'C:\Skyline DataMiner\Webpages\API' folder when downgrading to an older version [ID 43687]

From now on, when a DataMiner Agent is downgraded to an older version, the entire C:\Skyline DataMiner\Webpages\API folder will be cleared. Only the Web.config file will be kept.

SLLogCollector packages now also include the Web DcM log files [ID 43716]

SLLogCollector packages now also include the log files of the Web DcM.

Fixes

Problem when loading initial parameter data for remote elements [ID 43339] [ID 43552]

In some cases, client applications like DataMiner Cube would fail to load initial parameter data for remote elements.

Protocols: Problems with pollingRate attribute [ID 43418]

A number of issues have been fixed with regard to the pollingRate attribute, which allows you to slow down polling for specific SNMP columns in a table by specifying a minimum interval (in milliseconds) between polling.

  • Using pollingRate would not work when the element was using the production version of the protocol or when the partialSNMP option was specified in the table options.

  • Up to now, the decision to poll a column was taken by SLSNMPManager, which relied on the Polling.xml file that was stored alongside the Protocol.xml file. From now on, SLProtocol will determine which columns will be polled independently of the Polling.xml file.

Note

Stream Viewer will now indicate more clearly which columns were polled. When some columns were polled while others were skipped, the message [PollingRate polled column PIDs xxx,yyy] will be shown. Also, when the timer was faster than the polling rate, the message No column reached the PollingRate interval. will be shown, and no Get operation will be executed.

Problem when trying to send an SNMP Set command to have all active alarms resent [ID 43442]

You can have all active alarms resent by sending an SNMP Set command to the DMA (with the DataMiner IP address as target address) with OID 1.3.6.1.4.1.8813.1.1.1.1.4 and value set to the name of the SNMP manager.

However, since DataMiner versions 10.4.0 [CU12]/10.5.3, this would no longer work when the SNMP manager in question had the Resend all active alarms every ... option disabled.

Alarm indicating a runtime error would incorrectly say "-1 pending" when all threads cleared simultaneously [ID 43508]

When multiple threads of the same process have a runtime error, the associated alarm will say "+X pending", indicating the number of threads that are stuck.

Up to now, when all threads cleared simultaneously, in some cases, the alarm would incorrectly say "-1 pending".

Cassandra Cluster Migrator tool: Problem when reverse lookup of IP addresses returned hostnames other than those configured in the SSL certificate [ID 43520]

When you tried to migrate a Cassandra Cluster with SSL/TLS enabled, up to now, the Cassandra Cluster Migration tool would not be able to initialize when a reverse lookup of IP addresses returned hostnames other than those configured in the SSL certificate.

This issue can be prevented by manually checking if the IP address is one of the SANs (Subject Alternative Names) of the SSL certificate.

Problem when trying to update the log levels of an element that was not hosted on the local DataMiner Agent [ID 43582]

When you tried to update the log levels of an element that was not hosted on the local DataMiner Agent, up to now, the update request would incorrectly be ignored and would not be forwarded to the DataMiner Agent hosting the element.

From now on, the update request will correctly be forwarded to the DataMiner Agent hosting the element where it will be processed accordingly.

SLNet could return incorrect data to the client application when processing a cell subscription filter [ID 43600]

When processing a cell subscription filter, in some cases, SLNet could return incorrect data to the client application.

Restarting a replicated element could cause SLProtocol to leak memory [ID 43613]

When you restarted a replicated element that was in the process of starting up, in some cases, the resources in memory would incorrectly not get cleaned up, causing SLProtocol to leak memory.

Production version of DVE child elements would incorrectly be reset when you uploaded an updated copy of the DVE protocol version [ID 43640]

When you uploaded an updated copy of a DVE protocol version that had already been uploaded before, up to now, the production version of the DVE child elements that were using that protocol would incorrectly be reset.

STaaS: Data missing from heatmaps and alarm state pie charts [ID 43689]

When, in a client application connected to a system using STaaS, you viewed a heatmap or an alarm state pie chart, in some cases, an incorrect time zone conversion would cause those charts to not include all available data.

Service & Resource Management: No master agent would incorrectly get selected on systems with only a ResourceManager license [ID 43697]

Up to now, only on systems with both a ResourceManager license and a ServiceManager license would a master agent get selected.

From now on, a master agent will also get selected on systems with only a ResourceManager license. On these systems, the agent with the lowest DMA ID will always be promoted to master agent.

Also, when no master agent can be selected because the ResourceManager license is missing, the following log entry will be added to the SLMasterSyncerManager log file (with XXX being the IDs of the agents that do not have a ResourceManager license):

WARNING: No master DMA could be picked. Missing required ResourceManager license for DMAs XXX.

Swarming an element while automatic incident tracking was disabled would cause the alarms of that element to be removed from any user-defined alarm group they were in [ID 43739]

If automatic incident tracking was disabled and an element had an alarm that had been manually added to an alarm group, up to now, swarming that element would cause that alarm to incorrectly be removed from the alarm group and appear again as a separate alarm. This will no longer occur.

If an element gets swarmed while automatic incident tracking is enabled, the behavior remains the same as before: Manually created groups keep their elements, but any active relational anomalies (including automatically created alarm groups) involving the element are cleared.

Problem when importing a DELT package containing average trend data into a Cassandra Cluster or STaaS database [ID 43768]

Up to now, after you had imported a DELT package containing average trend data into a Cassandra Cluster or STaaS database, that database would contain invalid trend data.

SLWatchdog would incorrectly remove the threads table entries of all SLProtocol processes when one SLProtocol process disappeared [ID 43780]

Since DataMiner version 10.5.0/10.4.12, the DataMiner Agent is no longer restarted when an SLProtocol process disappears. Instead, a new SLProtocol process is started and all elements that were hosted by the process that disappeared are now be hosted by the newly created process.

However, up to now, when an SLProtocol process disappeared, SLWatchdog would remove all entries in its threads table that matched the name of the process (e.g. "SLProtocol"). This would result in all entries of the other SLProtocol processes to be removed as well.

From now on, SLWatchdog will only remove the threads table entries that match the name as well as the ID of the process.

Failover: Problem when trying to update the failover configuration when the ClusterEndpointsManager soft-launch option had been disabled [ID 43794]

Up to now, it would not be possible to update the failover configuration when the ClusterEndpointsManager soft-launch option had explicitly been disabled.

Improve this page