Can't find Item keys for ipmi when creating a new element

[buergi]

I have installed Zabbix Server 1.6 and an 1.6 Agent. How can i create new elements for monitoring IPMI values when there doesn't exists keys for IPMI?

Please help me!

[carbs]

I'm wondering this too, I tried entering the values from ipmitool but with no luck. For example ipmi tool returned (below is just part of it) this...

hdd0.state       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na        
hdd1.state       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na        
hdd2.state       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na        
hdd3.state       | 0x1        | discrete   | 0x0100| na        | na        | na        | na        | na        | na

So I tried entering hdd0.state in the "key" and/or "IPMI Sensor" fields, tried putting the IP of the host in the "IPMI Sensor" and a few other combinations but for the life of me I can not work out the way it is supposed to work. I keep seeing errors saying "Parameter [hdd0.fail] is not supported by agent on host". Is there a trick to setting up ipmi items on a host.

The manual discusses how to setup remote commands via IPMI but doesn't really discuss IMPI item monitoring.

Could anyone shed some light on which values belong in which fields and how it go about getting those values if they are not obvious? Any help would be greatly appreciated.

Thanks,
Mark

[oddie]

I have managed to get ipmi agent working against a Dell Poweredge. When running ipmitool like this:

ipmitool -H ip.ad.dre.ss -U zabbix -P XXXXX -L USER -A MD5 -I lan sensor

I get rows like this:

FAN MOD 1A RPM | 6600.000 | RPM | ok | na | 3525.000 | na | na | na | na

When configuring item on host with enabled ipmi agent:

Type: Ipmi Agent (ofcourse)
IPMI sensor: FAN MOD 1A RPM (no quotes needed)
Key: ipmi.fan.1a.rpm (i think this could be anything you want?)
Type of information: Numeric float (since 6600.000 is not an integer)
Units: rpm

What i don't know is how you specify IPMI sensor that has the same name as another. When you run "sensor" command with ipmitool you will maybe see a bunch of sensors named just "Temp" or just "Status" that are actually different sensors? Have no clue about selecting a specific one that doesn't have a unique name.

[carbs]

Maybe there is something going on with my server (Sun X6220 Blade) as I tried the same thing with no luck. Could be that it used IPMI v2.0 or something like that.

I might have to resort to using an external command for now as I really need to monitor the internal drives on this server.

[AdamLundrigan]

Not sure if you have figured out your problem yet, or if my problem is related to the one you had, but here goes:

I have setup Zabbix v1.6.1 collecting information from a Sun Fire X4100M2 server via IPMI. I can read non-discrete values fine, however specifying the IPMI key for a discrete sensor (ie: ps0.pwrok), Zabbix Server would complain:

Sensor or control ps0.pwrok@[172.16.21.223]:623 does not exists

Which is obviously not true, since it's published in the ILOM suppliment for the X4100M2. So I added the following to the zabbix server (poller, specifically) code to print all the available sensors:

*** checks_ipmi.c.orig	2008-11-27 10:30:02.000000000 -0330
--- checks_ipmi.c	2008-11-27 10:46:23.000000000 -0330
***************
*** 901,906 ****
--- 901,912 ----
  		zabbix_log(LOG_LEVEL_DEBUG, "Sensor or control %s@[%s]:%d does not exists",
  				item->ipmi_sensor, h->ip, h->port);
  		SET_MSG_RESULT(value, strdup("Sensor or control does not exists"));
+ 
+ 		int i;
+ 		zabbix_log(LOG_LEVEL_DEBUG, "Available Sensors:");
+         	for (i = 0; i < h->sensor_count; i++)
+ 			zabbix_log(LOG_LEVEL_DEBUG, "- %s", h->sensors[i].s_name);
+ 
  		return NOTSUPPORTED;
  	}

When I checked the log after zabbix server tried to read the ps0.pwrok, I saw this:

