Table of Contents

General Main Release 10.5.0 CU3

Note

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

Tip

Enhancements

VerifyNatsIsRunning prerequisite check has now been replaced by the VerifyNatsCluster check [ID 42206]

The VerifyNatsIsRunning prerequisite check has now been replaced by the VerifyNatsCluster check.

This check, which is included in upgrade packages, verifies whether the crucial NATS service used by DataMiner is running on all required DataMiner Agents and whether communication between all NATS nodes is possible.

The same prerequisite is also available as a BPA test in System Center.

This prerequisite check prevents situations where a DataMiner System becomes non-functional after an upgrade because of pre-existing issues with NATS. If this check fails, troubleshoot NATS before continuing the upgrade.

Enhanced ClearAllKeys() function [ID 42368]

Because of a number of enhancements, overall performance of the SLProtocol function ClearAllKeys() has increased.

SLAnalytics: Enhanced caching of DVE element information [ID 42555]

A number of enhancements have been made with regard to the caching of DVE element information.

MessageBroker: Enhanced performance when checking for local IP addresses [ID 42570]

As the MessageBroker prefers to set up NATS connections using local IP addresses, up to now, it would request the local IP addresses from the DNS for every item in the list of NATS endpoints. From now on, it will request the local IP addresses from the DNS only once.

The IP addresses returned by the DNS will be cached for one minute only. This will prevent providing outdated information when connections have to be set up later on.

Cassandra Cluster: Enhanced performance when importing DELT packages [ID 42613]

Because of a number of enhancements, overall performance has increased when importing DELT packages on systems with a database of type Cassandra Cluster, especially when those packages contain a large amount of trend data.

Additional SLNet log files [ID 42625]

From now on, SLNet logging will not only be kept in the SLNet.txt log file. Certain entries will now also be kept in one of the following new log files, which will all be located in the C:\Skyline DataMiner\Logging\SLNet\ folder.

Log file Contents
FacadeHandleMessage.txt All SLNet log entries created by the Facade.HandleMessage method.
ReducedLog.txt All SLNet log entries that have not been added to any of the other new log files.
RepositoriesMessage.txt All SLNet log entries created by the SLNet.Repositories method.
StartupLog.txt The first 1000 SLNet log entries added to the SLNet.txt log file after SLNet was started.
Note
  • The existing SLNet.txt log file will remain unchanged.
  • Contrary to the SLNet.txt log file, which can have up to 3 rollover files ([logfile]0.txt), the above-mentioned new log files can only have one single rollover file each.

Enhanced performance when logging in using external authentication via SAML [ID 42668]

Because of a number of enhancements, overall performance has increased when logging in using external authentication via SAML.

Protocols: Configuring an override parameter to replace the nominal smart baseline value of a column parameter [ID 42712]

In the type attribute of the Protocol.Params.Param.Alarm tag, it is now possible to configure an override parameter for a column parameter.

If an override parameter is configured in the protocol, the smart baseline calculation will first check if a value is configured in the override parameter and if a value is present. If that value is not an exception value, it will take this value and copy it to the nominal value parameter instead of trying to calculate a nominal value whenever the smart baseline timer elapses.

To configure an override parameter, use the following syntax:

<Alarm type="absolute:NOMINAL_VALUE_PID,FACTOR_PID,OVERRIDE_PID">
Note
  • The FACTOR_PID is optional and can be left empty.
  • The ID of the override parameter (OVERRIDE_PID) is the third value in the comma-separated list. The OVERRIDE_PID value must be (a) the parameter ID of a column in the same table as the source column or (b) the parameter ID of a standalone column. Any other parameter ID will not work.

Security enhancements [ID 42747] [ID 42843]

A number of security enhancements have been made.

Fixes

Problem with SLProtocol when a protocol version was overwritten while an element using that protocol version was starting up [ID 42344]

When a protocol version was overwritten while an element using that protocol version was starting up, in some cases, the SLProtocol process could stop working. Also, this could result in alarms like the following being generated:

