Table of Contents

General Feature Release 10.5.1 – 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!

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

No highlights have been selected yet.

New features

Retrieving additional logging from a DataMiner System [ID 40766]

From now on, the GetAdditionalLoggingMessage can be used to retrieve additional logging from a DataMiner System. It will return a GetAdditionalLoggingResponseMessage with the following information:

  • Log Name: The name of the log.
  • Log Type: The type of the log. Currently, only the log type "DxM" is supported.

Example:

// Send a request to collect additional logging info 
var additionalLoggingMessage = new GetAdditionalLoggingMessage();
var response = engine.SendSLNetMessages(additionalLoggingMessage);
var loggingInfo = response.AdditionalLoggingInfo;
foreach (var logEntry in loggingInfo)
{
    engine.GenerateInformationEvent($"Log Name: {logEntry.Name}, Log Type: {logEntry.Type}");
}

Also, the existing messages GetLogTextFileStringContentRequestMessage and GetLogTextFileBinaryContentRequestMessage now have two new properties that will allow them to retrieve additional logging:

  • AdditionalLogName: The name of the additional log to be retrieved.
  • LogType: The type of the log. Example: LogFileType.DxM

Example:

// Create a request to retrieve a specific additional log in a string format
var logRequest = new GetLogTextFileStringContentRequestMessage
{ 
    AdditionalLogName = "DataMiner UserDefinableApiEndpoint", 
    LogType = LogFileType.DxM
};

SLNet 'GetInfo' messages for the PropertyConfiguration' and 'ViewInfo' types now support retrieving information for a specific item [ID 41169]

SLNet GetInfo messages for the PropertyConfiguration and ViewInfo types now support retrieving information for a specific item. This will enhance the performance of the Skyline.DataMiner.Core.DataMinerSystem.Common NuGet package used in protocols or Automation scripts.

Type PropertyConfiguration

In the ExtraData property you can now specify ";type=<propertyType>" or ";type=<propertyType>;", where <propertyType> is either ELEMENT, SERVICE or VIEW.

If another value is specified, then all property configurations will be returned.

Type ViewInfo

In the ExtraData property you can now specify ";viewId=<ID>" or ";viewId=<ID>;", where <ID> is the ID of the view for which you want to retrieve more information.

New SLNet call GetProtocolQActionsStateRequestMessage to retrieve QAction compilation warnings and errors [ID 41218]

A new SLNet call GetProtocolQActionsStateRequestMessage can now be used to retrieve the compilation warnings and errors of a given protocol and version. The response, GetProtocolQActionsStateResponseMessage, will then contains all faulty QActions and their respective warnings and errors.

In future versions, this call will be used to verify whether DataMiner Swarming can be enabled on a DataMiner System.

Changes

Breaking changes

Automation: Locking behavior of Automation script actions has been enhanced [ID 41195]

A number of enhancements have been made with regard to the locking behavior of certain Automation script actions. This should significantly reduce the chances of scripts influencing each other and slowing each other down.

Breaking changes:

Actions
 Breaking change
Generate Information
Log
Send Notification
Send Report		 Text that supports the [dummy<id>] placeholder will display the old element name if it was updated during the execution of a script or it will still display the element name even if the element was deleted in the meantime.
Set State The action will fail with a different error. Previously, when an element would be removed during the execution of a script, it would state "No valid protocol mapping found". Now, it will depend on the state, but should be "Failed to change element state...".
Set Template The action will fail with a different error. Previously, when an element would be removed during the execution of a script, it would state "No valid protocol mapping found". Now, it will depend on the state, but should be "Failed to set template...".

Enhancements

DataMiner installer has been updated [ID 40409] [ID 41299]

The DataMiner installer has been updated.

When the configuration window appears, it will now be possible to either continue with the configuration or cancel the entire installation.

For more information on the installer, see Installing DataMiner using the DataMiner Installer.

Clustering compatibility check enhancements [ID 41046]

When, in e.g. DataMiner Cube, you try to add a DataMiner Agent to the DataMiner System, a number of checks will be performed to determine whether the new Agent is compatible to be added.

The checks with regard to database compatibility have now been enhanced.

See also: System Center - Agents: Clustering compatibility checks will now be performed by the DMA to which Cube is connected [ID 41049]

Cassandra Cluster Migrator tool: Enhancements [ID 41099]

A number of enhancements have been made to the Cassandra Cluster Migrator tool (SLCCMigrator.exe):

  • The initialization of a single agent has been disabled in favor of the global initialization, unless not all agents could be initialized.
  • Connection details will now only be requested once, unless not all agents could not be initialized.
  • The migration can now only be started when all agents have successfully been initialized.

Service & Resource Management: Starting bookings with elements that are not active [ID 41129]

It is now possible to start bookings with elements that are not active.

To do so, in the Resource Manager configuration file, set the AllowNotActiveElements option to true.

Service & Resource Management: Process of starting blocking tasks has now been optimized [ID 41175]

Up to now, when blocking tasks with the same start time needed to be scheduled for several bookings, in some cases, bookings with limited start actions could get blocked by bookings with longer start actions.

Because of a number of enhancements, the process of starting blocking tasks has now been optimized.

