Dyantrace Managed requires fixed IP address, what does Mission Control store (public IP, private IP?)?

[krokkas]

Client is insisting on installing Dynatrace Managed on AWS through Dev, then QA, then Prod. I've told them they require a Fixed IP, but need to check what Mission Control thinks is the fixed IP?

[Radoslaw_Szulgo]

Mission Control does not rely on internal network IP addresses. What is only required is to set up a network to allow outgoing communication to Mission Control's front-end server. Fixed IP is needed on Managed components e.g. server nodes because of internal communication between nodes.

More at:

https://help.dynatrace.com/dynatrace-managed/dynat...

Is that OK for you?

[krokkas]

So to be clear, if I move the Dynatrace Server between environments (uninstall in environment A and install in environment 2), Mission Contol won't care that the IP of the Server has changed, and I will just need to repoint the agents to the new Server install?

[krokkas]

above comment meant for @Radoslaw S.

[Radoslaw_Szulgo]

Mission Control won't care about IP. It cares only about cluster UUID and license key.

But the Dynatrace Server cares, because of internal communication to Cassandra, Security gateways etc. So it may not work when you move the cluster node to the other network.

What I suggest, is to set up 3 clusters in each stage - Dev, QA and Production - in case you need to manage Cluster and agent versions manually. If it is only a matter of staging agents, then it's enough to create 3 Environments (aka tenants) in the cluster and manage agent versions per environment {dev, qa, prod}.

[krokkas]

Hi @Radoslaw S., that begs a new question. Under the 1 licence key, can the client install a Dynatrace Server in each of Dev, QA, Prod and have all 3 running at the same time? I was under the impression that they could only have the Server running in one environment at any one time. The idea being the Dynatrace Server ended up in production and the each environment was a separate tenant.

[Radoslaw_Szulgo]

Of course 1 license = 1 cluster.

But on 1 license and 1 cluster you can create multiple environments (tenants)

[krokkas]

Fantastic, no more questions for now, thank you @Radoslaw S.

[Radoslaw_Szulgo]

your welcome.

[krokkas]

Hi @Radoslaw S. So we uninstalled the Dynatrace Server from the Dev environment and went to install it on the QA environment, but the installation is failing stating the "License is already used or no longer valid for installation." How do we proceed?

[krokkas]

@Radoslaw S. please ignore above message, a new licence key had been issued.

[guido_deinhamm]

Hi Kyle,

whenever you install a new Dynatrace cluster you need a license that is not already in use by another cluster.

So if you uninstall a cluster and re-install it somewhere else, then currently your license needs to be released manually by Dynatrace staff.

We are currently working on a solution so that whenever you completely uninstall a Dynatrace cluster its license is released automatically. That feature should be available in early September.

I had a look at your license and have released it for you. You should now be able to install a new cluster with the existing license.

Hope that helps,

Guido

[Radoslaw_Szulgo · Accepted solution]

Good news! We now support backup-restore to hosts with different IPs:

https://www.dynatrace.com/news/blog/dynatrace-managed-feature-update-version-1-162/