Upgrade from Insight Manager 7.2 to version 4.2

[Mark Blonde]

Hello,

I just ran an upgrade from Insight Manager 7.2 to version 4.2. We have two issues:

1) Our historical events did not get transferred over. The only events that we see are those that occurred once the upgrade was complete. Verifying the logs, there was no attempt to import the event data during the data migration portionof the upgrade. Is this normal?

2) Most of our Windows servers got imported with the "system type" erroneously labelled "Cluster" instead of "Server" and the product name labelled MCSC instead of the Server name (ex; Proliant 3000, Proliant D380). Does anyone know how this could be resolved?

Thanks,
Mark

[Aravindh Rajaram · Accepted solution]

1)When you migrate from IM7 to 4.2 the events are always archived and not migrated. You can access the events from the file: ~\Program Files\HP\Systems Insight Manager Data Migration Tool\user-defined-data\EventNotice.csv

2)After performing an upgrade, you must run identification before these
systems are displayed. To identify systems, select
Options>Discovery>Identify Systems, The Identify Systems page is displayed.
From this page, select all the systems ans then run the task. This should help you in getting the "system type" shown correctly.

[Mark Blonde]

Thanks for your reply. I guess I have my answer for item number 1.

As for question 2, I had run the system identification task thinking that it would update the information correctly; unfortunately, this did not resolve the issue. I even deleted some systems, rediscovered them manually and then ran the identification manually with the same disappointing results. I'm curious how Insight Manager populates those fields - ie, where is it getting the information?

Cheers,
Mark

[Aravindh Rajaram]

Mark,

Give this a try. Delete those servers from HPSIM, Enable only WBEM protocol (Options>Protocols>Global Protocol Settings), give the appropriate credentials there and then try discovering it again. This should work.

[Mark Blonde]

Thanks again. I tried what was suggested but with just the WBEM protocol enabled it is unable to get the information - the information comes back as unknown. I tried it with several passwords and it still didn't work.

Cheers,
Mark