Unmanaged Status in SIM. - Why is this ?

[Ben_160]

1. Some systems are reported as 'Unmanaged' in SIM 4.1 - I cant understand why as these servers have the management agents installed etc....

2. When I first installed SIM 4.1, on the home page it says click here to setup managed nodes, and then gives you info asking you to install SSH on these nodes and copy public keys etc.... - is this required as I didnt do this with Insight Manager 7 and if I dont do it will it work ok ?

Thanks
Ben.

[Ivan KOVAC]

Hello

1. Check the propertis of SNMP service, trap destination, community name. Also check security tab. If you have enabled option Accept SNMP packets from these hosts add 127.0.0.1 applay, restart SNMP servis, check for HP Insight web agent is started and that's it.
After this run Identification task.

2. SSH software is not required, but if you want improved management capabilities, it is
recommended that you install these components on managed systems

ivan

[Ben_160]

Thanks for reply.
I have checked these but it still says Unmanaged.

Strange thing is that the other servers that I had working in Insight Manager 7 are reported as managed etc... and I didnt touch the SNMP Services, trap info etc, so why would it be different with these new servers?

Many thanks

[Rick Loevenstein]

Verify that SNMP and Web Agent services are started on the systems reported as unmanaged, then try running Device Identification.

[Rob Buxton · Accepted solution]

The simplest way to get device identification is via SNMP.
SNMP communication needs to have a common Read Community name. Check that SNMP in HPSIM and the Server both have a suitable community name.
To extend HPSIM, you also need a Read/Write community name, but this is not essential for discovery.
Finally, on W2003 Hosts the SNMP default changed from Accept All Hosts to Accept Selected, to test, try changing this back to allow all and rerun the Device Identification.
Note that if allow selected is selected, you need to have 127.0.0.1 as well as the HPSIM Server. You might want to try using the IP Address of the HP Server rather than name just to ensure it's not a DNS issue.