Unknown SNMP device

[NJK-Work]

Hi,

I have a device that was starting to fail (1850R) that I moved the drives over to DL380 G1. My theory was that the hardware was similar enough to move it over and it still work. Well, will a little work, I got the server up and running on the new hardware without have to reinstall the OS and applications.

However, now the device shows up as "Unknown SNMP device" in Insight Manager 7 (latest version of everything). Here is what I have done:

1) Remove the device and readded it from IM.
2) Updated to 7.1 agents and drivers
3) Ripped everything out and reinstalled the 7.0 drivers (except SNMP).
4) Updated the firmware for the latest of everything on a DL380 G1.

Other problems include unabled to determine serial number and bios version, and CPU types and count. Its like it cannot read the information from the server anymore.

Any suggestions? Should I reinstall SNMP?
Side question....when IM queries a server, where does it pull the information from? For example, does it query the BIOS? Or is the information stored in the registry? Do the agents pull the information and then feed IM? If so, where then do the agents pull this information from (BIOS, registry, etc)?

Any help is appreciated.
Nelly

[Ed Cox]

Nelly,
Try this:
Remove the server from IM again.
IM uses a guid (hex representation of the serial number) to track your server. This guid is stored in the registry. When you brought over the drives from the 1850R you also brought over the guid.

Go into the registry on the DL 380 and look for a key called hostguid. Once you find it... delete it. Then restart your Foundation agent service. This will give the server a new guid. Re-add the server in IM and run your Daily Device ID task. See if that does the trick.
Ed Cox

[NJK-Work]

Hi Ed,

Thanks for the Tip. I had already tried this and it did not fix the problem. But I appreciate you taking the time to respond.

FYI - I tried ripping out everything again including SNMP and everything I could find in the registry...same problem.

Does it need to be able to read the utility partition to gather inventory information? I think this got wacked either by moving it to the new server or the installation TrueImage 7 on the server (which creates a secure zone partition which can be used to boot to).

Thanks
Nelly

[Ed Cox]

Hmmm...
The agents get their info through the device drivers (except the Foundation Agent which can also hit the bios). So not having the F10 utility partition MIGHT be the problem. But then again...the G2s (except maybe the 380G2) and G3s don't have utility partitions at all.
Once the info has been gathered by the agents the info is stored in the registry for Windows machines and in memory for Netware servers. IM comes around during discovery (as well as Hardware Status Polling) and if it can communicate properly (string to string) it adds all pertinent info in the database. Including machine type and vendor.
How about this...
Under the Manual Discovery area there is an Edit Device option. What if you were to try and manually tell IM7 that this is a Server and here is the name and then use your "Lock" function to lock the system type to your server?
Have you tried that yet?
By the way...is rebuilding this server an option?
Ed

[NJK-Work]

Hi Ed,

Thanks again. It knows its a server - just the inventory part is not working. So it does not know what model, the serial number, CPU, etc.

Do you know where in the registry this info is kept? Perhaps I can manually edit it...

Thanks
Nelson