Table of Contents

General Feature Release 10.4.4

Note

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

Important

When downgrading from DataMiner Feature Release version 10.3.8 (or higher) to DataMiner Feature Release version 10.3.4, 10.3.5, 10.3.6 or 10.3.7, an extra manual step has to be performed. For more information, see Downgrading a DMS.

Tip

Highlights

New features

Elasticsearch re-indexing tool [ID 37994]

Migrating data from from Elasticsearch 6.8.22 to OpenSearch 2.11.1 involves the following steps:

  1. Taking a snapshot of the Elasticsearch 6.8.22 cluster.
  2. Copying the snapshot to an Elasticsearch 7.10.0 cluster, and restoring it.
  3. Re-indexing the data and taking another snapshot.
  4. Copying the snapshot with the re-indexed data to an OpenSearch 2.11.1 cluster, and restoring it

To perform step 3, a command-line re-indexing tool has been developed: ReIndexElasticSearchIndexes.exe.

This tool accepts the following arguments:

Argument Description
-Node or -N The name of the node to be used for re-indexing (mandatory).
Format: http(s)://127.0.0.1:9200 or http(s)://fqdn:9200
-User or -U The user name, to be provided in case Elasticsearch was hardened.
See Securing the Elasticsearch database
-Password or -P The user password
-DBPrefix or -D The database prefix, to be provided in case a custom database prefix is used instead of the default dms- prefix.
If you do not provide a prefix, the default dms- will be used.
-TLSEnabled or -T Whether or not TLS is enabled for this ElasticSearch database.
Values: true or false. Default: false

If you do not specify a user name and user password, the tool will assume a default ElasticSearch database installation.

DataMiner Object Models: DomInstanceHistorySettings are now also available on DomDefinition level [ID 38294]

DomInstanceHistorySettings are now also available on DomDefinition level.

The behavior is similar to that of the options in the ModuleSettingsOverrides property of a DomDefinition:

  • When HistorySettings are available in the DomDefinition, these will take precedence.
  • When the HistorySettings object in the DomDefinition is null, the HistorySettings of the ModuleSettings will be used.
Important

In order for the HistorySettings of the ModuleSettings to be used, the HistorySettings object in the DomDefinition has to be null. Just making the values empty is not sufficient.

GQI: Full logging [ID 38870]

Full GQI logging will now be available in the C:\Skyline DataMiner\Logging\GQI folder.

The log level can be configured in the <appSettings> element of the C:\Skyline DataMiner\Files\SLHelper.exe.config file.

By default, this file will contain the following GQI log settings:

<add key="serilog:minimum-level" value="Information" />

In case of issues that need investigating, you can temporarily lower the minimum log level to "Debug".

Note
  • The SLHelper.exe.config file is overwritten with the default configuration during full DataMiner upgrades or downgrades.
  • A GQI error log will be added in the C:\Skyline DataMiner\Logging\GQI folder for every GQI request that fails.

Changes

Enhancements

Circular correlation rules will now be blocked [ID 38301]

A correlation rule will now be blocked when it was triggered due to a correlated alarm that depends on an alarm created by the rule in question.

Note

​This feature only works when the correlation rule and all alarms in question reside on the same DataMiner Agent.

Automation: Late script control requests will now be ignored [ID 38409]

From now on, SLAutomation will ignore any script control request it receives for a script that is not running or not running anymore, and will add an entry in the SLAutomation.txt log file when it does so.

Examples of new log entries:

  • DEBUG (5): Handling script command 'Continue' (2) for script with ID 954.
  • ERROR (-1): Handling command 'Continue' (2) for script with ID 954 failed with error code 2147942487.
  • ERROR (-1): Handling command 'Continue' (2) for script with ID 954 failed because it is not interactive.
  • INFO (-1): Handling command 'Continue' (2) for script with ID 954 failed because it is not active.

In the latter case, no error would be returned up to now.

GQI: All GQI queries opened by the same user will now share one and the same connection [ID 38452]

Up to now, each GQI query would open a dedicated SLNet connection. From now on, all GQI queries launched by the same user will share one and the same connection.

Enhanced performance when applying a table filter subscription containing wildcards and when applying a partial table cell subscription [ID 38555]

Because of a number of enhancements, overall performance has increased

  • when applying an initial table filter subscription containing wildcards that needs to be handled by the SLElement process, and
  • when applying a subscription of a partial table cell.

Service & Resource Management: Booking name validation now case-insensitive [ID 38556]

The validation of the name of a booking is now case-insensitive. This means that when the SRM Framework checks if there are future bookings with the same name, the casing is now no longer taken into account.

DataMiner Object Models: GenericEnum values will now be converted to the display value prior to being used in a DOM instance name concatenation [ID 38586]

