General Main Release 10.4.0 CU8
Note
For known issues with this version, refer to Known issues.
Tip
For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.
Enhancements
Failover: Virtual IP address check will now use both a ping and an arp command to check whether an IP address is free [ID 40516]
Up to now, on systems that do not allow ping commands to be executed, in some cases, the virtual IP address check would incorrectly conclude that the IP address was free and decide to claim it, causing the network interface card to malfunction due to IP addresses not being unique.
From now on, when the virtual IP address check has concluded that the IP address is free after having executed the required number of ping commands, it will double-check by executing an arp command.
Visual Overview: Enhanced image quality when zooming [ID 40537]
Because of a number of enhancements, the image quality of visual overviews during zoom operations in web applications has improved.
Limitations:
- In visual overviews shown on mobile devices, unlike in DataMiner Cube, grouped shapes will not ungroup when zooming.
- Scrolling on Children shapes that extend their boundaries will cause the visual overview to zoom instead of scroll. If you want the visual overview to scroll, you will have to use the scrollbar.
Visual Overview: All dynamic text in the KPI stencil will now automatically be truncated [ID 40545]
All dynamic text in the KPI stencil will now automatically be truncated with "..." to prevent it from exceeded the dimensions of a shape.
Cassandra Cluster Migrator tool: Enhanced migration of Failover systems [ID 40576]
Up to now, when the Cassandra Cluster Migrator tool (SLCCMigrator.exe) was used to migrate a DataMiner System that included at least one Failover system, the following actions still had to be performed manually:
- Checking whether all agents are stopped.
- Updating the DB.xml file on all agents to make sure the database type is set to "CassandraCluster".
- Starting all agents.
Because of a number of enhancements, from now on, no manual intervention whatsoever will be needed when the Cassandra Cluster Migrator tool is used to migrate a DataMiner System that includes at least one Failover system.
Automation: Enhanced locking when calling 'SetParameter' and 'GetParameter' on an element [ID 40682]
A number of enhancements have been made to the locking behavior in the SLAutomation process in order to prevent unnecessary holdups when interacting with the Engine and related Element objects in Automation scripts.
The following calls have been improved:
element.SetParameterand associated methods:ConnectMatrixCrosspointDisconnectMatrixCrosspointSetParameterByPrimaryKey
element.GetParameterand associated methods:GetMatrixInputForOutputGetParameterByPrimaryKeyGetParameterDisplayGetParameterDisplayByPrimaryKeyIsMatrixCrosspointConnected
SLAnalytics will now wait longer for a message from SLNet announcing that it has finished loading the configuration [ID 40729]
When starting up, up to now, SLAnalytics would wait up to 400 seconds for a message from SLNet announcing that it has finished loading the configuration. From now on, it will wait up to 20 minutes.
SLAnalytics: Maximum number of parameter changes processed by SLAnalytics will no longer be limited to 5000 per second [ID 40730]
From now on, the maximum number of parameter changes processed by SLAnalytics will no longer be limited to 5000 per second.
Protocols: Smart-serial connections now also support non-abbreviated IPv6 loopback addresses [ID 40758]
Up to now, smart-serial connections would support IPv6 loopback addresses only if they were abbreviated (e.g. ::1).
From now on, smart-serial connections will also support non-abbreviated IPv6 loopback addresses (e.g. 0:0:0:0:0:0:0:1 or similar).
SLLogCollector: Deprecated tool used to archive collected files replaced [ID 40815]
The tool used by SLLogCollector to archive the files it collects is deprecated and has now been replaced.
Important
The archives produced by the new tool can no longer be opened by the built-in Windows file archiver. To open these archives, users will now have to use third-party tools like e.g. 7-Zip.
SLDataGateway: Enhanced logging [ID 40846]
A number of enhancements have been made with regard to the logging of the SLDataGateway process.
The SLDBConnection.txt and SLCloudStorage.txt log files will now contain cleaner entries, and entries of type "Error" will also be added to the SLError.txt file.
Also, run-time log level updates will now be applied at runtime without requiring a DataMiner restart.
Fixes
ReIndexElasticSearchIndexes tool would incorrectly overwrite the existing mapping by the default mappings [ID 40073]
When the ReIndexElasticSearchIndexes tool was run, the existing mappings (which define how types should be handled) would incorrectly be overwritten by the default mappings. From now on, the existing mappings will be correctly passed from source database to destination database.
Logger tables and slatable data would not be deleted from the Cassandra Cluster database when the associated element was deleted [ID 40523]
If an element had logger tables that were stored in a database of type CassandraCluster, up to now, those logger tables would not be deleted from the database when the element was deleted.
Similarly, when an SLA element was deleted, the data in the slatable associated with that element would not be deleted.
SLAnalytics would get blocked for too long when it failed to perform a database operation [ID 40603]
When SLAnalytics fails to perform a database operation, it will retry the same operation several times before eventually giving up. While SLAnalytics is performing those retries, the cache will get blocked, causing all SLAnalytics functionality that relies on that cache to also get blocked.
In order to prevent SLAnalytics from getting blocked for too long and from taking up too much memory, from now on, SLAnalytics will perform less retries if the previous database operation it performed in the last hour also failed.
Storage as a Service: Problem when attempting to upgrade alarm masking data [ID 40625]
When a DataMiner Agent using STaaS started up, up to now, an error would be thrown when the DataMiner Agent attempted to upgrade alarm masking data to the new masking data format used since DataMiner version 10.0.0. As STaaS has only been supported since DataMiner version 10.4.0, upgrading alarm masking data is not necessary. Therefore, from now on, a DataMiner Agent using STaaS will no longer attempt to do so.
Service & Resource Management: Problem when retrieving resource pools with a property filter [ID 40642]
When resource pools were retrieved with a property filter, and one of the resource pools had "null" properties, a NullReferenceException would be thrown and no resource pools would be returned.
Note
The above-mentioned exception would only be thrown when, instead of FilterElements, (deprecated) object filters were being used.
Maps: Filter would incorrectly be altered when the filter pane was collapsed [ID 40660]
When you collapsed the filter pane, in that filter pane, the text box would be cleared and all alarm severity checkboxes would automatically be selected. From now on, when you expand or collapse the filter pane, the text box will no longer be cleared and the checkboxes will no longer be automatically selected.
Also, when you collapse the filter pane, the looking glass icon will now blink blue if a non-default filter is set.
SLAnalytics: Problem when fetching data at startup on STaaS/DaaS systems hosting more than 950 elements [ID 40790]
When, in a DataMiner System, a DataMiner Agent using STaaS/DaaS was hosting more than 950 elements, in some cases, SLAnalytics could throw errors when fetching data from the database at startup.
Word "asynchronous" would be spelled incorrectly in element log file entries [ID 40856]
In element log file, up to now, the word "asynchronous" would be spelled incorrectly as "ascynchronous" in entries notifying that an asynchronous QAction had failed. In those log entries, this word will now be spelled correctly.
Problem with SLProtocol when processing actions that occurred when an element was stopped or deleted [ID 40859]
When an unhandled exception was thrown by a QAction after an element had been stopped or deleted or when a force group action was executed while an element was being stopped or deleted, in some cases, SLProtocol could stop working.