Available Sensors:
- ft1.fm2.prsnt1
- ft1.fm1.prsnt1
- ft1.fm0.prsnt1
- ft0.fm2.prsnt1
- ft0.fm1.prsnt1
- ft0.fm0.prsnt1
- io.f0.fail1
- io.f0.speed
- io.f0.prsnt1
- ft1.fm2.f0.speed
- ft1.fm1.f0.speed
- ft1.fm0.f0.speed
- ft0.fm1.f0.speed
- ft0.fm2.f0.speed
- ft0.fm0.f0.speed
- ft1.fm2.fail1
- ft1.fm1.fail1
- ft1.fm0.fail1
- ft0.fm2.fail1
- ft0.fm1.fail1
- ft0.fm0.fail1
- p1.d3.fail1
- p1.d2.fail1
- p1.d1.fail1
- p1.d0.fail1
- p1.fail1
- p1.v_vtt
- p1.v_vddio
- p1.v_vdd
- p1.t_core
- p0.d3.fail1
- p0.d2.fail1
- p0.d1.fail1
- p0.d0.fail1
- p0.fail1
- p0.v_vtt
- p0.v_vddio
- p0.v_vdd
- p0.t_core
- io.t_amb
- pdb.t_amb
- fp.t_amb
- mb.v_+1v2core
- mb.v_+1v5core
- mb.v_+2v5core
- mb.v_-12v
- mb.v_+12v
- mb.v_+5v
- mb.v_+3v3
- mb.v_+3v3stby
- mb.v_bat
- mb.t_amb
- io.hdd3.fail1
- io.hdd2.fail1
- io.hdd1.fail1
- io.hdd0.fail1
- io.id1.prsnt1
- io.id0.prsnt1
- ps1.pwrok1
- ps1.vinok1
- ps1.prsnt1
[B]- ps0.pwrok[/B]1
- ps0.vinok1
- ps0.prsnt1
- fp.ledbd.prsnt1
- fp.alert1
- fp.locate.btn1
- fp.locate1
- fp.power1
- fp.usbfail1
- fp.prsnt1
- bp.alert1
- bp.locate.btn1
- bp.locate1
- bp.power1
- sys.fanfail1
- sys.tempfail1
- sys.psfail1
- sys.id1

Peculiar. All the discrete sensors are suffixed with '1', whereas non-discrete sensors retain their original name. Is this done within Zabbix, or by OpenIPMI?

Not that it matters too much at this point anyway, as while making the above hack to checks_ipmi.c in the poller, I noticed that all the code for handling discrete sensors is commented out, but this was the dead giveaway (checks_ipmi.c:425):

h->err = zbx_dsprintf(h->err, "Discrete sensor is not supported.");
h->ret = NOTSUPPORTED;
return;

General question to Zabbix insiders: When will discrete sensors be available in Zabbix? I am very keen on getting that feature fleshed out....if all it takes is for me to volunteer my time to work on it, I am more than willing. You know how to contact me

[carbs]

I haven't figured it out yet, but thanks for the diff. I patched my checks_ipmi.c and have a similar output to what you have. The sensors I really need to monitor are all suffixed with a '1', primarily the hdd?.fail items as this is a blade the power and fan sensor belong to the chassis so I don't need to monitor them here.

