Warnings/errors with check_openmanage plugin

[Trond Hasle Amundsen]

"Gianluca Varenni" <gianluca.varenni at gmail.com> writes:

> Here they are
>
> --------------
> List of Virtual Disks on Controller PERC 6/i Integrated (Embedded)
>
> Controller PERC 6/i Integrated (Embedded)
> ID                       : 0
> Status                   : Ok
> Name                     : Virtual Disk 0
> State                    : Ready
> HotSpare Policy violated : Not Assigned
> Virtual Disk Bad Blocks  : Not Applicable
> Secured                  : Not Applicable
> Progress                 : Not Applicable
> Layout                   : RAID-1
> Size                     : 148.50 GB (159450660864 bytes)
> Device Name              : Windows Disk 0
> Bus Protocol             : SATA
> Media                    : HDD
> Read Policy              : No Read Ahead
> Write Policy             : Write Back
> Cache Policy             : Not Applicable
> Stripe Element Size      : 64 KB
> Disk Cache Policy        : Enabled
>
> ID                       : 1
> Status                   : Ok
> Name                     : DATA
> State                    : Ready
> HotSpare Policy violated : Not Assigned
> Virtual Disk Bad Blocks  : Not Applicable
> Secured                  : Not Applicable
> Progress                 : Not Applicable
> Layout                   : RAID-5
> Size                     : 2,792.50 GB (2998424043520 bytes)
> Device Name              : Windows Disk 1
> Bus Protocol             : SATA
> Media                    : HDD
> Read Policy              : No Read Ahead
> Write Policy             : Write Back
> Cache Policy             : Not Applicable
> Stripe Element Size      : 64 KB
> Disk Cache Policy        : Enabled

Ok, this looks perfectly normal.

> root at tinman:~# snmpwalk -v2c -c public odyssey 
> 1.3.6.1.4.1.674.10893.1.20.140
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.1.1 = INTEGER: 1
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.1.4 = INTEGER: 4
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.2.1 = STRING: "Virtual Disk 
> 0"
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.2.4 = STRING: "DATA"
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.3.1 = STRING: "Windows Disk 
> 0"
> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.3.4 = STRING: "Windows Disk 
> 1"
[...]

The results from snmpwalk also looks OK, except for the fact that the
last number jumps from 1 to 4. Where is 2 and 3? The plugin assumes that
these indexes in the OIDs are sequential, which is clearly wrong. Though
this situation is rare (never seen it before) the plugin should deal and
the fact that it doesn't is a bug.

I have a modified version of the plugin available here:

  http://folk.uio.no/trondham/tmp/

Can you give it a try to see if this one performs better?

I'm curious about the cause of this problem. Have you perhaps created a
couple of virtual disks that were later deleted? It would be interesting
to see if a restart of OMSA, reboot or powercycle resets the indexes,
but please help debug the plugin before attempting this :)

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

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
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