General Main Release 10.5.0 CU8 - Preview

Important

We are still working on this release. Some release notes may still be modified or moved to a later release. Check back soon for updates!

Tip

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

Enhancements

DxMs upgraded [ID 43642]

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

• DataMiner SupportAssistant 1.7.7

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

Fixes

Protocols: Problems with pollingRate attribute [ID 43418]

A number of issues have been fixed with regard to the pollingRate attribute, which allows you to slow down polling for specific SNMP columns in a table by specifying a minimum interval (in milliseconds) between polling.

• Using pollingRate would not work when the element was using the production version of the protocol or when the partialSNMP option was specified in the table options.

• Up to now, the decision to poll a column was taken by SLSNMPManager, which relied on the Polling.xml file that was stored alongside the Protocol.xml file. From now on, SLProtocol will determine which columns will be polled independently of the Polling.xml file.

Note

The StreamViewer will now indicate more clearly which columns were polled. When some columns were polled while others were skipped, the message [PollingRate polled column PIDs xxx,yyy] will be shown. Also, when the timer was faster than the polling rate, the message No column reached the PollingRate interval. will be shown, and no Get operation will be executed.

Problem when trying to update the log levels of an element that was not hosted on the local DataMiner Agent [ID 43582]

When you tried to update the log levels of an element that was not hosted on the local DataMiner Agent, up to now, the update request would incorrectly be ignored and would not be forwarded to the DataMiner Agent hosting the element.

From now on, the update request will correctly be forwarded to the DataMiner Agent hosting the element where it will be processed accordingly.