Hello forum,
We are looking for tips on why we are unable to see HW status in a HP ML370 G5 in Orion SAM. Windows/application monitoring works OK.
Ran the Solarwinds SNMP utility and installed HP agent.
Discovery runs w/o errors.
Thx,
Sky2830
How is the Node Managed in Orion? Is this an SNMP managed node or WMI Managed Node? If it's SNMP, was SNMP enabled/configured before HP's Insight Manager Agent was installed, or after? Also, have you ensured all required vendor components are installed? In your case you should double check that the HP Insight Management WBEM Providers for Windows Server 2003/2008 software is also installed, if the node is managed via WMI in Orion.
Lastly, once you've checked/rechecked those items, did you click "List Resources" from the Node Management section of the "Node Details" view? Is Hardware Health listed as an option for this node?
Thanks for the prompt response.
The SNMP test fails at the Node Management. Works OK for all other Server 2003 nodes. This seems odd.
The HP agent we installed is the same we installed at dozen other W2003 boxes (HP Proliant agent cp014537.exe).
This particular server is W2003 R2 SP2 EE Terminal Services server. The others are W2003 Std Ed. Some are R2. None are Terminal Services Servers.
There is is Windows component "Hardware Monitoring" in this version in the Windows Management/Monitoring tools setup. Should we be using this.
Regards,
I tested the SNMP connectivity using 3rd party testers. It fails with error -2003 IIRC. Adjacent I.P.s work OK.
Windows firewall at this 2003R2 EE SP2 is not turned on. Could it by default block SNMP if not enabled and configured to allow SNMP?
***********************
Update:
The Solarwinds discovery polling test with SNMP now passes. Community string "Public" works, but "public" does not. Case sensitive?
Further testing seems to show that our other Server 2003 nodes do not care about community string case, but this one Server 2003 R2 EE SP2 does.
Has anyone else seen this?
We still do not get any HP hardware information from this server.
SNMP Community Strings are case sensitive based on the RFC. I can't comment on how each vendor implemented their SNMP Agent, but if they followed the RFC then it should be case sensitive.
As for not seeing Hardware Health, this is normal behavior if SNMP was enabled after the vendor agent software was installed. Since SNMP wasn't enabled the vendor MIBs weren't able to register with the SNMP agent. You should uninstall the HP SIM agent software from the server and install the absolute latest version available from HP's website. This should resolve the issue.
