Table of Contents

DataMiner Cube Feature Release 10.6.12

This Feature Release of the DataMiner Cube client application contains the same new features, enhancements, and fixes as DataMiner Cube Main Release 10.6.0 [CU9].

Note

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

Tip

Changes

Enhancements

Spectrum: Measurement point selections are now synced between clients in shared mode [ID 46513]

When a Spectrum component is in shared mode, its measurement point cycle is shared with other users. However, up to now, selecting or deselecting a measurement point would not immediately update the other connected clients.

From now on, changes to measurement point selections will immediately be pushed to the other clients.

Note

This feature will only work in conjunction with DataMiner server version 10.7.0/10.6.12 or newer.

Spectrum: Shared-mode users can now control how configuration changes are applied [ID 46514]

When a user changed the configuration of a Spectrum component in shared mode, up to now, the changes were not immediately reflected in other clients. From now on, the user can right-click the x clients button and select Push changes to other users. Other users will then receive a banner where they can apply or ignore the changes. Closing the Spectrum card also triggers the banner.

The Spectrum card behavior upon last session preset modification in shared mode setting, under Settings > Card, will control how other clients handle pushed changes:

  • Notify (default) will display the banner.
  • Skip will prevent notifications and updates.
  • Update automatically will apply pushed changes without displaying a warning.

Spectrum: Automatic standby will no longer be applied in shared mode [ID 46574]

When a Spectrum card is open, it automatically enters standby mode after the configured inactivity period. From now on, this will no longer happen when the Spectrum component is in shared mode. In addition, the standby options in the ribbon will now be disabled.

Spectrum: Preset section of Spectrum component has been adapted to the new theme [ID 46591]

The Preset section on the right side of a Spectrum component has now been adapted to the new theme.

Correlation: Warning for rules using 'Group by alarm' is now shown in red [ID 46670]

When you select a correlation rule that still uses the removed Group by alarm method, DataMiner Cube marks the rule as modified and displays a warning that the method is no longer supported. From now on, that warning will be shown in red, making it easier to see that you need to update the rule.

Spectrum: Preset loading options now behave more consistently [ID 46683]

Preset loading options now behave more consistently:

  • Selecting or loading a private or public preset no longer changes the preset content checkboxes. Your selections will be saved and restored when you reopen the Spectrum Analyzer.
  • All preset content checkboxes remain enabled. Bold labels indicate which content is available in the selected preset.
  • Last Session presets restore the session independently of the content checkboxes used to load private and public presets.
  • When you load a preset from Visual Overview, its configured loading flags are used instead of being combined with previously active flags.

The checkbox labels have also been clarified: Trace is now Reference trace, Threshold is now Thresholds, and Measurement cycle is now Measurement points.

Cluster update status: Possible statuses have changed [ID 46843]

Since DataMiner Cube version 10.5.0 CU20/10.6.0 CU8/10.6.11, the status of a cluster update is displayed next to the cluster name in the Cube header.

The possible statuses have now been changed to the following:

  • Updating... while the upgrade is in progress.
  • Update done when the upgrade was successful.
  • Update failed when the upgrade was not successful.

The Update failed status is only shown to users who have permission to view and launch upgrades.

Note

This feature will only work in conjunction with DataMiner server version 10.5.0 CU20/10.6.0 CU8/10.6.11 or newer. If no status is available, Cube will continue to show the cluster name as before, ensuring compatibility with older DataMiner Systems.

Fixes

Spectrum: Marker was shown on the first trace instead of the trace where it was added [ID 46290]

When you selected several measurement points in a Spectrum component and added a marker to a trace other than the first one, the marker was shown on the first trace when you reopened the card or loaded a preset.

The marker will now be shown on the trace where you added it.

Profiles: Instances, parameters, or definitions could be incorrectly marked as modified [ID 46468]

In some cases, a profile instance, a profile parameter, or a profile definition was marked as modified even though no changes had been made to it. This could happen when the server and client stored the same properties in different orders, causing Cube to detect a change.

Cube now compares profile instances, parameters, and definitions independently of property order, so differences in ordering no longer cause them to be marked as modified.

Service & Resource Management: Unavailable resource status could be selected manually [ID 46490]

Up to now, when you created or edited a resource in the Resources module in DataMiner Cube, you could select Unavailable in the Status box. This allowed you to manually set a resource to an invalid status.

The Status box will now only offer Available and Maintenance. If a resource is already set to Unavailable, its current status will still be displayed. Once you change it, you will only be able to select Available or Maintenance.

Spectrum: Last Session Preset could not be saved after loading a custom preset in shared mode [ID 46516]

When you opened a Spectrum component in shared mode and loaded a custom preset, up to now, it would no longer be possible to save the Last Session Preset. As a result, changes made to the custom preset could not be pushed to the other clients.

Spectrum: Preset loading flags would incorrectly affect other sessions [ID 46517]

When you loaded a preset in a Spectrum component, changing the preset loading flags would incorrectly affect all sessions instead of only the current session.

From now on, changes to preset loading flags will only be applied to the current session.

Spectrum: Banner would incorrectly always be shown to the user who pushed changes in shared mode [ID 46518]

Up to now, when you pushed changes to other users from a Spectrum component in shared mode, you would incorrectly always receive a banner indicating that changes were available.

