Table of Contents

General Main Release 10.5.0 CU1

Note

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

Tip

Enhancements

Web visual overviews: Load balancing [ID 41434] [ID 41728]

It is now possible to implement load balancing among DataMiner Agents in a DMS for visual overviews shown in web apps.

Up to now, the DataMiner Agent to which you were connected would handle all requests and updates with regard to web visual overviews.

Configuration

In the C:\Skyline DataMiner\Webpages\API\Web.config file of a particular DataMiner Agent, add the following keys in the <appSettings> section:

  • <add key="visualOverviewLoadBalancer" value="true" />

    Enables or disables load balancing on the DataMiner Agent in question.

    • When this key is set to true, for the DataMiner Agent in question, all requests and updates with regard to web visual overviews will by default be handled in a balanced manner by all the DataMiner Agents in the cluster.

      However, if you also add the dmasForLoadBalancer key (see below), these requests and updates will only be handled by the DataMiner Agents specified in that dmasForLoadBalancer key.

    • When this key is set to false, for the DataMiner Agent in question, all requests and updates with regard to web visual overviews will be handled by the local SLHelper process.

  • <add key="dmasForLoadBalancer" value="1;2;15" />

    If you enabled load balancing by setting the visualOverviewLoadBalancer key to true, you can use this key to restrict the number of DataMiner Agents that will be used for visual overview load balancing.

    The key's value must be set to a semicolon-separated list of DMA IDs. For example, if the value is set to "1;2;15", the DataMiner Agents with ID 1, 2, and 15 will be used to handle all requests and updates with regard to web visual overviews.

    If you only specify one ID (without trailing semicolon), only that specific DataMiner Agent will be used to handle all requests and updates with regard to web visual overviews.

Note

These settings are not synchronized among the Agents in the cluster.

New server messages

The following new messages can now be used to which you can target to be sent to other DMAs in the cluster:

  • TargetedGetVisualOverviewDataMessage allows you to retrieve a Visual Overview data message containing the image and the content of a visual overview.

  • TargetedSetVisualOverviewDataMessage allows you to execute actions on a visual overview that is rendered on a specific DataMiner Agent.

Note

DataMiner Agents will now automatically detect that a visual overview they are rendering has been updated. This means that other agents in the cluster will now be able to correctly process update events and request new images for their clients.

Logging

Additional logging with regard to visual overview load balancing will be available in the web logs located in the C:\Skyline DataMiner\Logging\Web folder.

Enhanced performance when updating subscriptions and when checking events against the set of active subscriptions [ID 41822]

Because of a number of enhancements, overall performance has increased when updating subscriptions and when checking events against the set of active subscriptions.

Security enhancements [ID 41913] [ID 42104] [ID 42343]

A number of security enhancements have been made.

Service & Resource Management: Enhanced handling of locked files when activating or deactivating functions [ID 41978]

A number of enhancements have been made to the ProtocolFunctionManager with regard to the handling of locked files when activating or deactivating functions.

Interactive Automation scripts: UI components 'Calendar' and 'Time' can now retrieve the time zone and date/time settings of the client [ID 42064]

When UI components of type Calendar or Time are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run, the UI components of type Calendar and Time will be able to return the time zone of the client and the time and date as entered by the user.

To allow the client to return the time zone and client time and date, on the UIBlockDefinition, set the ClientTimeInfo option to UIClientTimeInfo.Return. This option is intended to be used for UI components of type Calendar or Time (the latter with either AutomationDateTimeUpDownOptions, AutomationDateTimeUpDownOptions or AutomationDateTimePickerOptions).

The result of the ShowUI command now includes the following new methods that can be used to request the time zone and date/time settings of the client:

  • TimeZoneInfo GetClientTimeZoneInfo(string destVar)
  • DateTimeOffset GetClientDateTime(string destVar)
TimeZoneInfo GetClientTimeZoneInfo(string destVar)

This method will return the time zone of the client for the UI component with the specified destVar.

It will return null if the component does not exist, if ClientTimeInfo is not set to UIClientTimeInfo.Return, or if the component does not support the information. If the time zone information provided by the client cannot be deserialized into a TimeZoneInfo object, a SerializationException will be thrown.

