Ad Widget
Collapse
Monitoring Intel/LSI/Symbios RAID controllers
Collapse
X
-
create the value mapping manually, there are only a few:
Name: LSI RAID BBU & LD Status
Value: 0
NewValue: Optimal
Value: 1
New Value: Failed
Name: LSI RAID PhysDrv Status
Value: 0
NewValue: (Online|Hostpare|Unconfigured good)
Value: 1
NewValue: FailedComment
-
hi ArtemK,
thanks for the template - working great! There is one thing though - the trigger "RAID info is outdated" doesn't seem to clear. It looks like it is a nodata trigger for 720. However, the array status is normal, but this alert won't clear. Any thoughts?Comment
-
It's just checking if you are getting new data constantly, as by default data is submitted to zabbix server by trapper. So, you can have normal status for array, but this data can be outdated, if your script fails for some reason and doesn't submit new values to zabbix server, so check that you get new valuesLast edited by ArtemK; 22-03-2018, 17:09.Comment
-
I have a few newer Intel cards that I am trying to monitor with the scripts and Zabbix (active). I've tested the script on an Intel RS3DC080 Raid Controller as well as an older RMS25PB080 Raid Controller with the same results. I tried CmdTool2_64.exe, MegaCli64.exe, and Storcli64.exe but the only one I could get to see those cards was storcli64.exe. I modified the 3 scripts to point to storcli.exe and got some info but I'm not getting everything. Any suggestions on how to get this functioning properly with only storcli or how to make the other utilities work with my card. I ran CmdTool2 as admin to no avail.
Comment
-
I was afraid you were going to say that. Guess I better start learning powershell :-p. More of a bash fan myself but the line of work I am in requires windows.Comment
-
I went through and tested each command on storcli64.exe and it outputs the correct information yet the output of the trapper script only has this in it
- hw.raid.bbu[0,"bbu_state"] "0"
- hw.raid.logical_disk[0,0,"vd_state"] "0"
- hw.raid.physical_disk[0,252,0,"media_errors"] 0
- hw.raid.physical_disk[0,252,0,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,0,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,1,"media_errors"] 0
- hw.raid.physical_disk[0,252,1,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,1,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,2,"media_errors"] 0
- hw.raid.physical_disk[0,252,2,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,2,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,3,"media_errors"] 0
- hw.raid.physical_disk[0,252,3,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,3,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,4,"media_errors"] 0
- hw.raid.physical_disk[0,252,4,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,4,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,5,"media_errors"] 0
- hw.raid.physical_disk[0,252,5,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,5,"firmware_state"] "0"
- hw.raid.physical_disk[0,252,6,"media_errors"] 0
- hw.raid.physical_disk[0,252,6,"predictive_errors"] 0
- hw.raid.physical_disk[0,252,6,"firmware_state"] "0"
For example I ran '.\storcli64.exe -pdinfo -PhysDrv["252":"0"] -a 0 -NoLog | Select-String "Raw Size:\s+(\d+\.\d+\s..)" -AllMatches | % { $_.Matches } | % {$_.groups[1].value }' which came back with '3.638 TB' but for whatever reason it doesn't output to 'zsend_trapper_data.txt' when running the script.
Any suggestions on where to go from here?Comment
-
I think it works perfectly fine. Such items as disk size, raid volume size, etc (these changes rarely) are checked using zabbix agent, not trapper. So you should check, that your zabbix agent is configured correctly (you've added needed userparameters, right?)Comment
-
Sorry to waste your time. After letting it sit overnight everything pulled properly. Thanks for the assistance.Comment
-
Hello guys.
I am having a problem executing the parameter, it is giving an error.
PS C:\Users\Administrador> C:\Windows\System32\WindowsPowerShell\v1.0\powersh ell.exe -File "C:\Program Files\Zabbix\Raid
\raid_check.ps1" -mode adapter -item $2 -adapter $1
C:\Program Files\Zabbix\Raid\raid_check.ps1 : Falta um argumento para o parĂ¢metro 'mode_item'. Especifique um
parĂ¢metro do tipo 'System.String' e tente novamente.
+ CategoryInfo : InvalidArgument: (
[raid_check.ps1], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument,raid_check.ps1Comment
-
Hi,
question about the raid_check.pl file: it refers to /opt/MegaRAID/CmdTool2/CmdTool2 . That is the 32-bit version of that tool. Was this Perl file developed on a 32-bit host? If I run it on a 64-bit host, I get an libncurses.so.5 error message. I don't have this problem with CmdTool264 (the 64-bit version).
Cheers,
BC
Comment
-
Hi all,
I added the value mappings manually for my to be monitored host (the only way I know of in Zabbix 5, you can only import value mapping XML files for templates, but the template is not yet uploaded) and I get:
Cannot find value map "LSI RAID BBU & LD Status" used for item prototype "BBU state on adapter:{#ADAPTER_ID}" of discovery rule "RAID discovery bbu" on "Template LSI RAID".
What am i doing wrong?
Thanks,
BCComment
-
Hello,
Any chance there are updated StorCli64 versions available of the PS1 scripts? The MegaCli64 commands in the scripts don't work on some of my controllers. I keep running into "deprecated command, please use new syntax" messages or just can't find the equivalent between the two.
Appreciate any help.Comment
Comment