<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> On 06/18/2013 07:55 PM, <a class="moz-txt-link-abbreviated" href="mailto:nagios-users-request@lists.sourceforge.net">nagios-users-request@lists.sourceforge.net</a> wrote: <blockquote cite="mid:mailman.57477.1371603313.14365.nagios-users@lists.sourceforge.net" type="cite"> <pre wrap=""><div class="moz-txt-sig"><div class="moz-txt-sig">Date: Wed, 19 Jun 2013 02:41:02 +0200 From: Trond Hasle Amundsen <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:t.h.amundsen@usit.uio.no"><t.h.amundsen@usit.uio.no></a> Subject: Re: [Nagios-users] Problem with check_openmanage plugin and storage To: Nagios Users List <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:nagios-users@lists.sourceforge.net"><nagios-users@lists.sourceforge.net></a> Message-ID: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:15tk3lrrkyp.fsf@tux.uio.no"><15tk3lrrkyp.fsf@tux.uio.no></a> Content-Type: text/plain; charset=utf-8 Nic Bernstein <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:nic@onlight.com"><nic@onlight.com></a> writes: </div></div></pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> We've recently been experimenting with Trond Hasle Amundsen's check_openmanage > on a large network with about a hundred Dell servers of various ages, > capabilities, etc.? Mostly PE-2950, R210, R410 and R720.? Much thanks to Trond > for all his great work on Nagios plugins and other projects, by the way. > > We've hit a wall, however, with the storage monitoring aspects of this plugin. > > For example, here's a quite specific case.? This is a new PE R720, in debug: > > onlight@monitor:~$ check_openmanage -H host -C secret -d > System: PowerEdge R720 OMSA version: 7.1.0 > ServiceTag: ####### Plugin version: 3.7.9 > BIOS/date: 1.2.6 05/10/2012 Checking mode: SNMPv2c UDP/IPv4 > ----------------------------------------------------------------------------- > Storage Components > ============================================================================= > STATE | ID | MESSAGE TEXT > ---------+----------+-------------------------------------------------------- > OK | 0 | Controller 0 [PERC H310 Mini] is Ready > WARNING | 0:0:1:0 | Physical Disk 0:1:0 [Ata ST2000DM001-9YN164, 2.0TB] on ctrl 0 is Online, Not Certified > WARNING | 0:0:1:1 | Physical Disk 0:1:1 [Ata ST2000DM001-9YN164, 2.0TB] on ctrl 0 is Online, Not Certified > OK | 0:0 | Logical Drive '/dev/sda' [RAID-1, 1862.50 GB] is Ready > OK | 0:0 | Connector 0 [SAS] on controller 0 is Ready > OK | 0:1 | Connector 1 [SAS] on controller 0 is Ready > OK | 0:0:1 | Enclosure 0:0:1 [Backplane] on controller 0 is Ready [...] > This run exits with 1 (WARNING). > > We're not sure we agree with the decision to make the fact that a disk is not > Dell Certified a Warning, but we can at least understand that.? So, what if we > exclude storage, with --no-storage? </pre> </blockquote> <pre wrap="">The decision to create a warning for non-certified disks belongs to Dell. I've tried to let the plugin simply relay the warning level from Openmanage, unless it's outright wrong (such as reporting disks in predictive failure as OK).</pre> </blockquote> Yes, we completely understand that, and the use of the global status flag. I should have been clearer that we get that it wasn't your choice. <blockquote cite="mid:mailman.57477.1371603313.14365.nagios-users@lists.sourceforge.net" type="cite"> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> onlight@monitor:~$ check_openmanage -H host -C secret -d --no-storage > System: PowerEdge R720 OMSA version: 7.1.0 > ServiceTag: ####### Plugin version: 3.7.9 > BIOS/date: 1.2.6 05/10/2012 Checking mode: SNMPv2c UDP/IPv4 > ----------------------------------------------------------------------------- > </pre> </blockquote> </blockquote> [...] <blockquote cite="mid:mailman.57477.1371603313.14365.nagios-users@lists.sourceforge.net" type="cite"> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> OOPS! Something is wrong with this server, but I don't know what. The global > system health status is WARNING, but every component check is OK. This may > be a bug in the Nagios plugin, please file a bug report. > > This yields exit code 3 (UNKNOWN). </pre> </blockquote> <pre wrap="">This is a bug. Using blacklisting or check manipulation (such as --no-storage) should disable the global health check.</pre> </blockquote> Okay, that's what we'd expect. <blockquote cite="mid:mailman.57477.1371603313.14365.nagios-users@lists.sourceforge.net" type="cite"> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> Now, just for argument's sake, let's say we obviate the check for certified > drives, by commenting out the ????? "workaround for OMSA 7.1.0 bug" code (just > a handy little short-cut).? Here's what we get then: > [...] > Again, as with the original case, exit code is 1 (WARNING). > > Is there any way around this?? Should I be disabling global health checks?? </pre> </blockquote> <pre wrap="">Openmanage contains a bug that flips the reported warning level wrt. certified disks. Any certified disks are reported as non-certified and vice versa. The output above is expected when you remove the workaround in the code. </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> Here's a run to test that, and it works: > > onlight@monitor:~$ check_openmanage -H host -C secret -b pdisk=all > OK - System: 'PowerEdge R720', SN: '#######', 16 GB ram (4 dimms), 1 logical drives, 2 physical drives </pre> </blockquote> <pre wrap="">Here, the physical disks aren't checked at all, and the global check is correctly disabled, so this is an expected result. </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> Interestingly, when combining the blacklist with debug ("-d -b pdisk=all"), the > exit code is 3 (UNKNOWN), but with debug off, it's 0 (OK). </pre> </blockquote> <pre wrap="">Sounds like a bug, perhaps related to the one discussed earlier. </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> So, I guess what I'm wondering is why we need to blacklist the physical disks > (pdisk) instead of using --no-storage?? Shouldn't --no-storage also cause > globalstatus to be ignored? </pre> </blockquote> <pre wrap="">Yes it should, I'll look into that, thanks for the report :)</pre> </blockquote> Great, thanks! <blockquote cite="mid:mailman.57477.1371603313.14365.nagios-users@lists.sourceforge.net" type="cite"> <pre wrap="">Regarding the non-certified disks problem... There is a special blacklisting keyword to suppress the message about non-certified disks: check_openmanage -b pdisk_cert=all Please try this and see if it resolves your issue. Using blacklisting should also disable the global health check.</pre> </blockquote> Ah, that's just what we need. Much appreciated... No, that doesn't seem to be in my version (3.7.9, downloaded yesterday) <blockquote> <pre>onlight@monitor:~$ perl check_openmanage -H host -C secret -b pdisk_cert=all Physical Disk 0:1:0 [Ata ST2000DM001-9YN164, 2.0TB] on ctrl 0 is Online Physical Disk 0:1:1 [Ata ST2000DM001-9YN164, 2.0TB] on ctrl 0 is Online onlight@monitor:~$ echo $? 1 </pre> </blockquote> I guess I'll wait for a patch. Say Trond, I sent you some notes last week about enhancements we made to your check_linux_bonding plugin. Would you prefer I re-post those to the list instead? Thanks again! -nic <pre class="moz-signature" cols="72">-- Nic Bernstein <a class="moz-txt-link-abbreviated" href="mailto:nic@onlight.com">nic@onlight.com</a> Onlight, Inc. <a class="moz-txt-link-abbreviated" href="http://www.onlight.com">www.onlight.com</a> 219 N. Milwaukee St., Suite 2a v. 414.272.4477 Milwaukee, Wisconsin 53202 </pre> </body> </html>