Multiple IP Addresses in Device Info window

[Don Costello_1]

Hello,

I am experiencing a strange condition on 3 of my servers in CIM7. Each of these servers has multiple IP addresses listed in the device info page. These IP addresses are assigned to other servers on my network. As a result, I am not able to add them to my device list together. When I add one server, and then add another with an ip address that is on the original server's device list, it kicks the first server out of CIM. Does anyone know where these IP addresses are being picked up from, or what can be done to resolve? These servers are single NIC, with 1 IP address assignment per server. I have no idea why it is displaying those IP addresses. See attachment for details. Thanks!

[Scott Shaffer · Accepted solution]

This is a symptom of deploying the servers using some sort of imaging technology (the Rapid Deployment Pack, Altiris eXpress, Symantec Ghost, or simply breaking a mirrored drive pair.) This results in the agents on those servers all having the same GUID, or Globablly Unique IDentifier. To reset the servers GUID (to ensure uniqueness) perform the following steps. For Windows based systems, stop the Foundation Agent service on the server. Delete the GUID registry key "HKLM\Software\Compaq Insight Agent. " Restart the Foundation Agent service. Once this is done, the agent will generate a unique identifier for that server. Finally, have Insight Manager 7 rediscover the server and delete the Orphan_X listings.
To prevent this problem from occurring, delete the GUID from the source system prior to taking the image or breaking the mirrored pair.

Note that this GUID is a special one used and controlled by the agents and is not the same as the GUID used by Microsoft Windows 2000 and reset by the sysPrep utility. Also note that this behavior has been modified starting with version 5.2 of the Management Agents. When coupled with the latest server hardware the agents will read the GUID from the protected area of the ROM and thus this problem will not occur.

[Don Costello_1]

Brilliant! This resolved my issue... I am in the process of finding out if the servers were imaged prior to rollout ( I am fairly new to this company).

Thanks for your help!

[Andy B]

For your future reference and if your imaging software doesn't have the facility to make GUID's unique. There is a Microsoft utility called 'System Preparation Tool' that does this

http://www.microsoft.com/windows2000/downloads/tools/sysprep/default.asp

Run it on the machine before taking the image and when the image is deployed it runs a setup (can be made silent if I remember correctly).

[Ed Cox]

As a general FYI...
R.D.P. uses a utility in the image capture process called CPQPrep (IF you START the image process through the Windows OS via the AClient vs. Rdeploy via the command line).
It goes into the registry on the machine where you are going to capture the image and it deletes the GUID prior to the image capture. So that when you deploy the image onto another Proliant the image is without a GUID, forcing the Foundation agent to create a new one.
Ed