Anyone have a working template for an HP P2000 MSA storage array?
Ad Widget
Collapse
Working template for HP P2000 MSA Storage Array
Collapse
X
-
Tags: None
-
-
-
What happens if you execute the script in order to verify it is working. Adjust the username/password and run the following
Code:./hp-msa.pl >controllerip> lld controller
Comment
-
I will have to check when I am back in the office. I can't remember the error off the top of my head but I did get errors. I don't know that the script was ever actually trying to run. I gave the zabbix user execute permissions on the hp-msa.pl file and that error went away.Comment
-
this is the command I run.
perl /usr/lib/zabbix/externalscripts/hp-msa.pl
this is the output
Usage: hp-msa.pl <hostname> [lld|stats] at /usr/lib/zabbix/externalscripts/hp-msa.pl line 91.
Comment
-
Update to above. Ran this command perl /usr/lib/zabbix/externalscripts/hp-msa.pl >10.1.1.20> lld controller
This is the output
Unsuccessful stat on filename containing newline at /usr/share/perl5/XML/Simple.pm line 967.
Unsuccessful stat on filename containing newline at /usr/share/perl5/XML/Simple.pm line 980.
File does not exist: Can't connect to controller:80 (Temporary failure in name resolution)
Temporary failure in name resolution at /usr/share/perl5/LWP/Protocol/http.pm line 50.
at /usr/lib/zabbix/externalscripts/hp-msa.pl line 104.
Not sure where to go from here. BTW I'm on Ubuntu.Comment
-
I am using HP MSA p2000g3
I took the template HPE MSA 2040 Storage by HTTP and this template collected data on the state of controllers, pools, IOPs, and most importantly - the state of disks
It doesn't work great, but it worksComment
-
Update of my last post:
the template for HPE MSA 2040 Storage by HTTP does not really work. For me, using it caused the controller to freeze and issuing other troubles.
I made a small set of scripts for polling the storage via ssh, the polling is done from any host, I did it from the Zabbix server itself. The script collects data using a standard cli command for HP MSA P2000, does a little preprocessing, and sends it to Zabbix as logs via template. Triggers are based on detecting events in the log. This suited me, any suggestions to make it better are welcome.
Github:
-
Comment