General Feature Release 10.6.2 CU1

Note

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

Important

Before you upgrade to this DataMiner version:

• Make sure version 14.44.35211.0 or higher of the Microsoft Visual C++ x86/x64 redistributables is installed. Otherwise, the upgrade will trigger an automatic reboot of the DMA in order to complete the installation. The latest version of the redistributables can be downloaded from the Microsoft website:

  • vc_redist.x86.exe
  • vc_redist.x64.exe

• Make sure all DataMiner Agents in the cluster have been migrated to the BrokerGateway-managed NATS solution. For detailed information, see Migrating to BrokerGateway. See also: DataMiner Systems will now use the BrokerGateway-managed NATS solution by default [ID 43856] [ID 43861] [ID 44035] [ID 44050] [ID 44062]

• Make sure the Microsoft .NET 10 hosting bundle is installed (download the latest Hosting Bundle under ASP.NET Core Runtime from dotnet.microsoft.com). See also: DataMiner upgrade: New prerequisite will check whether .NET 10 is installed.

Tip

• For release notes related to DataMiner Cube, see DataMiner Cube Feature Release 10.6.2.
• For release notes related to the DataMiner web applications, see DataMiner web apps Feature Release 10.6.2.
• For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.

Changes

Fixes

Problem with the GQI DxM when it tried to connect to SLNet during DataMiner startup [ID 44380]

During DataMiner startup, in some rare cases, a fatal error could occur in the GQI DxM when it tried to connect to SLNet.

Calls that check whether the connection between client and DMA is still alive would incorrectly be blocked when 10 simultaneous calls were being processed [ID 44456]

When 10 simultaneous calls between a client application (e.g., DataMiner Cube) and a DataMiner Agent were being processed, up to now, any additional call would be blocked, including calls that check whether the connection between client and DMA was still alive. As a result, the client application would disconnect.

From now on, even when 10 simultaneous calls between a client application (e.g., DataMiner Cube) and a DataMiner Agent are being processed, calls that check whether the connection between client and DMA is still alive will never be blocked.

SLDataGateway issue caused by OpenSearch health monitoring [ID 44647]

After an upgrade to DataMiner 10.6.2 [CU0], it could occur that SLSearchHealth.txt reported issues with the health monitor, and SLDataGateway could crash at startup. The changes that introduced this issue, i.e., OpenSearch: Enhanced health monitoring [ID 43951], have been reverted.

Service & Resource Management: Problem when calculating resource availability [ID 44649]

When calculating resource availability, the resource manager only checks the first 1000 bookings returned by the database. This means that, if there are more than 1000 bookings, resource availability will not be calculated correctly, causing the following issues:

• When GetEligibleResources is being used, resources that are not available could be returned as available.
• When ReservationInstances are created or updated, resources could get overbooked beyond their available concurrency and capacity.

From now on, the creation of new bookings that overbook a resource will be prevented.