Hello everyone,
I have a problem with the BrokerGateway migration with a customer.
Using the dmupgrade-Package it will run without end.
Using the manual command the following error will be displayed in an infinite loop:
BrokerGateway could not be reached at https://<fqdn>/BrokerGateway/api/monitoring/getmonitoringstatus: The SSL connection could not be established, see inner exception. ---> Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
We assumed that it might be because of an invalid certificate, but could not get a new in time for the upgrade.
Instead we tried to disable https again and could not find any mentions of the fqdn in either IIS or the DataMiner Config Files anymore. We also die a complete reboot of the server. Still the error persists when trying to migrate.
We also tried to see what happens if we open the url in a browser and got a 404.
For now we have reverted to a backup and will get the certificate issue sorted before trying again.
Could there be anything else, other than the invalid certificate, that causes this issue?
Is there a way to manually tell the migration tool which ip/fqdn to use?
Best Regards,
Robert
Hi Robert,
We strongly recommend upgrading to at least 10.5.0 [CU11]/10.5.12 [CU2] before starting the migration. This ensures the latest version of BrokerGateway is installed.
https://[hostname]/BrokerGateway/api/monitoring/getmonitoringstatus should return a valid json when the DataMiner BrokerGateway is running. It will most likely say something like "Unauthorized","status":401 however, as you need to use a valid BrokerGateway-Api-Key in the header.
Since you get a 404 in your case, this means BrokerGateway could not be reached. Either because it was unavailable somehow or because the hostname was not correctly resolved.
Which SSL certificate are you currently using?
It could also be useful to check the BrokerGateway logging in C:\ProgramData\Skyline Communications\DataMiner BrokerGateway\Logs, to see if there is something wrong with the module itself.
As for your last question: the migrator tool will connect to the endpoints specified in C:\Skyline DataMiner\Configurations\ClusterEndpoints.json. These endpoints are specified as IPs for the remote nodes.
The first thing the migrator does however is go to https://[hostname]/BrokerGateway/api/monitoring/getmonitoringstatus as a way to check if everything is fine locally, so I expect that changing these would not fix the issue.
Robert, thanks for sharing – I have just started looking into 10.6 prerequisites for our environment, so no direct experience to share.. but there seems to be some dependencies for a specific 10.5 CU (CU2 or CU14?) and ClusterEndPoint softLaunch enabled.
https://docs.dataminer.services/dataminer/DataMiner_Tools/BrokerGateway_Migration.html
Can you share current and target release of this upgrade?
And is the cluster configured for gRPC or SLNet?
HTH
https://docs.dataminer.services/dataminer/DataMiner_Tools/BrokerGateway_Migration.html