Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_hds_ams.pl
Current Version
1.0
Last Release Date
2010-06-16
Compatible With
- Nagios 3.x
Owner
Website
Hits
95910
Files:
| File | Description |
|---|---|
| check_hds_ams.pl | check_hds_ams.pl |
Plugin let you a possibility to get HDS AMS storage status using active nagios plugin checks.
Requires
1. Net::SNMP module installed
2. SNMP agent configured on the storage system.
Tested with HDS AMS500, AMS2500
If you prefer using passive checks by handling snmp traps, you better use trap handling because it is faster and get you status change immediately not waiting for plugin schedule to activate check process.
Requires
1. Net::SNMP module installed
2. SNMP agent configured on the storage system.
Tested with HDS AMS500, AMS2500
If you prefer using passive checks by handling snmp traps, you better use trap handling because it is faster and get you status change immediately not waiting for plugin schedule to activate check process.
Reviews (3)
byhardcess, February 24, 2019
Works with 2100 models too
byNapsty, October 6, 2011
Good plugin to quickly check the AMS for hardware problems. Of course more output information would be nice, but I know that HDS' SNMP information is rare.
Thanks also to user car, which fixed the perl warnings with his diff.
Thanks also to user car, which fixed the perl warnings with his diff.
bycar, December 14, 2010
This also works on our AMS2300s. Thanks for saving me some valuable time and effort.
I had a couple of minor troubles, hopefully they'll help someone.
Firstly, I had trouble because I assumed that our AMS' community string would be "public". D'oh. I found it under Storage Nav -> Arrays -> (array) -> Settings -> SNMP Agent ->Environment Settings
Secondly, the script suffers a runtime failure when it attempts to report a failure:
Use of uninitialized value in string eq at check_hds_ams line 191.
which, unless I've misunderstood, appears to be a broken test in a home-rolled join() function. The following seems to be a fix:
--- /tmp/check_hds_ams.pl 2010-12-14 14:39:30.000000000 +1300
+++ check_hds_ams 2010-12-14 19:11:29.000000000 +1300
@@ -186,9 +186,6 @@
}
}
# separate messages by commas to be human friendly
- for my $err (@errs) {
- $result .= $err;
- $result .= ", " unless $errs[-1] eq $_;
- }
+ $result .= join ", ", @errs;
return $result;
}
I had a couple of minor troubles, hopefully they'll help someone.
Firstly, I had trouble because I assumed that our AMS' community string would be "public". D'oh. I found it under Storage Nav -> Arrays -> (array) -> Settings -> SNMP Agent ->Environment Settings
Secondly, the script suffers a runtime failure when it attempts to report a failure:
Use of uninitialized value in string eq at check_hds_ams line 191.
which, unless I've misunderstood, appears to be a broken test in a home-rolled join() function. The following seems to be a fix:
--- /tmp/check_hds_ams.pl 2010-12-14 14:39:30.000000000 +1300
+++ check_hds_ams 2010-12-14 19:11:29.000000000 +1300
@@ -186,9 +186,6 @@
}
}
# separate messages by commas to be human friendly
- for my $err (@errs) {
- $result .= $err;
- $result .= ", " unless $errs[-1] eq $_;
- }
+ $result .= join ", ", @errs;
return $result;
}
