check_openmanage internal error

[Trond Hasle Amundsen]

Adam Caines <acaines at lab.icc.edu> writes:

> Looks like it's reporting "path health".  The 6e has both sas ports
> connected to redundant controllers in the MD1120.  It's strange on
> another server, I also have a PERC H700 connect to a MD1220 with
> redundant links and it does not output the "path health" section.

[snip]

> ID             : 0
> Status         : Ok
> Name           : Logical Connector
> State          : Ready
> Connector Type : SAS Port RAID Mode
> Termination    : Not Applicable
> SCSI Rate      : Not Applicable
>
> Path Health
> Status : Ok
> Name   : Connector 0
> State  : Available
>
> Status : Ok
> Name   : Connector 1
> State  : Available

Yes, so this is the culprit... check_openmanage did not expect this
output. It looks like the controller is connected to the enclosure in
redundant path mode, according to the OMSA documentation[1]. I really
need to see how this looks with SSV format, can you provide the output
from this command:

  omreport storage connector controller=1 -fmt ssv

In case of redundant path mode, the plugin should check the path health
and report on it, in addition to the connector health. This
functionality must be added to the plugin.

Is it possible for you to check how check_openmanage handles this when
checking via SNMP as well?

[1] http://support.euro.dell.com/support/edocs/software/svradmin/6.4/en/CLI/HTML/reportst.htm#wp1077100

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

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
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