Idrac critical alert for virtual disk

Help
1

Hi,

Since the start of the week, we’ve been getting the following alert for all of our server idracsevery time discovery is running.

Rule: State Sensor Critical

Faults:

#1: sysObjectID => .1.3.6.1.4.1.674.10892.5; location_id => 33; sensor_id => 507; sensor_oid => .1.3.6.1.4.1.674.10892.5.5.1.20.140.1.1.4.1; sensor_descr => Virtual Disk 0; state_descr => failed;

According to the VD state graph and the event log, the state for that sensor hasn’t changed to justify getting this alert. Additionnally, I’ve disable alerting for the virtual disk sensor on all idracs and we are still receiving alerts.

====================================

Component Version
LibreNMS 1.49-23-ge3e3de1
DB Schema 2019_02_10_220000_add_dates_to_fdb (132)
PHP 7.2.15-1+ubuntu16.04.1+deb.sury.org+1
MySQL 10.0.38-MariaDB-0ubuntu0.16.04.1
RRDTool 1.5.5
SNMP NET-SNMP 5.7.3

====================================

[OK] Composer Version: 1.8.4
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database schema correct

2

Probably the discovery is setting the value incorrectly. Can you pastebin discovery.php -d -h HOSTNAME?

3

Here you go: https://pastebin.com/hsFH6Uab

4

Strangely, the last discover job only triggered the alert on one of the idracs which happens to not be the one from the previous paste, so here’s one for that device too: https://pastebin.com/7vkSh194

5

Hi All,

we’re encountering the same problem, here our Libre version:

====================================

Component Version
LibreNMS 1.50-45-gf63d7a8
DB Schema 2019_02_10_220000_add_dates_to_fdb (132)
PHP 7.2.12
MySQL 5.5.60-MariaDB
RRDTool 1.4.8
SNMP NET-SNMP 5.7.2

====================================

Currently we’re bound to disable those alerts, is there any fix in progress?

Here a pastebin of our discovery.php -d -h HOSTNAME : https://pastebin.com/yQAuXXXk