From now on, when you push changes to other users in shared mode, you will only receive a banner when multiple Spectrum components are open in your own session. Other users will always receive a banner.

Spectrum: 'Push to other clients' button would incorrectly be enabled when not in shared mode [ID 46519]

When a Spectrum component was not in shared mode, up to now, the Push changes to other users button would incorrectly be enabled, even though nothing happened when clicking it.

From now on, the button will be disabled when the Spectrum component is not in shared mode.

Spectrum: Shared-mode banner could be too small in Visual Overview [ID 46520]

When you viewed a Spectrum component in shared mode in Visual Overview, in some cases, the banner indicating that another user had pushed changes could be too small to use.

The banner will now be displayed clearly, even when the component has limited space.

Backup module was unavailable in mixed DaaS systems [ID 46528]

Up to now, the Backup module was unavailable whenever DaaS was enabled, including systems that also contained non-DaaS agents. As a result, it was not possible to configure or run backups for non-DaaS agents in these mixed environments.

From now on, the Backup module will be available in mixed environments. It will only include non-DaaS agents, and backup settings and operations will be applied only to those agents.

The module will remain unavailable when all agents in the system are DaaS agents.

System Center - Agents: Warning messages could be incorrect when adding or removing an Agent [ID 46550]

On DataMiner 10.6.0 and newer, when you added or removed an Agent in Cube, up to now, incorrect warning messages could be displayed because Cube would incorrectly still check the legacy NATSForceManualConfig and BrokerGateway soft-launch flags.

Spectrum: Display settings would not always be applied when loading a new preset [ID 46555]

Up to now, when you created a preset in a Spectrum session in shared mode and then loaded it in another session, in some cases, the display settings would not be applied, even when the option to load them was selected.

From now on, display settings will be applied whenever the option to load them is selected.

Spectrum: Average trace visibility would no longer be saved in presets [ID 46585]

Because of an issue, the visibility of the average trace in the Spectrum component would no longer be saved in presets. As a result, reopening a preset would not restore the visibility of the average trace.

From now on, Cube will again save and restore this setting with the preset.

Spectrum: Thresholds could be missing when loading a preset [ID 46622]

When you loaded a preset containing a threshold in a Spectrum component, in some cases, the threshold could be missing.

The threshold will now be displayed when the preset is loaded.

Spectrum component would remain blank after an element restart [ID 46646]

When you restarted an element while a Spectrum component was open, the component would remain blank because it did not create a new session.

From now on, the Spectrum component will create a new session when the element is restarted.

System Center - Agents: Migration window could remain open after an element export failed [ID 46657]

When an element export failed during migration, up to now, the Element migration window could continue to show "Migration has started." indefinitely without indicating that an error had occurred.

From now on, the window will indicate that the migration finished with errors.

Services: Exclude conditions on groups could be saved incorrectly [ID 46658]

When you configured a service with a group of child elements and applied an exclude condition to that group, Cube would incorrectly save the condition as both an include and an exclude trigger, and when you reopened the service in the editor, the exclude condition would be shown as an include condition. Saving the service again could then change its behavior.

Cube will now save these conditions correctly and correct affected configurations when you open the service editor.

Spectrum: Banner text was unclear after a Last Session Preset change [ID 46668]

When another session changed the Last Session Preset of a Spectrum analyzer in shared mode, the banner in Cube said, "This spectrum element has changes to its currently loaded preset." Because this wording referred to a preset rather than the session that made the change, it could be unclear.

The banner now says, "Another session has made changes to this spectrum analyzer."

Correlation: Rules with automation script actions could be incorrectly marked as modified [ID 46677]

When you selected a correlation rule with an action to run an automation script, up to now, Cube could mark the rule as modified even though you had not changed it. This could happen when the casing of the script name in the rule differed from the name of the available script.

From now on, Cube will compare script names without taking casing into account, so a difference in capitalization will no longer cause the rule to be marked as modified.

Spectrum: Marker could jump to another trace when adding the average trace [ID 46708]

When a Spectrum component contained a single trace and no measurement points, adding a marker to the trace could cause it to jump to the average trace when you added that trace. This could happen when Combined measurement point view was disabled. The marker could also jump when you added the max or min trace.

The marker will now remain on the trace where you added it.

Embedded web pages could appear over popups [ID 46740]

When another Cube overlay was opened or closed, embedded web page content could appear over a popup. This happened because overlays shared a focus key that controlled the visibility of embedded web browsers.

Each overlay now has its own focus key, so closing one overlay no longer affects the visibility of other active overlays.

Data Display: Full-screen button did not work in pop-up windows [ID 46742]

When a table was displayed in a pop-up window before the Surveyor had been opened in the current workspace, up to now, the full-screen button would not work.

From now on, the full-screen and exit-full-screen buttons will both work. You will be able to expand and restore tables in pop-up windows without first opening the Surveyor.

Spectrum: Thresholds section could collapse unexpectedly [ID 46745]

When you opened a spectrum analyzer or switched threshold edit mode, the Thresholds section in the info panel could collapse unexpectedly.

From now on, the Thresholds section will be expanded by default and will no longer collapse automatically when you leave threshold edit mode. This makes its behavior consistent with the other sections in the info panel.

Improve this page
Advanced search syntax