unmanaged

[Jeff T]

When viewing all the systems can someone tell my why some of them show "unmanaged"

Thank you

Jeff

[Joel Rubenstein]

This indicates that SIM can not communicate via SNMP to the system. If you click on the link for one of those systems and look at the management protocols detected SNMP will not be listed.

This is usually caused by an SNMP community string mismatch. Also,on Windows 2003 servers the default is to only accept SNMP requests from the localhost.

[David Claypool]

More completely, "Unmanaged" means that HP SIM has not been able to identify a management protocol with which to communicate with the system. That protocol could be SNMP, DMI, HTTP or WBEM.

[Jeff T]

Thanks joel and david, yes it appears to be a community sting error. I get a community name incorrect email from the managed machine.. How do I confirm what the correct community name should be?

thanks

[Joel Rubenstein]

The SNMP community string used by SIM is configured in

Options --> Protocol Settings --> Global Protocol Settings.

SIM will try each of the listed read community strings during the identify systems task.

Or you can override the global settings in "System protocol settings" on a system by system basis.

[Eric Williams_4]

I still get the 'unmanaged' alert for some of my sytems. I have added to correct SMTP traps and security settings. I set them up for 'read create'. I also set up global protocol settings to match the clients. Any more suggestions.

[Rob Buxton]

Getting SNMP correct should be enough to set resolved the unmanaged.
On W2003 Servers, if Allow Selected Hosts only is selected in the SNMP Settings then either Select Allow All Hosts (W2000 default) or ensure both localhost and SIM Server are added.