Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
IBM Storwize V7000 check_ibm_v7000_svc
Current Version
1.1
Last Release Date
2013-01-09
Compatible With
- Nagios 3.x
Owner
Website
License
GPL
Hits
60979
Files:
| File | Description |
|---|---|
| check_ibm_v7000_svc.pl | Version 1.1 |
| check_ibm_v7000_svc_v1_2.pl | Version 1.2 |
check_ibm_v7000_svc Nagios check
You need to configure a ssh key without passphrase for logins to your V7000 storage array. Also IBM's SVC.pm Perl Module is required and available here:
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=AW-0NK
http://www.alphaworks.ibm.com/tech/svctools
Usage: perl check_ibm_v7000_svc.pl -cluster=[IP or hostname] -check=[check] [ -exclude=[listofitems] ]
see "check_ibm_v7000_svc.pl -h" for more info
You need to configure a ssh key without passphrase for logins to your V7000 storage array. Also IBM's SVC.pm Perl Module is required and available here:
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=AW-0NK
http://www.alphaworks.ibm.com/tech/svctools
Usage: perl check_ibm_v7000_svc.pl -cluster=[IP or hostname] -check=[check] [ -exclude=[listofitems] ]
see "check_ibm_v7000_svc.pl -h" for more info
Reviews (5)
bymk_2, April 29, 2021
Seems this plugin is quite old.. saw someone mentioned bityard.org and there's other newer plugins around too.
Latest updated version which includes V7000 gen3 and iSCSI support can be found here: https://git.io/J3mJH
Latest updated version which includes V7000 gen3 and iSCSI support can be found here: https://git.io/J3mJH
Follow this link to testify your nagios configuration. Mine is working aboslutely fine & able to monitor entire IBM Storage with mostly all kind of monitoring parameters.
https://www.bityard.org/blog/2013/12/28/nagios_monitoring_ibm_svc_storwize
https://www.bityard.org/blog/2013/12/28/nagios_monitoring_ibm_svc_storwize
byGHRMSA, April 18, 2018
Hello,
I set up the supervision of 3 IBM V7000 (gen1 and gen2) for the Mulhouse hospital.
Everything works perfectly except for the exclusion of multiple hosts.
For example :
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.1.26.x -check=lshost -user=supervision
CRITICAL: SRVS3 (offline)
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.1.26.x -check=lshost -user=supervision -exclude=SRVS3
OK: all host online
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.2.26.x -check=lshost -user=supervision
CRITICAL: SRAPPLIDIS-H4 (offline) SRIMAGEVAULT (offline) SRAPPLIDIS-H3 (offline) SRAPPLIDIS-H5 (offline) SRVS3 (offline) SRAPPLIDIS-H1 (offline) SRSCCM-CAS (offline) SRSCCM-H1 (offline) SRDC5 (offline)
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.2.26.x -check=lshost exclude=SRAPPLIDIS-H4,SRIMAGEVAULT,SRAPPLIDIS-H3,SRAPPLIDIS-H5,SRVS3,SRAPPLIDIS-H1,SRSCCM-CAS,SRSCCM-H1,SRDC5 -user=supervision
CRITICAL: SRAPPLIDIS-H4 (offline) SRIMAGEVAULT (offline) SRAPPLIDIS-H3 (offline) SRAPPLIDIS-H5 (offline) SRVS3 (offline) SRAPPLIDIS-H1 (offline) SRSCCM-CAS (offline) SRSCCM-H1 (offline) SRDC5 (offline)
The separator is normally a comma.
Despite everything I do not get the expected result.
Our Storwize are in version 7.8.1.4.
Who could help us ?
I set up the supervision of 3 IBM V7000 (gen1 and gen2) for the Mulhouse hospital.
Everything works perfectly except for the exclusion of multiple hosts.
For example :
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.1.26.x -check=lshost -user=supervision
CRITICAL: SRVS3 (offline)
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.1.26.x -check=lshost -user=supervision -exclude=SRVS3
OK: all host online
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.2.26.x -check=lshost -user=supervision
CRITICAL: SRAPPLIDIS-H4 (offline) SRIMAGEVAULT (offline) SRAPPLIDIS-H3 (offline) SRAPPLIDIS-H5 (offline) SRVS3 (offline) SRAPPLIDIS-H1 (offline) SRSCCM-CAS (offline) SRSCCM-H1 (offline) SRDC5 (offline)
bash-4.1$ ./check_ibm_storwize.pl -cluster=x.2.26.x -check=lshost exclude=SRAPPLIDIS-H4,SRIMAGEVAULT,SRAPPLIDIS-H3,SRAPPLIDIS-H5,SRVS3,SRAPPLIDIS-H1,SRSCCM-CAS,SRSCCM-H1,SRDC5 -user=supervision
CRITICAL: SRAPPLIDIS-H4 (offline) SRIMAGEVAULT (offline) SRAPPLIDIS-H3 (offline) SRAPPLIDIS-H5 (offline) SRVS3 (offline) SRAPPLIDIS-H1 (offline) SRSCCM-CAS (offline) SRSCCM-H1 (offline) SRDC5 (offline)
The separator is normally a comma.
Despite everything I do not get the expected result.
Our Storwize are in version 7.8.1.4.
Who could help us ?
bymarchiom, September 7, 2016
This plugin works great for checking the health of an IBM v7000. The suggestions by daniel_cioruta are definitely needed to increase the accuracy of the lsdrive check. Once that change is made, the plugin reports back the correct status if there is a failed drive.
lsdrive check will never notify a degraded or offline disk.
You should replace the commented lines with the next line following the commented line:
my %lsdrive_states = (
#'' => 'OK',
'online' => 'OK',
'offline' => 'CRITICAL',
'degraded' => 'CRITICAL', );
} elsif ($check eq "lsdrive") {
# * online: blank
# * degraded: populated if associated with an error
# * offline: must be populated
$svc_command = "lsdrive";
$item = "mdisk member";
$item_name = "id";
#$item_state = "error_sequence_number";
$item_state = "status";
&itemcheck(\%lsdrive_states)
You should replace the commented lines with the next line following the commented line:
my %lsdrive_states = (
#'' => 'OK',
'online' => 'OK',
'offline' => 'CRITICAL',
'degraded' => 'CRITICAL', );
} elsif ($check eq "lsdrive") {
# * online: blank
# * degraded: populated if associated with an error
# * offline: must be populated
$svc_command = "lsdrive";
$item = "mdisk member";
$item_name = "id";
#$item_state = "error_sequence_number";
$item_state = "status";
&itemcheck(\%lsdrive_states)
