General Main Release 10.0.0 CU15

Note

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

Tip

For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.

Enhancements

Standalone Elastic Backup tool will now have to be used to restore a backup of an Elasticsearch database [ID 29677]

When you take a backup of a DataMiner Agent, you can opt to also take a backup of its Elasticsearch database. However, as the latter will in most cases be a cluster, automatically restoring an Elasticsearch backup when restoring a DataMiner Agent is not advisable.

From now on, even when a DataMiner backup includes an Elasticsearch backup, the latter will not be automatically restored when the DataMiner backup is restored. Restoring an Elasticsearch backup will now have to be done using the Standalone Elastic Backup tool.

For more information on the Standalone Elastic Backup tool, see Standalone Elastic Backup Tool.

SLWatchdog: Notification enhancements [ID 29697]

A number of enhancements have been made with regard to notifications generated by the SLWatchDog process.

DataMiner Cube: 'Not applicable' replaced by 'N/A' when displaying alarm statistics while the alarm storm protection mode is active [ID 29771]

When, in Visual Overview or the Surveyor, alarm statistics were displayed while the alarm storm protection mode was active, up to now, the number of alarms would be replaced by “Not applicable”. From now on, the number of alarms will be replaced by “N/A” instead of “Not applicable”.

Inter-DMA communication: Enhanced automatic HTTP port detection [ID 29834]

Up to now, when port 80 (HTTP) was unavailable between DataMiner Agents, connections between the DataMiner Agent modules on the different servers would only work after the ConnectTimeout setting had been increased. From now on, when auto-detecting the target port (via port 80 or 443) fails, the connection attempt will continue on default port 8004.

Also, a number of additional options were added to the connection string configuration (SLNetClientTest > Advanced > Edit Connection Strings):

The “To” field can now contain wildcards (* or ?). If there is no exact match, the settings of the record in question will then apply to all matching destinations. If more than one wildcard entry matches a destination, the behavior is undefined.
The connection string can now be set to “auto://nodetect” in order to skip the auto-detection of the target SLNet port and automatically default to 8004. When port 80 is blocked between agents, the 15-second autodetection timeout will then be skipped.

DataMiner Cube - Bookings app: Enhanced performance of the bookings timeline [ID 29876]

Due to a number of enhancements, overall performance of the bookings timeline has been increased.

LogCollector: Enhanced handling of long file paths [ID 29910]

When, during the creation of a dump file, SLLogCollector encountered a file of which the path was longer than 256 characters, up to now, an error would be thrown and the entire dump operation would fail. From now on, when SLLogCollector encounters a file of which the path was longer than 256 characters, it will exclude that file, and continue creating the dump file.

Also, when in the registry of a Windows 10 version 1607 or above the LongPathsEnabled option is set to 1 in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, SLLogCollector will now accept file paths that are longer than 256 characters.

SLManagedAutomation: Locking mechanism will now prevent exceptions from being thrown when reading or writing items in the dummies collection [ID 29930]

In an Automation script, every Engine object contains a collection of “dummies”. Each of these dummies represents an element and can be used to interact with that element. When an Automation script wants to interact with an element that is not yet available in the dummies collection, a new dummy is created.

Up to now, exceptions could be thrown when multiple threads were trying to read or write items in the dummies collection. Now, a locking mechanism has been added to prevent multiple threads from interfering with each other while accessing the dummies collection.

SLSNMPManager: Enhanced logging [ID 29935]

In order to determine the root causes of certain SNMP-related issues, the SLSNMPManager error logging has been enhanced.

This enhanced logging will especially be helpful when investigating the “Unable to set the destination IP” error.

SLElement: Enhanced memory usage when processing service impact data [ID 29948]

Due to a number of enhancements, overall memory usage of SLElement has increased, especially when processing service impact data.

Also, a small memory leak was fixed in elements contained within services.

New BPA tests added to default test set [ID 30010]

The following new BPA tests have been added to the default test set:

Minimum Requirements Check
Report Active RTE
View Recursion

Fixes

Service & Resource Management: Problem when trying to retrieve a resource with status 'Maintenance' or 'Unavailable' [ID 29511]

Due to a serialization issue involving the AvailableTo and AvailableFrom properties of the GetResourceMessage, in some cases, it would not be possible to retrieve a resource with status “Maintenance” or “Unavailable”.

DataMiner Cube - Surveyor: Newly created elements located in multiple views would incorrectly only appear in one of those views [ID 29544]

When you created a new element located in multiple views, in some rare cases, it would incorrectly only appear in one of those views. Only when you reconnected Cube would the element be displayed in all views in which it was located.

