I paired 2 cloud based DM Legs, configured VIPAcquired.ps1 file and run it with Powershell. However there are 2 issues which randomly acquire usually on inactive leg. Running PowerShell sometimes give us this error, although after rebooting EC2, it'll resolve and the error appear on the other leg and sometime the server is not accessible although the EC2 is running. As the result of these problem, the failover is not working and sometimes the DM stuck in Disconnected state until the server or EC2 is rebooted. Any suggestion?
Another new message for disconnected server. Is this something which DM may caused?
Normally DataMiner should execute the script automatically:
more information can be found here:
Were you able to create the access key, and do the other steps from the configuration?
Hi Bert, I upgraded to version 10.3.6 but still there is issue with failover and disconnection from server. Sometimes when restart on A leg happens, it auto failover to B and disconnect A. So we can reach A server unless we use IP address to RDP, and also sometimes both A and B of the same pair are running. So for example we can run DM on A leg but if we check Agents, it shows VIP is on B, and B is also running. This is causing Issue accessing Dataminer.Services and cloud connection
I'm not sure about the PowerShell script giving errors, but I've experienced the NLA error as well when trying to do an RDP. In my case this was effectively related to DataMiner and fixed with an upgrade to the latest version. And since this is some kind of network issue, your PowerShell script might also fail because of the same reason.
Which version are you running? Could you try the latest feature release available here?