Unknown systems in HP SIM 4.2 SP2

[Jason Hindson]

Even after installing the latest PSP (7.30) some, but not all, of my servers are showing as unknown systems. Is there a way to force HP SIM to report the information correctly? I hoped installing the latest agents would improve the situation, but it doesn't appear to help. I'm sorry if this has been brought up before, but there is no easy way to search this forum for previous questions. Thanks.

[Aravindh Rajaram]

After installing the Agents, did you run an Identify Systems task in HPSIM? If no, run this task.

[Jason Hindson]

Yes I've ran Identify as well as Hard/Software status polling, after the installation of the PSP.

Thanks for the thought.

[Aravindh Rajaram]

Are you trying to identify Win 2003 machines? If yes then you need to change the properties of the SNMP service to accept tokens from SIM. and also what protocols have you selected in the GLobal Protocol Settings page of SIM?

[Jason Hindson]

The unknown systems are all Windows 2000. My 2003 servers are identified properly. I'm using ICMP, HTTP, SNMP, and DMI.

[Aravindh Rajaram]

One more thought. I hpoe you have set the correct community strings. Also make sure that Insight Management Agents are installed on the managed nodes. Finally give this a try..delete the systems from HPSIM and then run a Automatic Discovery for those systems which are "Unknown" now

[Jason Hindson]

The managed node is using the Global Protocol settings, and the SNMP strings are properly configured there.

[Aravindh Rajaram]

make sure that **Insight Management Agents** are installed on the managed nodes. Finally give this a try..delete the systems from HPSIM and then run a Automatic Discovery for those systems which are "Unknown" now

[Aravindh Rajaram]

one more thought. In the system protocol setting page (NOT global protocol settings) enable WBEM and enter the credetials of the "Unknown" system and then run Identification. This should at any cost identify as server (if WMI service is running on the Win2k machine)...

[David Claypool]

HP SIM 4.2 has a feature called "Configure or repair agents" that will go out and fix any and all communication parameters with the agents.

Other than that, any chance that the systems in question are WS03? By default, SNMP is set to only respond to localhost.

[Mike Strako · Accepted solution]

Since it's Windows 2000, create traps on your SNMP target machines pointing to your CMS, also note if all agents are running on the target servers as well. Best regards.

[Jeff Hatzinger]

I had a similar problem. Eventually, I tried to manually add my CMS host to the 'Accept SNMP packets from these hosts:' option on the Security tab of the snmp service. All of the options were greyed out! Group Policy was controlling these options so I could not change it. Check to make sure someone is not forcing specific settings with Group Policy. If they are, nothing you do at the CMS is going to change these settings.

[Jason Hindson]

Thanks for your suggestions and help. I configured the SNMP service on the server and it now appears in HP SIM properly. The system is recognized by the CMS as a server and the details are populated like the other machines. Thanks all.