check_openmanage not using my custom temperature thresholds

[C. Bensend]

Hey folks,

   I am trying to use custom temperature thresholds with one of my
servers, and it doesn't seem to take them into account.

   The full command (as defined in NSC.ini for NSClient++):

command[check_openmanage]=check_openmanage.exe -e -p -w 0=50 -c 0=54 -b
bat_charge=ALL/ctrl_fw=ALL/ctrl_driver=ALL --omreport
F:\dellopenmanage\oma\bin\omreport.exe

   Per http://folk.uio.no/trondham/software/check_openmanage.html and
the man page, I'm pretty sure that's supposed to set the temperature
probe 0's warning threshold to 50C and critical to 54C.  However, I'm
still getting a non-OK for temp probe 0:

Temperature Probe 0 [System Board Ambient Temp] is too high at 43 C
------ SYSTEM: PowerEdge 2900, SN: 4PVXSK1

   Just to be sure this wasn't a glitch with the display of the temp
probe #, I've tried 0=50,1=50,2=50 and 0=54,1=54,2=54 but it still
complains.

   Am I missing something?  I've looked at this until I'm crosseyed,
and I'm pretty sure I'm using it correctly.  Is there a hardcoded
threshold in there that I'm not aware of?

Thanks much!

Benny


-- 
"Show me on the doll where the marketing touched you."
                               -- "Mally" on Fazed.net



------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
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