check_openmanage weirdness

[Trond Hasle Amundsen]

Greg Etling <getling at stern.nyu.edu> writes:

> Trond, thanks for your quick reply. Unfortunately it does appear we have 
> a disconnect between OMSA and SNMP:

[snip]

> [root at nagios ~]# snmpwalk -v2c -c ***** testserver 
> 1.3.6.1.4.1.674.10893.1.20.130.1
> SNMPv2-SMI::enterprises.674.10893.1.20.130.1 = No Such Object available 
> on this agent at this OID

Hmm.. you should see output like:

$ snmpwalk -v2c -c community hostname 1.3.6.1.4.1.674.10893.1.20.130.1
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.2.1 = STRING: "PERC 6/i Integrated"
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.3.1 = STRING: "DELL"
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.4.1 = INTEGER: 6
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.5.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.7.1 = INTEGER: 30
SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.8.1 = STRING: "6.2.0-0013"
[...]

> It appears to only have data under the 1.3.6.1.4.1.674.10892 and 
> 1.3.6.1.4.1.674.10899 trees. Thoughts?

Unfortunately my Windows knowledge is rather limited. I have never
installed OMSA on Windows, but I suspect that there are options to
choose from during the install. The first thing I would do is to
re-install OMSA step by step and try to figure out what I might have
missed. On Linux, the install procedure and packaging of the OMSA
components changed with version 6.2.0. This may very well be the case
with the Windows version as well.

Cheers,
-- 
Trond H. Amundsen <t.h.amundsen at usit.uio.no>
Center for Information Technology Services, University of Oslo

------------------------------------------------------------------------------

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null