After a lot of pressure from Skyline to upgrade our system from 10.1 to 10.2 (which caused us a lot of issues/time to resolve), management decided to upgrade to 10.2.
95% of development, bug fixes, … is performed on the DMA installation on my Localhost, which is off course no cluster.
Allthough I choose for the “Agents to upgrade” the “Unselect Cluster” option, the upgrade fails simply because VerifyClusterPorts fails. As I never will choose a cluster upgrade on my localhost, this test is absolutely not needed.
Please give me a workaround to skip this VerifyClusterPorts check, because now I cannot install 10.2 on my engineering labtop => I cannot give support or do bugfixes for typical 10.2 issues, which off course is unacceptable.
Thanks in advance for a way out
Hi Cristel,
As suggested in this post, can you verify if there aren’t any other agents / ip’s listed on the agents’ page in system center?
If that’s not the case, can you try to create a custom VerifyClusterPorts.LastRun.xml file as described here?
Hi Cristel,
Great to read it works now.
Just for your info:
The IP’s that are added to the cluster result from the IP address of your laptop that changes every time you switch wifi (or lan) networks.
Removed all agents (36), except for the pc one.
(Remark : on every boot of the pc: it gets another ip-@, and that ip-@ is added into DMS.xml as if it was ‘another’ agent on “another” cluster.)
Still the same =VerifyClusterPorts faillure.
I created the VerifyClusterPorts.LastRun.xml file with a recent date
Upgrade worked, but restart stucked on 99%.
stopt DMA with DataMiner Stop DataMiner And SLNet.bat,
removed all files in C:Skyline DataMinerUpgradesPackages
restart
Bingo : 10.2 installed + running
Hopefully everything still works fine
Thanks for the support