The DomInstanceNameDefinition class contains a simple list of IDomInstanceConcatenationItems. With this, you can add concatenation items of two types in a specific order to define your name: StaticValueConcatenationItem or FieldValueConcatenationItem.

In the case of the latter, if a FieldValue contains data for a GenericEnumFieldDescriptor (which can be either string values or integer values), these values will now be converted to the display value.

Note

Currently, using GenericEnum fields containing multiple values are not supported for name concatenation.

GQI: Ad hoc data source now supports real-time updates [ID 38643]

The ad hoc data source now supports real-time updates.

For this purpose, the IGQIUpdateable interface must be implemented in the data source.

SLAnalytics - Behavioral anomaly detection: Suggestion event generation will now be limited [ID 38674]

From now on, the generation of anomaly suggestion events will be limited to 50 events per hour per type of anomaly (level shift, trend change, flatline or variance change).

Note

The generation of anomaly alarm events (i.e. on parameters that have anomaly monitoring configured in the alarm template) will remain unlimited.

GQI: Clearer error message will now be thrown when an ad hoc data source or custom operator cannot be instantiated [ID 38686]

Up to now, when an ad hoc data source or custom operator could not be instantiated, the following exception would be thrown when an error occurred on object creation level (within the constructor):

Error: Could not create instance of datasource when trying to use an ad hoc datasource.

From now on, the following exception will be thrown instead:

Error trapped: Could not create instance of datasource 'datasource ID': <exception message>.

* <exception message> being the message that was thrown within the constructor.

SLLogCollector will now also collect the logs of the CommunicationGateway DxM [ID 38716]

SLLogCollector will now also collect the logs of the CommunicationGateway DxM.

SLAnalytics: Enhanced management of DataMinerObjectDeleteMessages [ID 38734]

Because of a number of enhancements, overall memory usage has been reduced, especially with regard to the management of DataMinerObjectDeleteMessages.

DxMs upgraded [ID 38743] [ID 38900]

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

  • DataMiner ArtifactDeployer: version 1.6.6
  • DataMiner CoreGateway: version 2.14.4.15849
  • DataMiner Orchestrator: version 1.5.6
  • DataMiner SupportAssistant: version 1.6.6

For detailed information about the changes included in those versions, refer to the dataminer.services change log.

Security enhancements [ID 38756] [ID 38650] [ID 38951]

A number of security enhancements have been made.

SLAnalytics - Trend predictions: Enhanced accuracy of the trend prediction mechanism [ID 38767]

Because of a number of enhancements, overall accuracy of the trend prediction mechanism has been improved.

SLProtocol will no longer forward all changes to standalone parameters to SLElement [ID 38785]

Up to now, SLProtocol would forward all changes to standalone parameters to SLElement, even when this was not strictly necessary. From now on, SLProtocol will only forward changes to standalone parameters to SLElement when the latter requires them.

Also, when an SNMP parameter used a wildcard as OID, up to now, SLProtocol would forward the value of that wildcard to SLElement, which would then pass it on to the SLSNMPManager process. From now on, SLProtocol will forward those wildcard values directly to SLSNMPManager.

Service & Resource Management: Past bookings will no longer be queried when creating a new booking or calculating available resources [ID 38798]

When creating or updating a booking, up to now, overlapping past bookings would be queried. This was necessary to validate the usage of contributing bookings that had already ended. In order to avoid the retrieval of those past bookings, the behavior of contributing bookings has now been altered.

From now on, it will no longer be possible to reuse a contributing booking that has already ended in a new booking. However, updating an existing main booking that uses a contributing booking will still be possible.

SLLogCollector will now run the 'tasklist /fo TABLE' command [ID 38842]

SLLogCollector will now by default run the tasklist /fo TABLE command, and save the output in the Logs\Windows folder of the generated package.

At installation the StorageModule service will now be configured to restart itself after each failure [ID 38843]

At installation, the StorageModule service will now be configured to restart itself after each failure.

At installation the APIGateway service will now be configured to restart itself after each failure [ID 38855]

At installation, the APIGateway service will now be configured to restart itself after each failure.

SLAnalytics - Behavioral anomaly detection: Enhanced performance when monitoring more than 100,000 parameters [ID 38922]

Because of a number of enhancements, overall performance of the SLAnalytics process has increased, especially when more than 100,000 parameters are being monitored for behavioral anomaly detection.

SLAnalytics - Behavioral anomaly detection: Enhanced generation of suggestion events when detecting variance changes [ID 38941]

A number of enhancements have been made to the mechanism that automatically generates a suggestion event when a variance change is detected.

