Discussion thread for official Zabbix Template IPMI

[AlexL]

This thread is designed to provide grounds for discussion of the official Zabbix Template for IPMI.
The template and details of the template is available in GIT repository. https://git.zabbix.com/projects/ZBX/...r/chassis_ipmi
Zabbix is always looking for ways to improve our services and to make our users happier.
We pride ourselves on doing our best each and every day, but we know that there is always something more to learn.
We would like to hear back from you to know what have you liked and what would you improve in the template.

[reedacus25]

As posted in ZBXNEXT-5527, I have tested the template (085e4ea53e3) against about 15 different SuperMicro motherboards, and one Dell Motherboard.

EDIT: Forgot to mention, this is a daily Ubuntu 20.04 build running 5.0.3Alpha.

I've made a table of the ipmi_sensor keys that ended up having isues for each MB.
I've also used 2 keys, where value 1 is a generic issue like

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

While a value of 2 is a more pronounced issue, a table of "2" values for each MB is pasted below the big table.
I've also tried to use "variables" as much as possible, because whether its 1.3, 3.3, 5, 12V or any other value, it just makes the table unruly.

Hopefully all of this formatting comes out well/correctly.
I'm not sure how to pull the raw LLD output, but I can provide that as well if that would be helpful as well.

Sensor Name	H8-DGI-F	X8-DTT-F	X8-DTT-HEF+	X9-DBL-3F	X9-DRG-HF+	X9-SRL-F	X10-DRG-OT+	X10-DRT-PT	X10-DRU-i+	X10-DRW-iT	X11-DDW-NT	X11-DPG-OT	X11-DPH-T	H11-DST-B	H11-DSU-iN	PowerEdge R610
ipmi_sensor[-{#VOLTAGE}V]				1
ipmi_sensor[{#VOLTAGE} PLL PG]																2
ipmi_sensor[{#VOLTAGE}]				1	1	1	1		1	1	1	1	1	1	1
ipmi_sensor[{#VOLTAGE}V AUX PG]																2
ipmi_sensor[{#VOLTAGE}V BMC]							1	1	1	1
ipmi_sensor[{#VOLTAGE}V LOM PG]																2
ipmi_sensor[{#VOLTAGE}V PCH]							1	1	1	1	1	1	1
ipmi_sensor[{#VOLTAGE}V PG]																2
ipmi_sensor[{#VOLTAGE}VCC]						1	1	1	1	1	1	1	1	1	1
ipmi_sensor[+{#VOLTAGE}V]	1	1	1	1				1
ipmi_sensor[+{#VOLTAGE}VSB]	1	1	1	1	1		1	1	1	1	1	1	1
ipmi_sensor[AVCC]						1
ipmi_sensor[Cable SAS {#A/B}]																2
ipmi_sensor[Chassis Intru]				2	2	2	2		2	2	2	2	2		2
ipmi_sensor[CMOS Battery]																2
ipmi_sensor[CPU VTT]						1
ipmi_sensor[CPU{#CPUNUM} DIMM]	1	1	1
ipmi_sensor[CPU{#CPUNUM} Temp]	2	2	2
ipmi_sensor[CPU{#CPUNUM} Vcore]	1	1	1	1	1
ipmi_sensor[CPU{#CPUNUM} VDIMM]				1
ipmi_sensor[DKM Status]																2
ipmi_sensor[Drive{#DRIVENUM}]																2
ipmi_sensor[Fan Redundancy]																2
ipmi_sensor[HDD Status ]								2
ipmi_sensor[HEATSINK PRES]																2
ipmi_sensor[iDRAC6 Ent PRES]																2
ipmi_sensor[Intrusion]	2															2
ipmi_sensor[MEM PG]																2
ipmi_sensor[OS Watchdog]																2
ipmi_sensor[P{#CPUNUM}_SOCDUAL]														1	1
ipmi_sensor[P{#CPUNUM}_SOCRUN]														1	1
ipmi_sensor[P{#CPUNUM}_VDDCR]														1	1
ipmi_sensor[P{#CPUNUM}_VMEM{#DIMMSx4}]														1	1
ipmi_sensor[Power Optimized]																2
ipmi_sensor[Presence ]																2
ipmi_sensor[Presence]																2
ipmi_sensor[PS Redundancy]																2
ipmi_sensor[PS Status]	2	2	2
ipmi_sensor[PS{#PSNUM} Status]				2	2	2	2	2	2	2	2	2	2	2	2
ipmi_sensor[PVNN PCH]											1	1	1
ipmi_sensor[Riser Config]																2
ipmi_sensor[RISER{#RISERNUM} PRES]																2
ipmi_sensor[ROMB Battery]																2
ipmi_sensor[Status]																2
ipmi_sensor[STOR ADAPT PRES]																2
ipmi_sensor[USB CABLE PRES]																2
ipmi_sensor[VBAT]	1	1	1	1	1	1	1	1	1	1	2	2	2	2	2
ipmi_sensor[VCORE PG]																2
ipmi_sensor[Vcore]						1
ipmi_sensor[Vcpu{#CPUNUM}]							1	1	1	1	1	1	1
ipmi_sensor[VDD_33_DUAL]														1	1
ipmi_sensor[VDD_5_DUAL]														1	1
ipmi_sensor[VDIMM {#DIMM1}{#DIMM2}]					1		1	1	1	1
ipmi_sensor[VDIMM]						1
ipmi_sensor[VDimmP{#CPUNUM}{#DIMMSx3]											1	1	1
ipmi_sensor[VDimmP{#CPUNUM}{#MULTIDIM}]
ipmi_sensor[VSB]						1
ipmi_sensor[VTT ]	1			1	1
ipmi_sensor[VTT PG]																2

MB	ERROR MSG
H8-DGI-F	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
X8-DTT-F	Preprocessing failed for: [{"id":"+5VSB","name":"(7.1).+5VSB","sensor":{"t ype ":2,"text":"voltage"},"reading":{"type":1,"tex ... 1. Failed: cannot extract value from json by path "$.[?(@.id=='CPU1 Temp')].value.first()": no data matches the specified path
X8-DTT-HEF+	Preprocessing failed for: [{"id":"+5VSB","name":"(7.1).+5VSB","sensor":{"t ype ":2,"text":"voltage"},"reading":{"type":1,"tex ... 1. Failed: cannot extract value from json by path "$.[?(@.id=='CPU1 Temp')].value.first()": no data matches the specified path
X9-DBL-3F	Preprocessing failed for: [{"id":"PS1 Status","name":"(10.1).PS1 Status","sensor":{"type":8,"text":"power_supply"}, "reading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X9-DRG-HF	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.2).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "reading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X9-SRL-F	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.2).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "reading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X10-DRG-OT+	Preprocessing failed for: [{"id":"GPU8 Temp","name":"(11.8).GPU8 Temp","sensor":{"type":1,"text":"temperature"},"re ading":{... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X10-DRT-PT	Preprocessing failed for: [{"id":"HDD Status ","name":"(4.1).HDD Status ","sensor":{"type":13,"text":"drive_slot"},... 1. Failed: cannot extract value from json by path "$.[?(@.id=='PS1 Status')].value.first()": no data matches the specified path
X10-DRU-i+	Preprocessing failed for: [{"id":"NVMe_SSD Temp ","name":"(1.4).NVMe_SSD Temp ","sensor":{"type":1,"text":"temperature"},... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X10-DRW-iT	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.2).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "reading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X11-DDW-NT	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.87).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "readin... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X11-DPG-OT	Preprocessing failed for: [{"id":"GPU10 Temp","name":"(11.10).GPU10 Temp","sensor":{"type":1,"text":"temperature"},"re ading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
X11-DPH-T	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.87).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "readin... 1. Failed: cannot extract value from json by path "$.[?(@.id=='Chassis Intru')].value.first()": no data matches the specified path
H11-DST-B	Preprocessing failed for: [{"id":"AOC_NIC_Temp ","name":"(r0.32.11.0).AOC_NIC_Temp ","sensor":{"type":1,"text":"tempera... 1. Failed: cannot extract value from json by path "$.[?(@.id=='VBAT')].value.first()": no data matches the specified path
H11-DSU-iN	Preprocessing failed for: [{"id":"PS2 Status","name":"(10.91).PS2 Status","sensor":{"type":8,"text":"power_supply"}, "readin... 1. Failed: cannot extract value from json by path "$.[?(@.id=='VBAT')].value.first()": no data matches the specified path
R610	Preprocessing failed for: [{"id":"ROMB Battery","name":"(26.3).ROMB Battery","sensor":{"type":41,"text":"battery"},"re ading... 1. Failed: cannot extract value from json by path "$.[?(@.id=='0.9V PG')].value.first()": no data matches the specified path

[reedacus25]

Upon looking further using ipmitool, at least for the "2" scenarios for the Supermicro boards, I believe this issue may be related to the unit being labeled "discrete", where others are Volts/RPM/etc.

3.3VCC           | 3.225      | Volts      | ok    | 2.613     | 2.681     | 2.885     | 3.718     | 3.922     | 3.990
VBAT             | 0x4        | discrete   | 0x04ff| na        | na        | na        | na        | na        | na
P1_VDDCR         | 1.120      | Volts      | ok    | 0.400     | 0.499     | 0.607     | 1.237     | 1.345     | 1.399
P1_VMEMABCD      | 1.231      | Volts      | ok    | 0.979     | 1.003     | 1.081     | 1.387     | 1.465     | 1.489
P2_VDDCR         | 1.143      | Volts      | ok    | 0.396     | 0.495     | 0.612     | 1.242     | 1.341     | 1.395
P1_VMEMEFGH      | 1.228      | Volts      | ok    | 0.976     | 0.997     | 1.074     | 1.389     | 1.466     | 1.487
VDD_5_DUAL       | 5.129      | Volts      | ok    | 4.019     | 4.139     | 4.439     | 5.729     | 6.029     | 6.149
VDD_33_DUAL      | 3.327      | Volts      | ok    | 2.613     | 2.681     | 2.885     | 3.718     | 3.922     | 3.990
P2_VMEMABCD      | 1.235      | Volts      | ok    | 0.976     | 0.997     | 1.074     | 1.389     | 1.466     | 1.487
P2_VMEMEFGH      | 1.242      | Volts      | ok    | 0.976     | 0.997     | 1.074     | 1.389     | 1.466     | 1.487
P1_SOCRUN        | 0.993      | Volts      | ok    | 0.300     | 0.496     | 0.629     | 1.070     | 1.147     | 1.343
P2_SOCRUN        | 1.000      | Volts      | ok    | 0.300     | 0.496     | 0.629     | 1.070     | 1.147     | 1.343
P1_SOCDUAL       | 0.900      | Volts      | ok    | 0.711     | 0.725     | 0.781     | 1.012     | 1.068     | 1.082
P2_SOCDUAL       | 0.900      | Volts      | ok    | 0.711     | 0.725     | 0.781     | 1.012     | 1.068     | 1.082
Chassis Intru    | 0x0        | discrete   | 0x0000| na        | na        | na        | na        | na        | na
PS1 Status       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na
PS2 Status       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na

And this also appears to be the same with the R610 results, where most failed with a "2" type.

Riser Config     | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
OS Watchdog      | 0x0        | discrete   | 0x0080| na        | na        | na        | na        | na        | na
SEL              | na         | discrete   | na    | na        | na        | na        | na        | na        | na
Intrusion        | 0x0        | discrete   | 0x0080| na        | na        | na        | na        | na        | na
PS Redundancy    | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
Fan Redundancy   | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
CPU Temp Interf  | na         | discrete   | na    | na        | na        | na        | na        | na        | na
Drive            | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
Cable SAS A      | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
Cable SAS B      | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na
DKM Status       | 0x0        | discrete   | 0x0080| na        | na        | na        | na        | na        | na

Hoping that this will be helpful and point someone in the correct direction.

[max.ch.88]

As posted in ZBXNEXT-5527, I have tested the template (085e4ea53e3) against about 15 different SuperMicro motherboards, and one Dell Motherboard.

EDIT: Forgot to mention, this is a daily Ubuntu 20.04 build running 5.0.3Alpha.

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

It's very strange, because of template_server_chassis_ipmi.xml has not items with Numeric (unsigned) type. Please download and import the template correctly.

[reedacus25]

Well, sadly this appears to have fixed things.
Which is odd, due to the original XML I downloaded having matching md5sums to the one I re-downloaded and uploaded.
So I guess something must have gotten mangled during the original XML import?
Either way, it looks like things are working now with no unsupported items across all hosts.

[eithor]

Hi,

I notice that the template creates triggers using non-existing values/discovery macros, e.g.:

IPMI: Ambient value is above non-recoverable high (greater than {#SENSOR_HI_DISAST} for 5m)

with expression:

ipmi.value[Ambient].min(5m)}>{#SENSOR_HI_DISAST}

This causes the trigger to be deactivated (unsupported).

I assume that the Discovery process should have populated these thresholds?

Please advice on how I can troubleshoot this missing/faulty discovery.

Environment:
Zabbix 5.0 on Debian, query to Dell and Fujitsu BMC over ipmi.

Best,
Eirik

[max.ch.88]

Hi,

I notice that the template creates triggers using non-existing values/discovery macros, e.g.:

IPMI: Ambient value is above non-recoverable high (greater than {#SENSOR_HI_DISAST} for 5m)

with expression:

ipmi.value[Ambient].min(5m)}>{#SENSOR_HI_DISAST}

This causes the trigger to be deactivated (unsupported).

I assume that the Discovery process should have populated these thresholds?

Please advice on how I can troubleshoot this missing/faulty discovery.

Environment:
Zabbix 5.0 on Debian, query to Dell and Fujitsu BMC over ipmi.

Best,
Eirik

Hello Eirik. The cause is the empty values of thresholds in your IPMI Baseboard Management Controller. The master item gets the values of sensors with their thresholds from BMC via one request in JSON format. The right way could be to set all thresholds yourself in BMC.

[aleksandar]

I got error with older HP server when using this template. Most probably it is a bug in the Zabbix server IPMI worker, not in the template itself.
Looks like the parsing is not working properly if "strange" string is in the trigger values.

I have saved the getipmi message and see that JSON is not formated properly. Problematic line is like this
{"id":"FAN6_OUTLET","name":"(29.12).FAN6_OUTLET "," sensor":{"type":4,"text":"fan"},"reading":{"type": 1,"text":"threshold"},"state":{"state":0,"text": "" },"value":4524.682141,"units":"RPM","threshold": {" lower":{"crit":inf},"upper":{"crit":999.200639}}},

In this line {"crit":inf} should be {"crit":"inf"}

ipmitool is returning this (only sample lines)
FAN6_INLET | 5450.185 | RPM | ok | na | inf | na | na | 999.201 | na
FAN6_OUTLET | 4524.682 | RPM | ok | na | inf | na | na | 999.201 | na

Error seen in the web interface is this: Invalid discovery rule value: cannot parse as a valid JSON object: invalid JSON object value starting character at: 'inf},"

Zabbix server version is 5.0.7 LTS on Ubuntu 18.04 LTS

[David Whyte]

Hi, having installed this template last night it seems to be generally working OK, though I have a couple of questions:

1. Does this template rely on the IPMI username/password under the Host/IPMI page, or the Template/Macros page? Or both?
2. Is it possible to set the update interval somewhere. Some of my sensors (e.g inlet temp) are being checked regularly. Others (e.g. fan speed) seem to only be checked every hour. Some seem to change between regular and irregular checks. I can't see how this interval is being specified.

Thanks,
David

[dauntless101]

Any tips for getting this to work with Supermicro IPMI? Running Zabbix 6.4.4, testing it out on X9DRI-F and X9SCM-F motherboards but not making a connection. I used port 623 as others have mentioned and verified in the Supermicro IPMI web interface that port is correct and open, servers are on the same network as Zabbix with no firewall restrictions. Added the username and password macro to the template. Thanks!

[davromaniak]

Hey.

I'm trying to create a trigger only for the "CMOS battery".

So I went the trigger prototypes way and added a new one for CMOS battery check.

It works at all, but it's been applied on all sensors.

Here's a screenshot of the trigger.



I tried to replace "{#SENSOR_ID}" by "CMOS Battery" but as expected, it can't be setup like this.

I also tried to create a static trigger with the expression

last(/Template Module - Chassis by IPMI/ipmi.state_text['CMOS Battery'])<>"battery presence detected"

But, as expected, I end up with the following error

Incorrect item key "ipmi.state_text['CMOS Battery']" provided for trigger expression on "Template Module - Chassis by IPMI".

Is there a way to match "{#SENSOR_ID}" in a trigger prototype (or any other variable) to avoid this trigger being applied to all discrete sensors checks ?

I'm starting to run out of ideas, so if anybody has any advice/idea on this subject, it would be appreciated.

Thanks a lot.

[Aleksey_work]

Oracle Linux 9.3, Zabbix 6.4.8, PostgreSQL 15.
In BMC, I created a zabbix user with the password password, the role is Administrator. In Zabbix I added a network host, IPMI interface, address, port 623. In the IPMI tab: Default, Administrator, zabbix, password. In macros: {$IPMI.PASSWORD} - password, {$IPMI.USER} - zabbix. After these settings, I see a green IPMI field in the interface, but in the discovery rules I see: "Invalid discovery rule value: cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'cannot connect to IPMI host: [16777411] Unknown error 16777411'" LogLevel=4 and there:

  1553:20240110:165454.632 IPMI agent item "ipmi.get" on host "server_IPMI" failed: first network error, wait for 15 seconds
  1553:20240110:165509.654 IPMI agent item "ipmi.get" on host "server_IPMI" failed: another network error, wait for 15 seconds
  1553:20240110:165524.675 IPMI agent item "ipmi.get" on host "server_IPMI" failed: another network error, wait for 15 seconds
  1553:20240110:165539.698 temporarily disabling IPMI agent checks on host "server_IPMI": interface unavailable
  1553:20240111:163034.407 enabling IPMI agent checks on host "server_IPMI": interface became available
  1552:20240111:163034.408 discovery rule "server_IPMI:ipmi.discrete.discovery" became not supported: Invalid discovery rule value: cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'cannot connect to IPMI host: [33554436] Unknown error 33554436'
  1552:20240111:163034.414 discovery rule "server_IPMI:ipmi.sensors.discovery" became not supported: Invalid discovery rule value: cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'cannot connect to IPMI host: [33554436] Unknown error 33554436'​

Zabbix modules:

ldd /usr/sbin/zabbix_server
/usr/sbin/zabbix_server: /usr/pgsql-15/lib/libpq.so.5: no version information available (required by /usr/sbin/zabbix_server)
        linux-vdso.so.1 (0x00007ffcadfe5000)
        libpq.so.5 => /usr/pgsql-15/lib/libpq.so.5 (0x00007f5de262c000)
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f5de24a3000)
        libodbc.so.2 => /lib64/libodbc.so.2 (0x00007f5de2431000)
        libnetsnmp.so.40 => /lib64/libnetsnmp.so.40 (0x00007f5de2347000)
        libssh.so.4 => /lib64/libssh.so.4 (0x00007f5de22d2000)
        libOpenIPMI.so.0 => /lib64/libOpenIPMI.so.0 (0x00007f5de21b7000)
        libOpenIPMIposix.so.0 => /lib64/libOpenIPMIposix.so.0 (0x00007f5de21ab000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f5de2191000)
        libevent-2.1.so.7 => /lib64/libevent-2.1.so.7 (0x00007f5de2138000)
        libevent_pthreads-2.1.so.7 => /lib64/libevent_pthreads-2.1.so.7 (0x00007f5de2133000)
        libssl.so.3 => /lib64/libssl.so.3 (0x00007f5de208d000)
        libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f5de1c5b000)
        libldap.so.2 => /lib64/libldap.so.2 (0x00007f5de1bf2000)
        liblber.so.2 => /lib64/liblber.so.2 (0x00007f5de1be0000)
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f5de1b3f000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f5de1a64000)
        libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f5de19c8000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f5de17bf000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f5de1766000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f5de173a000)
        libltdl.so.7 => /lib64/libltdl.so.7 (0x00007f5de172e000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f5de2be1000)
        libOpenIPMIutils.so.0 => /lib64/libOpenIPMIutils.so.0 (0x00007f5de1723000)
        libgdbm.so.6 => /lib64/libgdbm.so.6 (0x00007f5de1712000)
        libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f5de16f0000)
        libnghttp2.so.14 => /lib64/libnghttp2.so.14 (0x00007f5de16c6000)
        libidn2.so.0 => /lib64/libidn2.so.0 (0x00007f5de16a5000)
        libpsl.so.5 => /lib64/libpsl.so.5 (0x00007f5de1691000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f5de15b6000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f5de159d000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f5de1594000)
        libbrotlidec.so.1 => /lib64/libbrotlidec.so.1 (0x00007f5de1586000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f5de1575000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f5de156e000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f5de155a000)
        libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f5de151e000)
        libunistring.so.2 => /lib64/libunistring.so.2 (0x00007f5de1399000)
        libbrotlicommon.so.1 => /lib64/libbrotlicommon.so.1 (0x00007f5de1376000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f5de1349000)​

Initially (before installing the Zabbix server), the OpenIPMI and ipmitool packages were not installed, I installed them while dealing with the problem described above. launched from the zabbix server:

ipmitool -I lanplus -U zabbix -P password -H ip_server sensor

returns the metric, it would seem that everything should work, but it doesn’t work in Zabbix, I can’t understand what the problem is. What else can you look at in the logs/settings to make it work?

[rene.hankel]

i have almost the same problem like Aleksey_work. ipmitools works, zabbix tells me again and again

956:20240819:113406.595 IPMI agent item "ipmi.get" on host "CHITERRAMGNT01" failed: first network error, wait for 15 seconds
956:20240819:113421.616 IPMI agent item "ipmi.get" on host "CHITERRAMGNT01" failed: another network error, wait for 15 seconds
956:20240819:113436.636 IPMI agent item "ipmi.get" on host "CHITERRAMGNT01" failed: another network error, wait for 15 seconds
956:20240819:113451.656 temporarily disabling IPMI agent checks on host "CHITERRAMGNT01": interface unavailable

und finally 'cannot connect to IPMI host: [22] Invalid argument'

but why? what he wants?

[soporte-quasarti]

Hi, There is any activity in this forum? I can't see any replies from creators.
In my case, I'm using the template, but ALL voltage monitors plus "VCORE PG", "VTT PG" and "MEM PG" shows this message: "state deasserted", and I don't understand it.
Additionally, the ambient temperature monitor get data in 1 hour interval, and I don't know how to change it.
"System level watts" monitor has an irregular interval.

The model of two servers is Dell R610.
Zabbix server 7.0.4
Template version: 7.0-1

So, in conclusion, this template needs more documentation, and/or be created by vendor (as a suggestion).

[marcos.della]

See if anyone is monitoring this particular thread....

Working with Supermicro servers, I've discovered that if a temp probe reports 115C, that means that the probe has failed. Of course the template just records that as a critical error. Possible to add a macro that identifies a "failure" value? I've seen zero indicate unable to read the probe and on things like SuperMicro, 115.0 to indicate a probe failure (not entirely sure what the difference is). But we've been having temp issues in our DCs and have had a number of the sensors give up and fail (leading to alerts that we cannot clear as they don't have the option to delete/clear them from the default template).

I've inherited the template and create a whole new set of triggers (and "turned off" the original) but that seems not like a very long term solution...