Ok,

 as I see in your output, all sensors with smHealthMonitorType equal to 1,
everyone have smHealthMonitorReadingUnit equal to mV.
And this mean our sensor definition still correct, not see reason for your changes.

But I found 2 additional sensor classes (current type 7, unit mA) and (power type, unit mW).
I will add it.

smHealthMonitorType.22 = 1
smHealthMonitorType.23 = 1
smHealthMonitorType.24 = 1
smHealthMonitorType.25 = 1
smHealthMonitorType.26 = 1
smHealthMonitorType.27 = 1
smHealthMonitorType.28 = 1
smHealthMonitorType.29 = 1
smHealthMonitorType.30 = 1
smHealthMonitorType.31 = 1
smHealthMonitorType.32 = 1
smHealthMonitorType.33 = 1
..
smHealthMonitorType.42 = 1
smHealthMonitorType.43 = 1
..
smHealthMonitorType.52 = 1
smHealthMonitorType.53 = 1

smHealthMonitorReadingUnit.22 = "mV"
smHealthMonitorReadingUnit.23 = "mV"
smHealthMonitorReadingUnit.24 = "mV"
smHealthMonitorReadingUnit.25 = "mV"
smHealthMonitorReadingUnit.26 = "mV"
smHealthMonitorReadingUnit.27 = "mV"
smHealthMonitorReadingUnit.28 = "mV"
smHealthMonitorReadingUnit.29 = "mV"
smHealthMonitorReadingUnit.30 = "mV"
smHealthMonitorReadingUnit.31 = "mV"
smHealthMonitorReadingUnit.32 = "mV"
smHealthMonitorReadingUnit.33 = "mV"
..
smHealthMonitorReadingUnit.42 = "mV"
smHealthMonitorReadingUnit.43 = "mV"
..
smHealthMonitorReadingUnit.52 = "mV"
smHealthMonitorReadingUnit.53 = "mV"


Torstein Eide wrote on 03.02.2020 13:04:

Hi Mike

See attached file

man. 27. jan. 2020 kl. 19:21 skrev Mike Stupalov <mike@observium.org>:

Hrm,

 please attach discovery debug for more understand, what your device return in this MIB:
./discovery.php -d -m sensors -h <device>

Torstein Eide wrote on 27.01.2020 20:51:

for voltage, the scale is in mV, (0.001), some times it would reset to 1.

like this, for a 12V rail:

It is the fix "+  'scale'               =>  0.001," that is important.

since the "map_class" is more reliable then than the  " 'mV' => 0.001,".

man. 27. jan. 2020 kl. 18:33 skrev Mike Stupalov <mike@observium.org>:

Hi,

 please describe, what you mean as (voltage was unreliable)?

as I see, you just added min (0) and max (250000),
if your server return such values, we can exclude in same (single) definition.
Both this values also impossible for fan speed and temperature.

Torstein Eide via observium wrote on 24.01.2020 14:40:

Hi 

For me the scale read by the supermicro voltage was unreliable, so i have change it to be 2 separately entries.

Index: includes/definitions/mibs/supermicro.inc.php

===================================================================
--- includes/definitions/mibs/supermicro.inc.php (revision 10173)
+++ includes/definitions/mibs/supermicro.inc.php (working copy)
@@ -29,6 +29,8 @@
   'SUPERMICRO-HEALTH-MIB::smHealthMonitorName.1' => '/.+/'
 ];
 
+
+// Tempeture and fanspeed
 $config['mibs'][$mib]['sensor'][] = array(
   'table'               => 'smHealthMonitorTable',
   'oid'                 => 'smHealthMonitorReading',
@@ -35,11 +37,12 @@
   'oid_descr'           => 'smHealthMonitorName',
   'descr_transform'     => [ 'action' => 'ireplace', 'from' => [ 'Temperature', 'Temp', 'Voltage', ' Fan Speed', ' Speed' ], 'to' => '' ],
   'oid_class'           => 'smHealthMonitorType',
-  'map_class'           => [ 0 => 'fanspeed', 1 => 'voltage', 2 => 'temperature' ],
+  'map_class'           => [ 0 => 'fanspeed', 2 => 'temperature' ],
   // This table have unit oid smHealthMonitorDivisor, but it always 0
   'oid_scale'           => 'smHealthMonitorReadingUnit',
   'map_scale'           => [ 'C' => 1, 'mV' => 0.001, 'RPM' => 1 ],
   'oid_num'             => '.1.3.6.1.4.1.10876.2.1.1.1.1.4',
+  'min'                 => 0,
   'limit_scale'         => 'scale', // limits scale same as main scale
   'oid_limit_high'      => 'smHealthMonitorHighLimit',
   'oid_limit_low'       => 'smHealthMonitorLowLimit',
@@ -47,6 +50,31 @@
   'rename_rrd'          => 'supermicro-%index%'
 );
 
+// voltage
+
+$config['mibs'][$mib]['sensor'][] = array(
+  'table'               => 'smHealthMonitorTable',
+  'oid'                 => 'smHealthMonitorReading',
+  'oid_descr'           => 'smHealthMonitorName',
+  'descr_transform'     => [ 'action' => 'ireplace', 'from' => [ 'Temperature', 'Temp', 'Voltage', ' Fan Speed', ' Speed' ], 'to' => '' ],
+  'oid_class'           => 'smHealthMonitorType',
+  'map_class'           => [  1 => 'voltage' ],
+  // This table have unit oid smHealthMonitorDivisor, but it always 0
+  //'oid_scale'           => 'smHealthMonitorReadingUnit',
+  //'map_scale'           => [ 'C' => 1, 'mV' => 0.001,  'RPM' => 1 ],
+  'limit_scale'         => 'scale', // limits scale same as main scale
+  'scale'               =>  0.001,
+  'oid_num'             => '.1.3.6.1.4.1.10876.2.1.1.1.1.4',
+  'min'                 => 0,
+  'max'                 => 250000,
+  'oid_limit_high'      => 'smHealthMonitorHighLimit',
+  'oid_limit_low'       => 'smHealthMonitorLowLimit',
+  'test'                => [ 'field' => 'smHealthMonitorReadingUnit', 'operator' => 'notin', 'value' => [ 'ThermalText', 'N/A' ] ],
+  'rename_rrd'          => 'supermicro-%index%'
+);

This fix the problem i had with scale changing for voltage.

--

Torstein Eide
Torsteine@gmail.com

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

--
Mike Stupalov
Observium Limited, http://observium.org

--

Torstein Eide
Torsteine@gmail.com

--
Mike Stupalov
Observium Limited, http://observium.org

--

Torstein Eide
Torsteine@gmail.com