When you opened a trend group with several graphs, in some rare cases, color icons would be missing from the trend graph legend.

Manually clearing a clearable alarm on a single-value parameter would incorrectly set the alarm state of the parameter to 'undefined' instead of 'normal' [ID 29745]

When you manually cleared a clearable alarm on a single-value parameter, the alarm state of the parameter would incorrectly be set to “undefined” instead of “normal”.

DataMiner.xml: <NetworkAdapters> tag not correctly applied when a network adapter did not have a current IP address assigned [ID 29759]

In the DataMiner.xml file, you can use the <NetworkAdapters> tag to override the order of the network adapters on a DataMiner Agent.

Up to now, when one of the adapters had an IP address defined in the Windows Registry but had no current IP address assigned, in some cases, an incorrect order could get applied in DataMiner.

SLSpectrum would no longer properly clean up client connections [ID 29769]

In some cases, the SLSpectrum process would no longer properly clean up client connections. As a result, its overall performance would decrease each time a client had made a connection.

DataMiner Cube - Alarm templates: Problem with overlapping time frames when the end time of a schedule entry was set to midnight [ID 29772]

When configuring schedules in alarm templates, in some cases, entries could have overlapping time frames, especially when the end time of one of those entries was set to midnight.

DataMiner Cube - Visual Overview: Field and FieldID placeholders could not be used by a Visio file assigned to a view enhanced with EPM data [ID 29790]

When a view was enhanced with EPM data and had a Visio file assigned to it, in some cases, the Visio file assigned to that view would not be able to use the Field and FieldID placeholders.

DataMiner Cube: Problem when pressing the Back button during logon [ID 29808]

When you pressed the Back button while logging on, in some cases, an error could occur in the logon screen, forcing you to restart Cube.

Monitoring app: Service child pop-up pages without parent page could not be opened [ID 29816]

When, for an element included in a service, only parameters from one of its pop-up pages were included and none of that pop-up page’s parent page, then that parent page would not be included in the service and there would be no way to access the pop-up page. From now on, in cases like this one, pop-up pages of service children will be added to the Monitoring app’s side panel after all other pages.

Legacy Reporter app: Problem when trying to display a trend graph for a table column parameter [ID 29818]

When the legacy Reporter app had to display a trend graph for a table column parameter, in some cases, a “no trend graph is available” message would incorrectly appear instead, especially when that table column parameter had both average and real-time trending enabled on certain rows.

DataMiner Cube: Problem with SLSpectrum when closing a spectrum element card [ID 29824]

In some cases, an error could occur in SLSpectrum when you closed a spectrum element card.

Not all references to child elements were removed from the original DMA after a DELT migration of main DVE elements [ID 29831]

After a DELT migration of main DVE elements from one DMA to another, in some cases, not all references to the child elements would be removed from the original DMA.

DataMiner Cube - Visual Overview: Problem when opening a visual overview that contained a filtered table [ID 29846]

In some cases, DataMiner could become unresponsive when you opened a visual overview that contained a filtered table.

Masking monitored column parameters that were not in an alarm state would not cause them to get marked as being masked [ID 29871]

When you masked a monitored column parameter that was not in an alarm state, it would incorrectly not get marked as being masked.

SLAnalytics: Memory spikes when requesting trend predictions [ID 29925][ID 29983]

In some cases, large memory spikes would occur in the SLAnalytics process when requesting trend predictions for parameters with a small polling interval that did not receive regular (non-exception) parameter value updates in the real-time trend data history.

Failover: Problem with SLNet during DataMiner startup [ID 29950]

On a Failover system, in some rare cases, an error could occur in SLNet during DataMiner startup, causing the following run-time error in SLDMS:

THREAD PROBLEM : SLDMS.exe - ConnectionThread [pid 99999 - thread 99999]

DataMiner Cube - Bookings app: Memory leak in bookings list [ID 30048]

When an item was removed from the bookings list, it could occur that the item was not removed from memory.

Problem when masking DVE elements containing table parameters [ID 30084]

When an element is masked, DataMiner will mask all parameters of that element. Table parameters will be masked as a whole, meaning that column parameters will not be masked individually. However, in case of DVE elements, a column parameter can be exported as a separate, standalone DVE parameter. So, here, a column parameter can be masked individually as the rest of the table is not part of the DVE element.

Up to now, when an entire table had been exported to a DVE element, and that DVE element was masked, then DataMiner would incorrectly mask the table as a whole as well as each column individually, leading to double masking.

From now on, when an entire table was exported to a DVE element, the column parameters will no longer be masked individually. The default table masking procedure will be applied.

Table of Contents