HP SIM 5.0 server discovery

[John Lash_1]

I have one server that I cannot seem to get correctly discovered in HP SIM 5.0. It is a W2K3 server running HP PSP 7.2. The server was built and configured the same as all others but will not appear as a discovered server. If I try to manually add it by IP the error message states the IP already exists. Search of the device and IP tables in the SQL db shows that it is in fact there but it cannot be searched, displayed or deleted. All SNMP settings are correct and there are no noted system errors. I have even changed the IP and NIC ports to no avail. Note: The server was built from scratch and not an image. Any thoughts? Thanks.

[jim crick]

I had a similar issue with discovery of servers. My issue turned out to be a problem with the installation of the SIM. After many support sessions with an HP Engineer, we were left with no solid solution. I ended up re-installing SIM. Once done, all the problems went away, and I noticed that the server itself performed much more efficiently. Hope you can find a more suitable answer, but if not, this should work for you to.

[John Lash_1]

It appears only to happen with DL380 G2 Servers that have Windows 2003 installed. The systems can be checked using the https:\\servname:2381 url but they will not register with the HP SIM server when scanned. Any thoughts to a resolution appreciated.

[Rick Curtis_3]

I have a similar situation. I have about 40 servers that discover properly and show the server name in the server list. I have 2 servers, both DL380 G3 or G4 that discover and list themselves only by their IP address. All SNMP settings have been checked...Server 2003.

[John Lash_1]

Mine do not appear by IP or by name. If I attempt to manually discover by IP I get the following:

* The system could not be added for the following reasons:

A system already exists with the IP Address you provided. Please specify a unique IP address.

Like I stated in the begining of the thread, the IP's and names exist in the SQL tables of the HP SIM database, but will not display in the console.

[Joel Rubenstein · Accepted solution]

You can use the mxnode command to list all nodes discovered by SIM.

The format is mxnode -lt (nodename or IP address)

To create a file of all SIM discovered nodes

mxnode -lt > node.txt

Then you can search for the problematic IP address to determine what node SIM has attached the address to.

[John Lash_1]

Joel,

I had forgot about the mxnode -lt command. I imported the output file into Excel and could see the overlaps in IP's on some of our older Compaq servers with older agents that were from cloned sysprep images. I remembered a fix you had given me back on 08/2004 for resetting the Unique GUID. This appears to be doing the trick again.

I have included the fix for others to reference.

Thanks again!

John

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671060

It sounds like you cloned the servers from an image that had the agents preinstalled. This creates a problem with duplicate agent GUIDs. The solution is to Delete and recreate a Unique GUID for the Insight Agent Host in the registry. In order to do this follow the instructions below:

1. Stop the Foundation Agents Service

2. Start/Run/Regedit

3. Goto HKEY_Local_Machine

4. Select the Software\Compaq Insight Agent folder and locate the hostGUID

5. Select and delete the value hostGUID

6. Restart the Foundations Agents Service.

When the Foundation Agents restart a unique Host GUID is created.

You should then be able to delete and rediscover the servers.

[John Lash_1]

Joel,

Have you ever seen where the same identical hostGUID continues to get generated? What version of the agents stopped using the hostGUID key?

Thanks

John