Orphaned CMS after migrating implementation to different hardware.

[David_943]

After backing up our CMS implemenation, and then recovering it onto newer hardware (same server name), the CMS is now an orphaned node within HP SIM itself (and no longer holds the devicekey value of 1 within the DB). In addition, another node continues to claim the CMS's IP Address even though it does not own it. The backup/recovery procedures used to change hardware can be found in the HP Document "Backing up and restoring HP Systems Insight Manager 5.1 data files in a Windows environment". We have used these procedures before (pre-SP1) without issue. The overall (recovered) implementation appears to be working as expected. However, I imagine an orphaned CMS is an indication of problems to come. Does anyone know how to recover an orphaned CMS node?

Thank you in advance.

[David_943]

Was able to resolve the issue by using mxnode to fix some of the basic stuff (like IP address), and manually updating the SQL tables (with HP SIM stopped) to fix some of the more hidden stuff (FQDN, node name, etc...).

[David_943]

The fix stayed for a while but eventually the HP SIM node became an orphan again. Not sure what triggered it (HP SIM restart, reboot, plugin install, etc...).

Does anyone have a true to fix to this?

Thanks.

[David_943]

Was more thorough manually updating the tables in SQL this time (after stopping the SIM service). Added the GUID (after looking up in the registry) and some other key information. Seems to have done the trick and stuck this time.