-
Problem report
-
Resolution: Fixed
-
Major
-
5.0.5
-
Debian 10 amd64
Zabbix 5.0.5
ProLiant DL325 Gen10
iLO Firmware Version 2.31 Oct 13 2020
-
Sprint 72 (Jan 2021), Sprint 73 (Feb 2021)
-
0.5
Steps to reproduce:
- Download latest version of SNMP iLO Template
https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/hp_ilo_snmp - Import Template
- Link Template to HPE iLO SN;P Host in Zabbix
- Wait for items to be discovered
Result:
Active Problem Triggers for High Temperature, because the default Threshold Macros of:
- {$TEMP_WARN} 50
- {$TEMP_CRIT} 60
Are also used as a fallback for:
- {$TEMP_CRIT:"CPU"}
- {$TEMP_CRIT:"Memory"}
- {$TEMP_CRIT:"PSU"}
- {$TEMP_CRIT:"Device"}
although these Items might have a much higher Threshold.
Expected:
Default values for all Macros used in the Template or at least a very clear notice in the README, that the possibility to use MACROS like {$TEMP_CRIT:"Device"} is already prepared.
Notes:
What is the intention of defining Context MACROS in the Template default Triggers, but not set their default values anywhere? So we have a fallback to the default MACRO, leading to several false positives (at least for us).
As they are not defined, they all Fallback to {$TEMP_CRIT} 60. I know it's very easy to fix, by adding the missing macros myself, but I talk about the out-of-box experience.
Please see a very nice overview of the iLO Thresholds, I marked the sensor numbers, so both screenshots are comparable. iLO has a very good overview of the manufacturer Thresholds for each component, and you can see that we have different 70°C+ sensors, which have a 100°C Limit for example.