Unexpected Exception [Exception from HRESULT: 0x8004024C]: The element is unknown.

DataMiner not able to start up after installation [ID 42431]

After installation, in some cases, DataMiner would not be able to start up because the MessageBrokerConfig.json file could not be found in the C:\ProgramData\Skyline Communications\DataMiner\ folder.

Redundancy groups: Matrix parameter updates in a derived element would incorrectly not get applied in the source element (and vice versa) [ID 42598]

When, within a redundancy group, a matrix parameter in a derived element was updated, in some cases, that same matrix parameter would incorrectly not get updated in the source element (and vice versa).

SLHelper - GQI: Log entry of caught exception would incorrectly not include all details [ID 42608]

On systems using the SLHelper process for GQI-related operations, up to now, an exception thrown when using a custom implementation of an ad hoc data source would be caught, but the log entry would incorrectly not include the full message. From now on, the log entry will include all details of the exception that was thrown.

Problem when starting an element with DCF connections towards a previously deleted element [ID 42632]

When an element that had DCF connections towards a previously deleted element was started, in some cases, an "unhandled exception" notice could appear in the Alarm Console. Also, as a result of the exception, the element's connection information would not be available in SLNet and DataMiner Cube, and no connection lines would be displayed for the connections in question.

SNMP forwarding: Inconsistent messages in alarm storm information events [ID 42642]

SNMP managers generate an information event each time an alarm storm starts and ends.

Up to now, the word "SNMP manager" would not be spelled consistently in both messages. The information event announcing the start of an alarm storm would start with Alarmstorm for SNMP Manager: ..., while the information event announcing the end of an alarm storm would start with Alarmstorm for SNMPManager: ...

From now on, both information events will start with Alarmstorm for SNMP Manager: ...

Problem with trend windows after switching from daylight saving time to standard time [ID 42685]

In some rare cases, trend windows could get stuck in SLDataGateway after switching from daylight saving time to standard time.

VerifyClusterPorts: Log entries would incorrectly ask you to check the DMS.xml file when using the BrokerGateway-managed NATS solution [ID 42701]

When the VerifyClusterPorts prerequisite failed, up to now, its log entries would incorrectly always ask you to check the DMS.xml file, regardless of whether the system was using the legacy SLNet-managed NATS solution or the BrokerGateway-managed NATS solution introduced in DataMiner 10.5.0 [CU2]/10.5.5.

From now on, the VerifyClusterPorts log entries will ask you to check the following file, depending on the NATS solution the system is using:

NATS solution being used File mentioned in VerifyClusterPorts log entries
SLNet-managed NATS solution DMS.xml
BrokerGateway-managed NATS solution ClusterEndpoints.json

SLNet protocol cache would incorrectly retain the names of deleted protocols [ID 42710]

In some rare cases, the SLNet protocol cache would incorrectly retain the names of deleted protocols.

'Register DataMiner as Service.bat' would incorrectly register services as 32-bit services [ID 42713]

In some cases, the Windows batch file Register DataMiner as Service.bat would incorrectly assume that a machine was running a 32-bit operating system. As a result, it would incorrectly register services as 32-bit services.

As 32-bit Windows systems are no longer supported, from now on, the Register DataMiner as Service.bat file will no longer check the architecture of the operating system.

GQI DxM: Problem when using certain extensions because of issues with named pipes [ID 42782]

In order to communicate with its extension processes, the GQI DxM uses named pipes. In some cases, because a pipe would fail to connect to the core GQI process, it would no longer be possible to use a particular extension.

Additionally, a number of enhancements have been made with regard to the management of named pipes.

Antivirus software could incorrectly flag DcomConfig.exe as a virus and remove it from the system [ID 42979]

Since DataMiner 10.4.0 [CU14]/10.5.0 [CU2]/10.5.5, some antivirus software could incorrectly flag C:\Skyline DataMiner\tools\DcomConfig.exe as a virus and remove it from the system. As a result, DataMiner upgrades would fail.

Improve this page