1823753 Members
4112 Online
109664 Solutions
New Discussion юеВ

SNMP Alias

 
SOLVED
Go to solution
Doug Wogan
Regular Advisor

SNMP Alias

Try this one on for size. I've got two Windows 2000 clusters. Built from the same drive using ghostwalker to strip the sid and rename the node. I try and manually add each node in the database and can only keep one in at a time. If I search for the device that I just added everything looks good except for the SNMP Alias. Meaning if I add NTSERVER1 and go to the device information it shows NTSERVER1 for the Device Name, SNMP Alias, and DNS Name. If I add NTSERVER2 and go to the device parameters it shows NTSERVER1 as the SNMP Alias. If I add NTSERVER3 it also shows NTSERVER1 as the SNMP Alias. Any ideas?
2 REPLIES 2
Ed Cox
Respected Contributor
Solution

Re: SNMP Alias

This may along the lines of Ghost duplicating the GUID. This is the unique parameter in the registry that the Foundation Agent reports to IM 7. Consider it our Agent "sid". Ghostwalker has no idea what an Insight Agent GUID is. So therefore it doesn't strip it out.
Go to your NTServer2 registry. Search for a key...something like: hostGUID .Looks like it has a hexidecimal representation of the SMBIOS serial number. Delete the key. Restart your Foundation Agent and it will create a unique GUID based on the local BIOS.
Let me know if this does the trick.
If IM 7 sees two identical GUIDs it basically wets the bed and can't deal with that. A tell tale sign is that if you add NTServer1 and look at it's property page, you'll see multiple IP's associated with it, or rather more IP addresses than it should have.
Good luck!
Ed Cox
Doug Wogan
Regular Advisor

Re: SNMP Alias

Ed.
Even though you are a Bucks fan I appriciate the help. That did the trick. I did have multiple IP's associated witht he devices like you said. I deleted the reg key, restarted the service and all is good now.
Thanks again for your help.
Doug.