Visual Overview: Connections between SLHelper and mobile Visual Overview sessions will now time out after 5 minutes of inactivity [ID 38985]

Up to now, when SLHelper did not send any updates to a mobile Visual Overview client session for 2 minutes, the connection would be destroyed. This connection timeout has now been changed from 2 minutes to 5 minutes.

Fixes

SLLogCollector: Minor issues [ID 38011]

A number of minor issues were fixed with regard to the SLLogCollector tool.

Problem when a redundancy group was set to an undefined state [ID 38401]

When a redundancy group was set to an undefined state, a large number of empty connectivity contexts would be inserted into the Connectivity section of the redundancy.xml file. As a result, the correct connectivity contexts would be overwritten, causing the redundancy group to be stuck in the undefined state.

Problem with file offload mechanism when main database is offline [ID 38542]

When the main database is offline, file offloads are used to store write/delete operations. In some cases, this file offload mechanism could end up in an unrecoverable state due to a threading issue.

Hostname of SNMP element would not get resolved after the element had gone into timeout [ID 38547]

When an element with an SNMP connection that was configured with a hostname instead of an IP address went into timeout, and during the timeout the hostname could not be resolved, the element would remain in timeout and would no longer try to resolve the hostname until it was restarted.

Also, in StreamViewer, the error messages that indicate that the hostname could not be resolved have now been made clearer. For example, in case of SNMPv3, a generic DISCOVERY FAILED error would appear when something went wrong while setting up a connection. From now on, the error will indicate what exactly went wrong (e.g. the engine ID could not be discovered, the user credentials were not valid, etc.).

Problem with SLProtocol when calculating the length of a serial response [ID 38591]

In some cases, SLProtocol could stop working due to an Access violation reading location error being thrown while calculating the length of a serial response.

GQI: Problem when sorting DOM instances when the column by which you sorted contained null values [ID 38592]

When DOM instances were sorted, in some cases, an error could be thrown when the column by which you sorted contained null values.

Problem when a DataMiner Cube client tried to connect using gRPC [ID 38606]

When a DataMiner Cube client tried to connect to a DataMiner Agent using gRPC, in some rare cases, a disconnect could occur with the following error:

Some messages have probably gone lost. Waiting for X while X+20 already entered.

SLAnalytics - Automatic incident tracking: Problem when updating alarm groups [ID 38629]

Each time the focus score of an alarm is updated, incident tracking has to update its alarm groups. In some cases, incident tracking would incorrectly update its groups twice, causing the groups to be set to an undefined state.

DaaS: The StorageModule service would incorrectly start up before the NATS service had started up [ID 38644]

When starting a DaaS system (DataMiner as a Service), in some cases, the StorageModule service would start up before the NATS service had started up. As a result, StorageModule would fail to connect to NATS and would shut down.

The DaaS startup routine has now been improved to prevent issues like the one described above.

Service & Resource Management: Booking corrupted after SRM_QuarantineHandling retrieved incorrect version of the booking [ID 38646]

Up to now, it could occur that the script SRM_QuarantineHandling retrieved a previous version of a booking instead of the latest, quarantined version, which could cause subsequent updates to corrupt the booking object. To prevent this, SRM_QuarantineHandling will now be called after a booking is saved.

STaaS: Problem when going into file offload mode [ID 38648]

When the system went into file offload mode, in some cases, a serialization issue could occur, causing the file offload mode to get stuck.

SLAnalytics - Behavioral anomaly detection: Problem when updating the anomaly configuration for a DVE element [ID 38661]

When you had updated the anomaly configuration for a DVE element, SLAnalytics would not process the changes correctly, causing incorrect behavioral anomaly alarms to be generated.

DataMiner upgrade: Some folders would not get cleaned up when performing an upgrade [ID 38672]

Up to now, the following folders would incorrectly not get cleaned up when performing a DataMiner upgrade:

  • C:\Skyline DataMiner\Webpages\API\bin
  • C:\Skyline DataMiner\Webpages\Maps\bin

Errors would be thrown at DataMiner startup when production protocols had an information template assigned [ID 38683]

At DataMiner startup, in some cases, errors could incorrectly be thrown when at least one production protocol had an information template assigned.

SLAnalytics: Problem when processing an element with an invalid alarm template [ID 38724]

In some cases, SLAnalytics could stop working while processing an element with an invalid alarm template.

Paused element set back to the active state would no longer receive any alarm updates [ID 38744]

When a paused element was set back to the "started" state, it would no longer receive any alarm updates until it was restarted.

DataMiner Maps: KML layers would incorrectly always be displayed first in the legend [ID 38746]

When using either Google Maps or OpenStreetMap, KML layers would incorrectly always be displayed first in the layer legend, regardless of the order in which they were specified in the map configuration file.

