Cannot monitor server that HPSIM is running on

[Brent Sowers]

I'm runnning HP SIM 5.1 on a Proliant G4p server, and have set up all of the agents on the server from the Proliant Support pack 7.70, just like I have set them up on all of the other servers. HP SIM lists the local server as a system, but it does not monitor the status of itself, or even identify itself correctly. The server OS (Red Hat Enterprise Linux 4) does not show up through HP SIM, alerts that are being generated by the local server by the local agents do not show up in HP SIM, and the health status always displays good for the local server even when its not.

I've set up numerous other identical servers for HP SIM to monitor and have not had any of these problems. Is there any reason why HP SIM wouldn't be able to monitor the server where its running?

[jernatety]

Did you set the traps and identify the SNMP settings for this server?

[Brent Sowers]

Yes, I have the SNMP settings on the HP SIM server identical to the settings on the other servers that are working correctly, except the trapsink and communities specify 127.0.0.1 instead of the network IP address of the server.

[Brent Sowers]

I looked in to this a little more, and the only difference I can see is that when I perform a discovery on the local server, the following shows up in the Stdout:
"System does not have the SNMP ProLiant Server (Foundation) agents installed."
The other servers say that the SNMP Proliant server agents were found when I perform a discovery.

[jernatety]

Have you installed the insight manager certificate on that server for a trust relationship between the server and HPSIM?

Setting up the CMS to trust managed ProLiant servers:

In HP SIM, select Options>Security>Certificates>Server Certificates
click [Export]. Remember the location of the file (servcert.cert).

Next

In Internet Explorer
select Tools>InternetOptions>Content>Certificates click the Trusted Root Certificate Authorities tab.
Import the exported file in step 1, and select Automatically select the certificate store....

Then reboot and try

[Brent Sowers]

The CMS and monitored servers are all Linux. Since the one and only server that it is having trouble monitoring is itself, do I need to add the server's certificate? I would think since it's the same computer that it would automatically trust the server's certificate.

[David Claypool]

Certificate is not involved in the case you state. My guess is that your snmp.conf needs to have 'localhost' added to it.

[Brent Sowers]

I've edited snmpd.conf on the server, and added read only and read write communities, and a trapsink with "localhost", restarted snmpd, and it still doesn't identify correctly, it still says that the SNMP Proliant agents are not installed. I tried adding communities and a trapsink with the networked IP address of the server as well and the identify still doesn't pick it up.

[Brent Sowers]

I got this working by going to Options.. Protocol Settings.. System Protocol Settings, selecting the local server, and checking "Update values for this protocol" under SNMP settings. I selected to use global defaults. Once I did this, the system shows up correctly.