[ZBX-18638] Template Server HP iLO SNMP doesn't provide default values for all used macros Created: 2020 Nov 11  Updated: 2024 Apr 10  Resolved: 2021 Feb 14

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 5.0.5
Fix Version/s: 5.0.9rc1, 5.2.5rc1, 5.4.0alpha2, 5.4 (plan)

Type: Problem report Priority: Major
Reporter: Marco Hofmann Assignee: Maxim Chudinov (Inactive)
Resolution: Fixed Votes: 0
Labels: HPe, SNMP, iLO
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 10 amd64
Zabbix 5.0.5
ProLiant DL325 Gen10

iLO Firmware Version 2.31 Oct 13 2020

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png    
Team: Team INT
Sprint: Sprint 72 (Jan 2021), Sprint 73 (Feb 2021)
Story Points: 0.5

 Description   

Steps to reproduce:

  1. Download latest version of SNMP iLO Template
    https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/hp_ilo_snmp
  2. Import Template
  3. Link Template to HPE iLO SN;P Host in Zabbix
  4. 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.



 Comments   
Comment by Edgar Akhmetshin [ 2020 Nov 13 ]

Hello Marco,

Could you please provide full snmpwalk output and fresh MIB file from vendor for this device?

If thresholds can be read from device - template should use them, if not - all HPe device's has different level of thresholds, so it's not possible to set it once and for all, that's why macros are used, so you can easily adjust them exactly for your environment.

Regards,
Edgar

Comment by Marco Hofmann [ 2020 Nov 16 ]

As discussed outside of this ZBX-issue, I provided Zabbix Team a complete SNMPWALK from an iLO4 and an iLO5, each on the latest Firmware version.

The latest MIB files can be downloaded here, without any account or registration: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04272529
Latest version for Linux, Downlaod the tar.gz file, look for the MIB files. I also added them to the files I sent to Zabbix Team.

For the Thresholds, for our HPE servers I find them under: cpqHeTemperatureThreshold // .1.3.6.1.4.1.232.6.2.6.8.1.5
Do you need additional screenshots?

Regarding the macros: My problem is, that the current templates use the following macros in their Trigger prototypes

  • {$TEMP_CRIT:"CPU"}
  • {$TEMP_CRIT:"Memory"}
  • {$TEMP_CRIT:"PSU"}
  • {$TEMP_CRIT:"Device"}
    but does not define the Macros. This looks like an oversight to me. Hence I created this ticket.

And further on, may I suggest to include more of the overall health triggers? For example:
cpqHeThermalCondition // .1.3.6.1.4.1.232.6.2.6.1.0
Syntax INTEGER {other(1), ok(2), degraded(3), failed(4)}

Comment by Maxim Chudinov (Inactive) [ 2021 Feb 08 ]

Available in:

Generated at Tue Jun 10 06:40:45 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.