Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

CNAMTS DCRUM migration from 12.2.2 to 12.3.5

Dynatrace Helper
Dynatrace Helper


The CNAMTS DCRUM environment consists of 2 DCRUM platforms:

-SUD with 5 CAS, 3 ADS, 1 CSS

-GE with 3 CAS, 3 ADS, 1CC

These platforms share 1 RUM console and 5 AMD probes.

For this migration, there were 4 phases :

1) The 2 CSS and the RUM Console have been migrated

2) The CAS and the ADS servers of the GE platform have been migrated

3) The CAS and the ADS servers of the SUD platform have been migrated

4) The AMD probes have been migrated

To be successful, the DCRUM migration needs preparation:

If the migration is completely successful for the customer, we encountered these problems :

  • some CSS users passwords were declared as obsolete but it was impossible to reset the password. The workaround solution was to reset the passwords manually in the CSS interface (call SUPDCRUM-9389)
  • in the RUM console, it was impossible to define farms with the CAS/ADS in version 12.3. The issue was resolved by resetting the UUID of the CAS and ADS servers (call SUPDCRUM-9876). The verification of the UUID should be in the migration preparation process.
  • after the migration, in the DMI report datasource, the names are the IP addresses instead of the description (call SUPDCRUM-10025). The issue is resolved in version 12.3.6.
  • after the migration, in the DMI report, the metric "Tier" was changed to "Tier (obsolete)" (call SUPDCRUM-10212). Normal behaviour, the metric id changed with the migration and has to be manually changed in the DMI reports definition.

Regards, Antoine Buffotot


Dynatrace Pro
Dynatrace Pro

Thank you for sharing.