Available Sensors:
- bl9.prsnt1
- bl8.prsnt1
- bl7.prsnt1
- bl6.prsnt1
- bl5.prsnt1
- bl4.prsnt1
- bl3.prsnt1
- bl2.prsnt1
- bl1.prsnt1
- bl0.prsnt1
- p1.v_vddio
- p0.v_vddio
- p1.v_vtt
- p0.v_vtt
- p1.v_vdd
- p0.v_vdd
- p1.t_core
- p0.t_core
- p1.prsnt1
- p0.prsnt1
- fm5.fail1
- fm4.fail1
- fm3.fail1
- fm2.fail1
- fm1.fail1
- fm0.fail1
- fm5.f1.speed
- fm5.f0.speed
- fm4.f1.speed
- fm4.f0.speed
- fm3.f1.speed
- fm3.f0.speed
- fm2.f1.speed
- fm2.f0.speed
- fm1.f1.speed
- fm1.f0.speed
- fm0.f1.speed
- fm0.f0.speed
- hdd3.fail1
- hdd2.fail1
- hdd1.fail1
- hdd0.fail1
- ps1.pwrok11
- ps1.pwrok01
- ps0.pwrok11
- ps0.pwrok01
- ps1.vinok11
- ps1.vinok01
- ps0.vinok11
- ps0.vinok01
- ps1.prsnt1
- ps0.prsnt1
- mb.v_+1v2
- mb.v_+1v5
- mb.v_+2v5
- mb.v_+12v
- mb.v_+5v
- mb.v_+3v3
- mb.v_+3v3aux
- mb.v_bat
- mb.t_amb2
- mb.t_amb1
- mb.t_amb0
- nem1.prsnt1
- nem0.prsnt1
- cmm.prsnt1
- sys.locate.btn1

It would be awesome if discrete sensors were working, it will help me sleep a little better at night as we will know when something fails

[richlv]

General question to Zabbix insiders: When will discrete sensors be available in Zabbix? I am very keen on getting that feature fleshed out....if all it takes is for me to volunteer my time to work on it, I am more than willing. You know how to contact me

it's been some time since this offer
has something happened in this front since ?

[AdamLundrigan]

I have hacked together some modifications to src/zabbix_server/poller/checks_ipmi.c which allows Zabbix server to collect discrete sensor readings.

I have noticed one odd behavior since making this change to my Zabbix server. After upgrading one of my X4100s to the latest firmware, and then adding it to Zabbix server for IPMI monitoring, the server crashed. After the server was restarted, it collected IPMI data from the machine fine. I'm still not sure if there is a connection between my modifications and this problem. I'll update this post, and the patch if necessary, if there is.

DISCLAIMER: I have not fully tested these patches. If you choose to use this patch, it is at your own risk. In other words, to quote the GPL:

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

Enjoy!

[gustav]

Does the patch work in 1.6.6

Hi.

I also noticed that Zabbix doesn't handle discrete sensors and I'm wondering wether this patch suites 1.6.6 as well?

Another question, maybe out of scope a little bit, but related to Sun Fire X4200. Using ipmtool I see sensors like io.hdd0.fail, but nos as within your template p0.fail for instance or the DIMM related ones as well.

I have the latest version of ILOM, flashed it yesterday.

[marmeks]

Is there update to this?
Although it is great that I can monitor temperature, RPM, Watts etc, the ability to monitor discrete sensors (RAID status OK, PSU status OK etc) is a MUST.

[andris]

Yesterday I got this task and started looking into it.

[Humberto]

Any solution to the issue?

Colleagues, start using zabbix 3.0 recently, and now I came across the same problem posed in the post, reading ipmi discrete values. As the latest actions by what I saw is 2002, and since we already have new versions of zabbix and everything, wanted to know if there is any solution to this problem, we can believe that actually zabbix is not able to collect this type of data ? : Eek:

[richlv]

sure, Zabbix 2.2.0 added support for discrete IPMI sensors : https://www.zabbix.com/documentation...screte_sensors

[Humberto]

Problem

Thanks for the reply, but then I have a problem because I use the version of Zabbix 3.0.4 and when I do consultations IPMI if the values are analog such as temperature and pressure, are normally collected; now are discrete returns the error that many already reporting ("sensor or control DASD Backplane 1 @ [172.16.4.24] 623 does not exist"), that the principle would be the inexistence of the sensor, but clearly the sensor exists. What can I do? Can you help me?

[richlv]

is your Zabbix server compiled against the latest OpenIPMI version ? (older versions are known to add .0 to the sensor names) ?
can you query that exact sensor name with ipmitool - and if you can try with OpenIPMI, too ?