Check HP P2000 API

[christudorache]

Having an issue with the Check_P2000_API plugin
I downloaded the plugin from http://exchange.nagios.org/directory/Pl ... 00/details and the specific file was check_p2000_api-v1.5.zip
Everytime I run the command, I get the following error:
CRITICAL : Disks 49 OK, Vdisk 6 OK, Temperature 18 OK, Voltage 26 OK, Overall 3 OK, Midplane/Chassis 1 OK, RAID IOM 2 OK, AC Power Supply 2 OK, 7 Critical, Enclosures 2 OK
Has this happened to anyone before, if so were you able to resolve? Let me know. Thank you.

[abrist]

It looks like the critical is due to the powersupply checks:

AC Power Supply 2 OK, 7 Critical

Do you see any errors/warnings/etc in the HP web interface for the device?

[christudorache]

I do not see any issues with the power supply. What does the 7 signify?
No errors in the event log on the storage SAN.
I checked another storage SAN and received the following:
0K : Disks 49 OK, Vdisk 4 OK, Temperature 14 OK, Voltage 28 OK, Overall 1 OK, Midplane/Chassis 1 OK, RAID IOM 2 OK, AC Power Supply 2 OK, Enclosures 2 OK

[abrist]

hmmm, I don't know where it came from. I just assume that the criticals applied to the hardware check immediately to the left in the output. You did not see any issue on the device's web ui frontend?

[Box293]

Can you post the exact command you are using.

Also, you could probably narrow down the actual part of the plugin that is causing this problem by executing the plugin with the -c argument:

Code: Select all

-c Sets what you want to do
status - get the status of the SAN
disk - Get performance data of the disks
controller - Get performance data of the controllers
vdisk - Get performance data of the VDisks
volume - Get performance data of the volumes 

Hopefully only one of these will produce a critical result, which should help narrow down what the "7 Critcal" means

[Richard_Lian]

We are having exactly the same issue. Did you get a resolution to it?

It started happening for us after a recent SAN firmware upgrade.

I can only assume that the SAN is outputting some new additional information that the script does not know how to handle, but it is a little past my skill set on how to resolve it.

Regards,

Richard

[Richard_Lian]

These are my details if they help at all.


Command
# 'Check HP P2000 SAN' command definition
define command {
command_name check_p2000
command_line $USER1$/check_p2000_api.php -H $HOSTADDRESS$ -U username -P 'password' $ARG1$
}

Checks
define service {
use generic-service
host_name SAN A,SAN B
service_description Status
check_command check_p2000!-c status
register 1
}

define service {
use generic-service
host_name SAN A,SAN B
service_description Controller CPU
check_command check_p2000!-c controller -S cpu-load -u "%" -w 75 -C 90!!!!!!!
register 1
}


PHP script is also attached as a txt file.

Regards,

Richard

[Box293]

Richard,
We can probably narrow down the actual part of the plugin that is causing this problem by executing the plugin with the -c argument:

Code: Select all

  -c Sets what you want to do
    status - get the status of the SAN
    disk - Get performance data of the disks
    controller - Get performance data of the controllers
    vdisk - Get performance data of the VDisks
    volume - Get performance data of the volumes

Can you try adding each one of these to your commands to see what one is causing the issue?

[Richard_Lian]

I have just run through each of the arguments using -c and each one reports "ok" for the relevant return apart from "status" which produces the strange output with an error

CRITICAL : Disks 45 OK, Vdisk 4 OK, Temperature 18 OK, Voltage 26 OK, Overall 3 OK, Midplane/Chassis 1 OK, RAID IOM 2 OK, AC Power Supply 2 OK, 7 Critical, Enclosures 2 OK,

It must think there is "7 Critical" on something but it does not appear to be any of the components listed.

[Box293]

I have just run through each of the arguments using -c and each one reports "ok" for the relevant return apart from "status" which produces the strange output with an error

I expect that christudorache will report the same behaviour.

I can only assume that the SAN is outputting some new additional information that the script does not know how to handle

I think you are spot on. I had a look on the authors website:

http://www.toms-blog.com/nagios-hp-msa- ... e-monitor/

And the exact behaviour has been reported on this page (the last item at the bottom of the page)

Seeing as the author updates this plugin regularly I suggest the both of you report this behaviour on that page. There really is nothing else we can help with here.