From now on, the legend will always show the layers in the order in which they were specified in the map configuration file.

Failover: Memory leak when invoking PowerShell scripts [ID 38763]

On Failover systems using a shared hostname, SLNet regularly executes PowerShell scripts. However, invoking those scripts would cause a memory leak. To prevent this, each PowerShell script will now be run in a separate process, which will be terminated at the end of the script.

BPA test 'Check agent presence in NATS' could throw an incorrect error when the local NATS process had been running for a long time [ID 38776]

When the local NATS process had been running for a long time, in some cases, the Check agent presence in NATS BPA test could incorrectly throw the following error:

Failed to execute NATS server test, the local NATS server might be offline.

Problem with SLProtocol when it was not able to reach the StorageModule service during startup [ID 38824]

In some cases, during startup, SLProtocol would stop working when it was not able to reach the StorageModule service.

Automation: Problem when sending an email to a user or group [ID 38844]

When an Automation script sent an email to a user or a user group using an Email action, in some cases, an error could be thrown.

Problem with SLProtocol when it took longer than 15 minutes to execute a poll group [ID 38858]

When an element used SNMP or HTTP communication, a notification would only be sent to SLWatchdog when a poll group finished executing. As a result, when it took longer than 15 minutes to execute a poll group, an SLProtocol run-time error alarm would be generated and subsequently cleared when the poll group finished.

In order to avoid such run-time error alarms from being generated, a check will now be performed when a response is received, and an additional notification will be sent to SLWatchdog when the first notification to SLWatchdog was sent more than one minute ago.

STaaS: Failing request would not be retried [ID 38874]

When a request to the cloud failed, in some cases, the Azure SDK would not be able to perform any retries and would throw the following exception:

System.ArgumentOutOfRangeException: 'minValue' cannot be greater than maxValue.

Mediation protocols: Problem when the value of the 'baseFor' attribute is identical to that of the '<ElementType>' tag [ID 38878]

When a mediation protocol had a baseFor attribute with a value identical to that of its <ElementType> tag, this could lead to issues in SLNet.

From now on, it will no longer be possible to upload a protocol of which the value of the baseFor attribute is identical to that of the <ElementType> tag.

STaaS: Problem when generating a DataMiner backup with the database backup option enabled [ID 38896]

Up to now, on STaaS systems, a notice would be generated when a DataMiner backup was executed with the database backup option enabled.

From now on, when a DataMiner backup is executed with the database backup option enabled, on a STaaS system, no database backup will be performed.

Note

On STaaS systems, database backups are taken automatically. If you want a STaaS backup to be restored, contact Skyline support.

StorageModule: Only final retry will be logged as error when a data storage request fails [ID 38897]

When a StorageModule client requests data to be stored, in some cases, a subscription exception can be thrown. Those data storage requests are retried automatically. However, up to now, each retry would be logged as error.

From now on, only the final retry will be logged as error. All prior retries will only be logged when the log level is set to "debug".

Problem with SLLog when stopping or restarting DataMiner [ID 38902]

When DataMiner was stopped or restarted, in some cases, the SLLog process could stop working.

Visual Overview: SLHelper would not clean up the UIProvider for an inactive user group when users from another user group were still active [ID 38979]

Up to now, SLHelper would incorrectly not clean up the server-side UIProvider for a particular user group after 8 hours of inactivity when users from another user group were still active.

From now on, SLHelper will no longer take into account activity from other user groups when it decides to clean up the UIProvider for a particular user group after 8 hours of inactivity.

SLAnalytics will no longer automatically restore a lost session with SLDataGateway [ID 38984]

Since DataMiner version 10.3.0 [CU9]/10.3.12, SLAnalytics would automatically restore a lost session with SLDataGateway. From now on, it will no longer do so.

Problem with SLDataMiner when retrieving users from a user group due to LDAP setting ReferralConfigured='false' [ID 39058]

When, in DataMiner.xml, the <LDAP> element contained the ReferralConfigured="false" attribute, SLDataMiner would stop working when it tried to retrieve the users from a particular user group that contained subgroups.

Problem with SLProtocol due to incorrect redundant connection [ID 39114]

The redundant polling feature allows SLProtocol to select another connection when the main connection goes into a timeout.

In some cases, when SLProtocol selected a connection with a type different from that of the main connection, an error could occur. From now on, when SLProtocol has to select another connection when the main connection goes into a timeout, it will only take into account connections with a type equal to that of the main connection.

SLDataMiner could stop working when a MIB file was being generated for a protocol that contained parameters with discrete values [ID 39120]

When a MIB file was being generated for a protocol that contained parameters with discrete values, in some cases, SLDataMiner could stop working.

Propose changes