If this time zone information has to be stored for later use, consider the following:

  • Use the ToSerializedString() method to get a string containing all details. Later, this information can then be restored by using TimeZoneInfo.FromSerializedString(storedInfo).

    Note

    The time zone information that is returned might not be the most recent and could result in incorrect time interpretations.

  • Use the Id property, which can then be restored by using TimeZoneInfo.FindSystemTimeZoneById(storedId).

    Note

    The ID that is returned might not be available on the DataMiner Agent that is executing the Automation script.

For more info, see Saving and restoring time zones

DateTimeOffset GetClientDateTime(string destVar)

This method will return the date and time as it was entered in the UI block with the specified destVar, in the time zone of the client (taking into account the client's UTC offset). The DateTime property of the returned value will contain the the date and/or time in the user's time zone.

The returned value will be DateTimeOffset.MinValue if the component does not exist, if ClientTimeInfo is not set to UIClientTimeInfo.Return, or if the component does not support the information.

Important

Components that have ClientTimeInfo enabled should not have components with a destVar that contains "_DateTimeComponentClient".

Service & Resource Management: Configuring the script to be executed when a reservation goes into quarantine [ID 42067]

Up to now, when a reservation went into quarantine, the SRM_QuarantineHandling script would always be executed. From now on, when you create a reservation, you will be able to specify the name of the quarantine script to be executed in the QuarantineHandlingScriptName property.

Note
  • If the QuarantineHandlingScriptName property contains Null, an empty string, white space, or "SRM_QuarantineHandling", the default SRM_QuarantineHandling script will be executed when the reservation goes into quarantine.
  • If multiple reservations go into quarantine after a resource or reservation update, the scripts configured on the different reservations will each be executed once for the reservations in question.

NATS: NatsCustodianResetNatsRequest will now be blocked when the NATSForceManualConfig option is enabled [ID 42074]

When the NATSForceManualConfig option is enabled in the MaintenanceSettings.xml file, the NatsCustodianResetNatsRequest message will now be blocked. Instead of performing a NATS reset, it will now return an error with the following message:

Resetting NATS is blocked while the system is running a Manual Config. See https://docs.dataminer.services/dataminer/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_advanced_procedures/SLNetClientTest_disabling_automatic_nats_config.html for more information.

Note

The NatsCustodianResetNatsRequest message will also be blocked when BrokerGateway is being used.

GQI DxM: Enhanced performance when executing multiple queries simultaneously [ID 42191]

Because of a number of enhancements, overall performance has increased when executing multiple queries simultaneously.

Connection enhancements [ID 42233]

A number of enhancements have been made with regard to the connections made among DataMiner Agents as well as the connections made between DataMiner Agents and client applications.

GQI DxM: Logging can now be viewed in DataMiner Cube [ID 42352]

From now on, you can view the logging of the GQI DxM in DataMiner Cube.

Also, no new log file will be started every day anymore. From now on, a new log file will only be started as soon as the size of the existing file reaches 5 MB.

Note

Currently, DataMiner Cube only allows you to view the logging of the parent process. It does not yet allow you to view the logging of the child processes (i.e. the logging of the ad hoc data sources and the operators).

GQI DxM: Separate log file per extension library in Extensions folder [ID 42355]

From now on, a separate log file will be created per GQI DxM extension library in the C:\ProgramData\Skyline Communications\DataMiner GQI\Logs\Extensions folder.

Example:

  • C:\ProgramData\Skyline Communications\DataMiner GQI\Logs\Extensions\Library A.txt
  • C:\ProgramData\Skyline Communications\DataMiner GQI\Logs\Extensions\Library B.txt

The log entries added to those files will now each include the name of the extension as well as the name of the user. The log entry format will now be the following:

[Timestamp][Level][Extension][User][SessionId][NodeId] Message

SLLogCollector now collects the logging of the GQI DxM extensions from the Extensions folder [ID 42379]

SLLogCollector will now look for GQI DxM extension logging in the following folder:

  • C:\ProgramData\Skyline Communications\DataMiner GQI\Logs\Extensions

Fixes

Issue in SLNet could cause errors to be thrown in low-code apps [ID 40978]

Because of an issue in SLNet, after a restart of a DataMiner Agent, "not supported by the current server version" errors could get thrown in all low-code apps.

DataMiner Object Models: No longer possible to query DOM after initializing a Cassandra Cluster migration [ID 40993]

After a Cassandra Cluster migration had been initialized, it would no longer be possible to query DOM.

Cassandra: Problem with incorrect gc_grace_seconds values [ID 41939]

On systems with a Cassandra or Cassandra Cluster database, a number of issues have been fixed with regard to the gc_grace_seconds setting:

  • The gc_grace_seconds values will no longer be updated during a DataMiner restart.
  • The gc_grace_seconds value for trend data will now by default be set to 0.
  • The gc_grace_seconds value for logger tables will now by default be set to 4 hours (with TTL) or to 1 day (without TTL).

Problem when trying to update the protocol version of an element in error [ID 41962]

When you tried to update the protocol version of an element in error via DataMiner Cube, in some rare cases, a message would incorrectly appear, stating that it was not possible to update the element.

Problems with SNMP managers [ID 42014]

In the following cases, an SNMP manager configured to send SNMPv3 Inform messages would get stuck in a timeout:

  • When multiple SNMP managers were sending information to the same IP address and port.
  • When "time window" errors were thrown after the SNMP manager (configured with authnopriv or authpriv) had been restarted.

Also, "out of time window" errors could be thrown when an SNMP manager received SNMPv3 traps. From now on, in SNMPv3 mode, the first alarm sent by DataMiner to the SNMP manager will always be a PING alarm. This will allow an SNMP manager to clean up time table information, which will prevent "out of time window" errors from being thrown when receiving subsequent alarms.

Problem when deleting elements with logger tables [ID 42029]

When an element with a logger table was deleted, some items would not be removed from Cassandra and from OpenSearch/Elasticsearch:

  • SLDataGateway still contained the table definitions.

  • When the databaseName option was used, the table that had been created in a separate table schema would not be deleted.

  • In case of a Cassandra Cluster, the logger table is by default stored in the sldmadb_elementdata_<dmaid>_<elementid>_<tableid> keyspace. When an element with a logger table was deleted, the database table would correctly be removed, but the empty keyspace would still exist.

Note

When an element with a logger table is deleted, the logger table will not be deleted when it has the customDatabaseName or databaseNameProtocol option.

SLAnalytics: Memory leak due to an excessive number of messages being received following an alarm template update [ID 42047]

When an alarm template was updated, in some cases, the alarm focus manager could receive a excessive number of messages, causing SLAnalytics to leak memory.

SLAnalytics - Behavioral anomaly detection: Problem when trying to retrieve incorrect INF values from the database [ID 42069]

In some cases, INF (infinity) values would incorrectly get stored in the database. Attempts to retrieve those values would then result in the Behavioral anomaly detection feature not starting up.

DataMiner Taskbar Utility would incorrectly show a pop-up window when made to perform a DataMiner upgrade using the command prompt [ID 42135]

When you made SLTaskbarUtility perform a DataMiner upgrade using the command prompt, up to now, a pop-up window would appear when the DataMiner Agent was not running. As pop-up windows are only expected to appear when running in interactive mode, from now on, pop-up windows will no longer appear when you make SLTaskbarUtility perform actions using the command prompt.

Not possible to simultaneously update multiple TTL settings [ID 42139]

In some cases, it would not be possible to simultaneously update multiple TTL settings.

MessageBroker: Subscriptions that had been disposed of would incorrectly get recreated [ID 42164]

After a MessageBroker client had disposed of a subscription and had reconnected to NATS, in some cases, the subscription would incorrectly get recreated.

Problem when NATS sessions were disposed [ID 42281]

In some rare cases, an exception could be thrown when NATS sessions were disposed.

GQI DxM: Problem when executing a query using ad hoc data sources with real-time updates enabled [ID 42310]

When a query using ad hoc data sources was executed with real-time updates enabled, up to now, the following message could incorrectly appear:

Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.

Problem when exporting an element to a .dmimport file [ID 42320]

In some rare cases, exporting an element to a .dmimport file could fail.

SLNetClientTest tool: Problem when trying to connect to a DataMiner Agent using external authentication via SAML [ID 42341]

When, in the SLNetClientTest tool, you tried to connect to a DataMiner Agent using external authentication via SAML, the following error message would appear:

Unable to load DLL 'WebView2Loader.dll': The specified module could not be found.

The WebView2Loader.dll file will now been added to the DataMiner upgrade packages.

Warning

Always be extremely careful when using this tool, as it can have far-reaching consequences on the functionality of your DataMiner System.

Improve this page