I also have the same problem mentioned above with the HP Physical Disk Temperature. I ran the vbs scripts manually and they only return null, even though status and hourson return proper values. I have just disabled the item in my HP monitoring because it isn't critical, but it would be nice to get working, if anyone knows of an update.
Ad Widget
Collapse
Complete HP server hardware monitoring ZBX2
Collapse
X
-
I also have the same problem mentioned above with the HP Physical Disk Temperature. I ran the vbs scripts manually and they only return null, even though status and hourson return proper values. I have just disabled the item in my HP monitoring because it isn't critical, but it would be nice to get working, if anyone knows of an update.
Same problem here, I'm afraid that HP have made some changes in their HP "Smart Array Configuration" CLI tool.
@mmarkwitzz, By any chance, did you try to update your vbs script for it ?
Your template is still brillant tho (dl360e g8).
Thanks a lot.Comment
-
Good News, I finally found where the problem was...
HP did change something in their smart array configuration utility product... => The name "HP Array Configuration Utility (ACU)" is now "HP Smart Storage Administrator (SSA)". So the installation path entered in the VBS script (zabbix_hp_wbem.vbs) is now wrong.
I changed the rows 603 to 606 like in the scripts "zabbix_hp_wbem.vbs" below :
If (objFSO.FileExists("C:\Program Files (x86)\Compaq\Hpacucli\Bin\hpacucli.exe")) Then
strHpacucli = "C:\Program Files (x86)\Compaq\Hpacucli\Bin\hpacucli.exe"
ElseIf (objFSO.FileExists("C:\Program Files\Compaq\Hpacucli\Bin\hpacucli.exe")) Then
strHpacucli = "C:\Program Files\Compaq\Hpacucli\Bin\hpacucli.exe"
Became :
If (objFSO.FileExists("C:\Program Files (x86)\HP\hpssacli\bin\hpssacli.exe")) Then
strHpacucli = "C:\Program Files (x86)\HP\hpssacli\bin\hpssacli.exe"
ElseIf (objFSO.FileExists("C:\Program Files\HP\hpssacli\bin\hpssacli.exe")) Then
strHpacucli = "C:\Program Files\HP\hpssacli\bin\hpssacli.exe"
You can find the vbs script in attachement (zip).
Have a good day!Attached FilesComment
-
I found a bug in the Power Meter discovery section that was resulting in a discovery error of "Value should be a JSON object." The version of the discovery script that I am using has the latest date on the top of 2012.06.29.1.
For me it was on line 867:
This resulted in an unnamed result during the discovery:Code:PowmetPairs(PROP_PMETNO, x) = PROPNAME_PMETNO & "|" & strNo
Code:zabbix_get -s admin01 -k hp.discovery[powmets] { "data": [ { "{#}":"1", }, { "{#}":"2", } ] }
That line had a variable typo, it has to be fixed in two places on that line (PMETNO to POWMETNO):
I think this should result in the discovery working. Has anyone else seen similar or gotten this to work?Code:PowmetPairs(PROP_POWMETNO, x) = PROPNAME_POWMETNO & "|" & strNo
Code:zabbix_get -s admin01 -k hp.discovery[powmets] { "data": [ { "{#POWMETNO}":"1", }, { "{#POWMETNO}":"2", } ] }Comment
-
I think u rightAs descibed in
http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200#api_access_changes
I don“t know how i could give or look if the user have api access permission.
So, i inserted the "print $res;" in line 60 and the result is the same like before.
Hmm, maybe i need some packages for perl or php5 for parsing json ?
Greetings
abibobaComment
-
Hi, just to confirm that this template works with (Zabbix 3.4). I'm currently carrying out some testing and also making some amendments to the existing old template to show the correct values and status of the hardware, please see attached picture. I will provide everyone my findings and instruction after testing has been completed.
UPDATE: 03.01.2019
HPE Server Hardware Monitoring Template ZBX V2.2 For Zabbix 3.4 MPA (ACTIVE AGENT)
Please See The New Modified Template HERE
*** Please Download and Test ***Last edited by DeltaCentral; 03-01-2019, 12:41.Comment
Comment