Table of Contents

General Main Release 10.6.0 CU8

Note

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

Tip

Prerequisites

Before you upgrade to this DataMiner version:

Changes

Enhancements

MessageBroker library has been upgraded to Microsoft .NET 10 [ID 44205]

The MessageBroker library has been upgraded to Microsoft .NET 10.

DataMiner Installer now supports command-line installation [ID 45554]

You can now install DataMiner from the command line by running the following command:

DataMinerInstaller.exe Install <Path to firststartupchoiceconfig.json>

For more information about the configuration file, see Unattended DataMiner installation.

DataMiner Installer: Perpetual STaaS systems will retain their configured DMA ID and use a supplied license file [ID 46102]

When you configure a perpetual STaaS system using the DataMiner Installer, the configured DMA ID is now retained instead of being replaced with an ID returned by dataminer.services.

Also, when the Installer is run in unattended mode, you will now be able to specify the optional LicenseConfig.LicenseFilePath setting in order to apply an existing DataMiner.lic file. The installer will then copy the license file to the DataMiner root folder and start DataMiner, without requiring you to generate and upload a Request.lic file.

User-Defined APIs: UserDefinableApiEndpoint DxM health status is now reported to dataminer.services [ID 46356]

The UserDefinableApiEndpoint DxM now reports its health status to dataminer.services.

When it can validate or repair the IIS rewrite rule for user-defined APIs, it reports a healthy status. If the rule cannot be repaired, it reports an unhealthy status.

BrokerGateway will now fall back to a local IP address and can reset its cluster configuration [ID 46382]

As the ClusterEndpoints.json file is missing or empty when BrokerGateway is installed for the first time, from now on, it will fall back to a configuration with a single local agent. It will use a detected local IP address, preferring an IPv4 address, instead of the local host or container name.

In addition, the new POST api/clusteringapi/resetbrokergateway operation clears stale cluster information and detects the local agent again.

DxMs upgraded [ID 46577]

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

  • DataMiner DataAPI 1.5.0

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

VerifyDotNetVersion prerequisite check will no longer check whether .NET 8 is installed [ID 46579]

From now on, the VerifyDotNetVersion prerequisite check will no longer check whether .NET 8 is installed when you install or upgrade DataMiner.

Microsoft .NET 10 remains required.

Fixes

Deleted-service information events would no longer have the service impact of the deleted service [ID 46195]

Up to now, when a service was deleted, the generated deleted-service information event would incorrectly no longer have the service impact of that deleted service.

Stopping an element with a logger table could cause SLProtocol to stop unexpectedly [ID 46299]

Up to now, in some rare cases, stopping an element with a logger table could cause the SLProtocol process hosting the element to stop unexpectedly.

DIS: DIS Inject could not trigger QAction execution on parameters unknown to SLNet [ID 46304]

Up to now, DIS Inject could not trigger QAction execution through parameters that are only known in SLProtocol and not in SLNet, such as dummy parameters.

From now on, DIS Inject will be able to trigger QActions through those parameters as well. Parameters that are known in SLNet will still be validated against the parameter security level.

Automation scripts from app packages could leave stale database entries when removed on systems using STaaS [ID 46308]

On systems using STaaS, up to now, after an app package was installed, removing included automation scripts could fail to remove the corresponding AppPackageContent database entries.

This issue was caused by a case-sensitive mismatch in the script-type filter (automationscript instead of AutomationScript). From now on, the filter is case-insensitive, so stale automation script entries are removed correctly.

Failover: SLASPConnection could fail to initialize after a Failover switch [ID 46350]

After a Failover switch, SLASPConnection could fail to initialize correctly when the DataMiner Agent came back online. This could cause the following issues:

  • The legacy Reporter could be unavailable when the LegacyReportsAndDashboards soft-launch option was enabled.
  • Incoming notifications could remain in memory without being processed, causing a memory leak.
  • The reporter page in DataMiner Cube and the distribution, alarm count, and timeline components in the Dashboards app could show outdated information.

SRM: Conflicting bookings incorrectly could be created during bulk creation [ID 46351]

Up to now, bulk creation of booking instances could incorrectly create instances identified as conflicting when the force quarantine flag was disabled.

NATSReset.exe could throw an InvalidOperationException after the IP address of a DataMiner Agent had changed [ID 46360]

Up to now, after the IP address of a DataMiner Agent had changed, running NATSReset.exe could throw an InvalidOperationException.

NATSMigration and NATSRepair could omit errors from the final error overview [ID 46362]

Up to now, some errors encountered by NATSMigration.exe or NATSRepair.exe could incorrectly be missing from the error overview at the end of the command-line output.

STaaS: Ordering DOM entries by optional fields could throw a CRUD exception [ID 46377]

On systems using STaaS, up to now, ordering DOM entries by an optional field could throw a CRUD exception when one or more entries did not contain that field.

SLSNMPManager could stop unexpectedly when testing a connection with SNMPv3 credentials [ID 46438]

Up to now, testing a connection that used SNMPv3 credentials from the Credential Library with SHA-224, SHA-256, SHA-384, or SHA-512 authentication could cause the SLSNMPManager process to stop unexpectedly.

SNMP: Community credentials could be lost when an automation script modified an element [ID 46537]

Up to now, when an automation script modified an element that used community credentials from the Credential Library on its main connection, the element could lose those credentials if the script did not change them. From now on, the credentials will be retained.

SLScripting could stop working due to recursive assembly resolution logging [ID 46572]

In some cases, when SLScripting tried to log that a different version of an assembly had been loaded than the requested version, the logging could trigger another resolution attempt for the same assembly. This could result in a recursive loop that caused SLScripting to stop working.

A safeguard has now been introduced in the version mismatch logger and the resolve failure logger to prevent this recursive behavior.

Elasticsearch re-indexing tool: Various fixes [ID 46587]

A number of fixes have been made to the Elasticsearch re-indexing tool (ReIndexElasticSearchIndexes):

  • Up to now, after migrating from Elasticsearch to OpenSearch, the Elasticsearch re-indexing tool could replace the date-math expression in the index.provided_name field with a literal index name. This could prevent rollover-managed indices from rolling over on schedule. The tool now preserves the expression when it recreates indices.

  • The tool now swaps aliases atomically, verifies that exactly one index has the write flag on the active alias, and compares alias sets without relying on their order. It also skips index families that should not roll over and finds the next available sequence number when the expected one is already in use. Before modifying indices, it checks whether the cluster has enough shard capacity and, if needed, provides the suggested cluster.max_shards_per_node setting. You can bypass this check with --SkipShardPreflight if the cluster has already been sized.

  • The tool now handles null responses and failed destination reads without stopping unexpectedly. It also reduces redundant _cat/indices requests for performance and normalizes the -D/--DBPrefix argument so it can be supplied without a trailing hyphen.

Problem when APIGateway was shut down [ID 46619]

Up to now, when the APIGateway module was shut down, it would stop working unexpectedly and throw an ObjectDisposedException.

Improve this page
Advanced search syntax