Some issues adding a new cluster to decommit an old one

[xdatanet]

We are changing technologies behind our two productions clusters (location and OS), we have a license for two nodes, but to do this we thinked to add a new cluster (the third) with a brand new OS, then sync it with the others, after that throwing away an old one.
Following the instructions, in the process of adding the cluster, almost everythings, was done flawless.
Now we have a new cluster in the prod line, but here starts the troubles: dashboard does not work because the license limit (maybe for a limited amount of time a new cluster should be allowed to stay in line without upgrading license); anyway, the move to take offline the old node shouldn't have required too much time in our minds, we were wrong: the global config didn't write on the new (third) cluster, is it a license limit? Or should be something else to pay attention? (the node is seen correctly from others, shards are synched and so on...)

In case it is a license limit, i presume that we must decommit one of the old cluster in advance and remain with only one node in production and then add the new one, am i right?

Any ideas will be appreciated, best regards,
- Leonardo

[sgardil]

We are changing technologies behind our two productions clusters (location and OS), we have a license for two nodes, but to do this we thinked to add a new cluster (the third) with a brand new OS, then sync it with the others, after that throwing away an old one.
Following the instructions, in the process of adding the cluster, almost everythings, was done flawless.
Now we have a new cluster in the prod line, but here starts the troubles: dashboard does not work because the license limit (maybe for a limited amount of time a new cluster should be allowed to stay in line without upgrading license); anyway, the move to take offline the old node shouldn't have required too much time in our minds, we were wrong: the global config didn't write on the new (third) cluster, is it a license limit? Or should be something else to pay attention? (the node is seen correctly from others, shards are synched and so on...)

In case it is a license limit, i presume that we must decommit one of the old cluster in advance and remain with only one node in production and then add the new one, am i right?

Any ideas will be appreciated, best regards,
- Leonardo

Hey Leonardo

The addition of almost everything was done flawless is a little spooky to me. Just to be certain is the only thing that wasnt the licensing issue that you are running into? You can try decommissioning one of the licenses while spinning up the new instance to move that license over but I would say the best bet is to reach out to your CSM at Nagios and they can help you with licensing issues.

[xdatanet]

Thank You for the response, we have solved anyway. It was due to certificates server/peers, we need to copy manually and in advance all of them, otherwise the config sync wont work correctly.

[jmichaelson]

Glad you got this working. I'm gong to mark this as resolved.