I'm having an issue for an ICM upgrade from 6 through 7.0c SR4 to 7.5.x. As part of the upgrade process a RoggerA and RoggerB are built based on ICM7.0c using an EDMT import of the 6.0 database and a copyof the ICM registry key tree from each respective source Rogger i.e. apply RoggerA 6.0 registry tree to new tech refresh RoggerA 7.0 and apply RoggerB 6.0 registry tree to RoggerB 7.0. This is the process described in the upgrade guide.
However, when RoggerB is installed and rebooted after the ICM7.0c install, it attempts to run both RouterB AND RouterA on the same server. It suddenly seems to think it is now RouterA as well as RouterB. The registry now shows a new tree for RouterA, icmsetup shows RouterA and the process attempt to run RouterA. The real RouterA has already been installed, is running and is connected via bopth public and private network.
I've trawled the release notes for ICM 7.0c through to SR4 but can't see a mention of this issue which would be a pretty major problem.
We have fixed the issue by deleting the RouterA registry tree before rebooting the server and also deleting the entry via icmsetup, which should mean we can then move on to upgrade to ICM7.5. However, I'm concerned that this isn't a good starting point for a new 7.5 build so would like to understand why this issue is occuring.
Is there a patch that I am missing here?