Service & Resource Management: Enhanced deletion of ReservationInstances in bulk [ID 41236]

When ReservationInstances were deleted in bulk, up to now, an individual delete request would be sent to the database for every instance.

From now on, when ReservationInstances are deleted in bulk, a single delete request will be sent to the database for every batch of 200 ReservationInstances.

This will significantly enhance overall performance when deleting large numbers of ReservationInstances.

VerifyClusterPorts: Endpoints to be tested will be retrieved from the Single Source of Truth [ID 41262]

The VerifyClusterPorts prerequisite and the VerifyClusterPorts.dmupgrade package will now use the Single Source of Truth (C:\Skyline DataMiner\Configurations\ClusterEndpoints.json) to determine which endpoints should be tested.

If this JSON file cannot be found, the endpoint to be tested will be retrieved from the DMS.xml and SLCloud.xml files.

SLAnalytics: Synchronization of the configuration.xml file can now be forced via Cube [ID 41270]

Up to now, when you had made changes to a C:\Skyline DataMiner\Analytics\configuration.xml file on the leader Agent, you had to manually replace the file on all Agents in the cluster. From now on, you can force the synchronization of this file via Cube.

See also Synchronizing data between DataMiner Agents

DxMs upgraded [ID 41297]

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.8.1
  • DataMiner CoreGateway: version 2.14.11
  • DataMiner FieldControl: version 2.11.1
  • DataMiner Orchestrator: version 1.7.1
  • DataMiner SupportAssistant: version 1.7.1

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

Fixes

When an element that was used in an alarm level link configuration was restarted, in some cases, both SLElement and SLProtocol could leak memory, as would SLDataMiner when the alarm level links were pushed to locked elements.

For more information on the <AlarmLevelLinks> element, see How to aggregate alarm severities

SLElement: Incorrect alarm linking [ID 41057]

In some cases, new alarm events could incorrectly get linked to previously closed external events or information events on the same element.

SLElement would leak memory when filtering a recursive table or a directview/view table that had to be sorted [ID 41058]

When SLElement had to process a table filter request, it would leak memory in the following cases:

  • When the table had a foreign key to itself.
  • When a directview or view table with a number of non-initialized columns had to be sorted.

SLElement would leak memory when SLNet needed to be notified of baseline changes [ID 41088]

When a baseline changed and SLNet needed to be notified of the new values, SLElement would leak memory.

Failover: Problem when an element.xml file was updated while StorageModule was synchronizing its cache [ID 41133]

When, in a Failover setup, SLDMS was synchronizing an updated element.xml file while the StorageModule DcM was synchronizing its cache to an XML file, in some rare cases, an exception could be thrown in the StorageModule DcM, causing the element.xml update to fail.

LDAP/ActiveDirectory domain users would no longer be able to log in [ID 41143]

Since DataMiner 10.4.0 [CU4]/10.4.7, in some cases, LDAP/ActiveDirectory domain users would no longer be able to log in. When such a user tried to log in, the following entry would be added to the SLNet.txt log file:

Authentication Step Failure: Not a DataMiner user: CONTOSA\user

This issue would only occur on LDAP servers where CN=CONTOSA,CN=Partitions,CN=Configuration,DC=contosa,DC=com does not have a nETBIOSName attribute, for example when accessing the GlobalCatalog of a forest.

After having upgraded to a DataMiner version that contains this fix, you can do the following:

  • Wait up to an hour for the next LDAP synchronization to occur, or
  • Manually trigger the "Skyline DataMiner LDAP Resync" task in Windows Task Scheduler.

All users should then be able to log in again.

STaaS: Excessive number of duplicate entries added to the SLErrors.txt log file in case of connection problems [ID 41192]

On STaaS systems, in case of connection problems, a large number of the following errors would be added to the SLErrors.txt log file:

  • The remote name could not be resolved.
  • Unable to connect to the remote server.

From now on, in case of connection problems, the generation of SLErrors.txt log file entries will be throttled in order to reduce the number of duplicate entries.

Protocols: Problems when polling SNMP tables using GetNext [ID 41235]

A number of problems that occurred when polling SNMP tables using GetNext have been fixed:

  • When an entire SNMP table was polled using GetNext messages, and not all rows had values with the same syntax (e.g. 1.2.3 vs 4.5.6.7), in some cases, cells would be empty or would be shifted to another row. The SLSNMPManager process could even disappear. From now on, all table cell values will be displayed correctly.

  • Up to now, an SNMP table would be polled until the returned OID result went out of scope. For example, when only 3 columns were defined in the table parameter, and the SNMP table contained 20 columns, all 20 columns would be polled, even though the data in the remaining 17 columns was not needed. From now on, as soon as the columns defined in the table parameter are polled, polling will stop and the result will be filled in.

  • Up to now, only the rows with a value in the first column would be added to the table. From now on, when the table parameter has the instance option defined, rows of which the first column on the right of the instance column is empty will also be added to the table.

No longer possible to clear certain DVE alarm events [ID 41343]

Since DataMiner feature version 10.4.8, it would incorrectly no longer be possible to clear DVE alarm events generated by DataMiner modules like Correlation, Automation, SLAnalytics, etc.

Propose changes