IPMI "HDD status" not working for Supermicro servers

[lionel seydoux]

HI,
I'm trying to monitor Supermicro servers with Zabbix IPMI agent. It works properly for most of the sensors, but not at all for the "HDD status"

Zabbix discovers the sensor as follow:
29684:20180227:141359.066 Added sensor: host:'xxx.xxx.xxx.xxx:623' id_type:0 id_sz:16 id:'HDD Status ' reading_type:0x6f ('sensor specific') type:0xd ('drive_slot') full_name:'2(4.1).HDD Status '

reading type: 0x6f
type: 0xd

according to the IPMI doc (https://www.intel.com/content/dam/ww...ce-spec-v2.pdf), in the tables 42-1 and 42-3:
- 0x6f means discrete sensor
- 0xd means drive slot(Bay). that one should define 9 bits, where the first one is the drive presence



ipmitool is returning me a hex value of 0x01ff

[root@nmst ~]# ipmitool -H xxx.xxx.xxx.xxx -U aaaa sensor
...
HDD Status | 0x1 | discrete | 0x01ff| na | na | na | na | na | na


Zabbix, however return mean a value of 768. If I have a look to the zabbix logs, I see the following
29684:20180227:155157.089 State [HDD Status | disk | drive_slot | sensor specific | state 8 value is 1]
29684:20180227:155157.089 State [HDD Status | disk | drive_slot | sensor specific | state 9 value is 1]

it seems it only sees the bits 8 and 9 defined, meaning 1100000000 -> 768 in decimal


Is Zabbix really understanding properly Supermicro IPMI ? is the IPMI implementation of supermicro wrong ?

Could anyone monitor the status of Supermicro HDD with the zabbix IPMI agent ?

cheers

[cmarotta]

This is likely a supermicro problem. As i've learned, only a limited number of RAID cards and will pass HDD health info to the BMC/IPMI.


Note 3: The Storage Monitoring feature is only available for Supermicro's Broadcom 3108 or Supermicro's Marvell® SE9230 controller, not the onboard Intel controllers. Please also note that the Marvell® SE9230 controller is only supported for X11 versions of motherboards.

[cmarotta]

You will have to rely on either SNMP MIB's or using the Zabbix OS Agent to locally poll for RAID and Drive Health

[Spisarau]

HI,

Is Zabbix really understanding properly Supermicro IPMI ? is the IPMI implementation of supermicro wrong ?

Could anyone monitor the status of Supermicro HDD with the zabbix IPMI agent ?

cheers

when Zabbix gets IPMI info it has it in this way

[{"id":"HDD Status ","name":"(4.36).HDD Status ","sensor":{"type":13,"t

so to make it work you just need to set IPMI Sensor with additional spaces "HDD Status "
editor is removing extra spaces so it should be more than one

[roma]

HI,
I'm trying to monitor Supermicro servers with Zabbix IPMI agent. It works properly for most of the sensors, but not at all for the "HDD status"

Zabbix discovers the sensor as follow:
29684:20180227:141359.066 Added sensor: host:'xxx.xxx.xxx.xxx:623' id_type:0 id_sz:16 id:'HDD Status ' reading_type:0x6f ('sensor specific') type:0xd ('drive_slot') full_name:'2(4.1).HDD Status chatiw'

reading type: 0x6f
type: 0xd

according to the IPMI doc (https://www.intel.com/content/dam/ww...ce-spec-v2.pdf), in the tables 42-1 and 42-3:
- 0x6f means discrete sensor ometv
- 0xd means drive slot(Bay). that one should define 9 bits, where the first one is the drive presence



ipmitool is returning me a hex value of 0x01ff

[root@nmst ~]# ipmitool -H xxx.xxx.xxx.xxx -U aaaa sensor
...
HDD Status | 0x1 | discrete | 0x01ff| na | na | na | na | na | na


Zabbix, however return mean a value of 768. If I have a look to the zabbix logs, I see the following
29684:20180227:155157.089 State [HDD Status | disk | drive_slot | sensor specific | state 8 value is 1]
29684:20180227:155157.089 State [HDD Status | disk | drive_slot | sensor specific | state 9 value is 1]

it seems it only sees the bits 8 and 9 defined, meaning 1100000000 -> 768 in decimal


Is Zabbix really understanding properly Supermicro IPMI ? is the IPMI implementation of supermicro wrong ?

Could anyone monitor the status of Supermicro HDD with the zabbix IPMI agent ?

cheers

Hello, rather then doing it in a long way
Just set IPMI Sensor with additional spaces "HDD Status "
editor is removing extra spaces so it should be more than one
I am ensure you this one works for you.