We have several brand new HPE Server GEN10 with an iLO5 card, ping me if you need help!

mchudinov Hello Marco! Are you ready to test the new "Template Server by IPMI"? You will need to install Zabbix 5.0 from the source code.

Hello, we have several brand Supermicro SYS-5019S-ML and SYS-5019S-M2. Temperature and fan sensors are not reading. Discovery rules status - Not supported (
SNMP error: (badValue) The value given has the wrong type or length)
 

Fan Sensors:

Temperature Sensors:

@mchudinov

Couldn't i use https://repo.zabbix.com/zabbix/4.5/debian/pool/main/z/zabbix/zabbix-server-mysql_5.0.0~alpha1-1%2Bbuster_amd64.deb for testing?

mchudinov No, you should install it from the latest source code.
git clone https://git.zabbix.com/scm/zbx/zabbix.git --branch master --depth 1 --single-branch zabbix-5.0
and manual https://www.zabbix.com/documentation/5.0/manual/installation/install

I'm willing to help and I will help, but to be honest I don't have the time and the experience to compile Zabbix server for myself.
I wait for the next DEB (alpha2?) that will include that feature by default, then I will spin up a test Debian 10 VM and test this feature.

I've got a wide range of Supermicro servers I can test against, X8-H11.

Stood up alpha3 today from repo for Ubuntu, would love to be able to help.

Template available in:

• 5.0.0alpha4 (master) 085e4ea53e3

I've just run my different servers (16 unique SuperMicro motherboards, and 1 Dell) through with the template linked above, and I have come across some issues.

What is the best way to provide feedback to improve the Template?

Most of the unsupported items look to be issues with the value type:

Value "1.824000" of type "string" is not suitable for value type "Numeric (unsigned)"

However, some look to be more problematic, such as:

Preprocessing failed for: [{"id":"PS Status","name":"(10.1).PS Status","sensor":{"type":8,"text":"power_supply"},"reading":...
1. Failed: cannot extract value from json by path "$.[?(@.id=='Intrusion')].value.first()": no data matches the specified path

Which loooks like it is looking at something in the Power Supply Status for Intrusion Switch data.

Just hoping to provide some wide data points if possible.

Hello Reed Dier!
Please describe your problem on Zabbix forum in this topic
https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/398023-discussion-thread-for-official-zabbix-template-ipmi
Thank you.

Documentation updated:

• What's new in 5.0
• Template changes

In the last few days I did some tests with HP iLO SNMP: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/hp_ilo_snmp?at=refs%2Fheads%2Frelease%2F5.0
Our machine for example: ProLiant DL380 Gen10 iLO 5 2.31 Oct 13 2020

I found a design decision I don't understand.
First of all, we get several false positives:

Second, and this has a direct correlation: 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). I talk about:

• {$TEMP_CRIT:"CPU"}
• {$TEMP_CRIT:"Memory"}
• {$TEMP_CRIT:"PSU"}
• {$TEMP_CRIT:"Device"}

and so on. As they are not defined, they all Fallback to {$TEMP_CRIT} 60. I know it's very easy to fix, but I talk about the out-of-box experience.
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.

Moved to ZBX-18638