Page 2 of 2
Re: nagiosxi add dell openmanage
Posted: Wed Jan 12, 2011 4:46 am
by Box293
vmt,
A simple typing mistake here.
When I execute on shell:
./check_openmanage -H 172.x.x.x
Controller 0 [PERC H700 Integrated]: Firmware '12.3.0-0032' is out of date
Cache Battery 0 in controller 0 is Charging (Ready) [probably harmless]
check_openmanage.png
Go back to the commands section and change -I to -H and all should work fine.
Re: nagiosxi add dell openmanage
Posted: Thu Jan 13, 2011 9:27 am
by vmt
ohh, okay, thanks. Now I get a response!
When I do ./check_openmanage -H 172.17.16.39 -C public --all
ESM log content: 1 critical, 0 non-critical, 226 ok
Controller 0 [PERC H700 Integrated]: Firmware '12.3.0-0032' is out of date
Im thinking there should be more, or?
tia
stefan
Re: nagiosxi add dell openmanage
Posted: Sat Jan 15, 2011 11:32 pm
by Box293
This looks like what you would expect. Clearly your server that has Dell OpenManage installed needs a firmware upgrade. You can see the status being reported as non-critical.
What else do you think should be reported?
Re: nagiosxi add dell openmanage
Posted: Wed Jan 19, 2011 10:23 am
by tonyyarusso
Poking this thread to make our script happy. Hope it's going well for you.
Re: nagiosxi add dell openmanage
Posted: Wed Feb 02, 2011 5:08 am
by vmt
Hello all,
sorry had much other work...
Im thinking there should be a lot: Networking, chassis...., all what I can see on OMSA server. Or I get only error messages when something is going wrong?
BTW, the firmware controller gives a critical when I do service checks. When i Do same check as host check then its not critical!?
tia
stefan
Re: nagiosxi add dell openmanage
Posted: Wed Feb 02, 2011 6:26 pm
by Box293
If all is OK with the Dell server then all it is going to report is OK. You are not going to get a summary of all the components and their status.
If a particular component like your PERC H700 controller needs a firmware update then you will only be notified of this.
I am unsure about the second point you made about the host check. Perhaps it has to do with the host check expecting different states (return codes) like Up / Down / Unreachable instead of OK / Warning / Critical / Unknown ?