Tom,

 

Yes, that makes sense.

I didn’t consider the fact that you could have Fan sensors reported with different unit on the same device.

This would indeed messed up the aggregate graph.

 

If there is no other way than looking at the name to identify the sensor I agree this is not reliable at all (I have fans that are just called sensor-12 and sensor-13 on another BMC).

 

In my case I will map “percent” to “capacity” as it is the option that is less likely to cause issues.

 

By the way, any reason why this wasn’t already implemented ?

From my end the code seems to handle everything properly.

 

The only thing I can think of, is that the aggregate graph might not make a lot of sense if you have sensors for different things that are in percent.

 

Best regards,

Louis

 


Louis Bailleul
Computer Systems Engineer
Imaging & Engineering | Imaging
 
Telephone: +44 1932 376000
Direct: +44 1932 376842
VOIP: 74416842
Mobile: +44 7786 525307
Email: louis.bailleul@pgs.com
 
A Clearer Image | www.pgs.com
 

 

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans
Sent: Friday, February 26, 2016 13:25
To: Observium Network Observation System
Subject: Re: [Observium] IPMI fan speed as percent

 

Louis,

Even if we could do different units for the same entity (which we don't, because showing an aggregate graph of fans doing both rpm and % is impossible), there is no way to know if a "percent" sensor on your BMC is actually a fan, apart from trying to see if the word "Fan" is in the name, but I'm not sure I consider that reliable enough.

Tom

On 2016-02-26 14:22, Louis Bailleul wrote:

Hi Tom,

 

Sorry for the late answer.

I had the chance to try with Capacity instead of Fanspeed.

 

But actually I was quick to blame the graphs : they are not that bad once they have settled (see attached).

It just the legend that says “rpm” that is confusing.

They basically provide the same thing as with “Capacity”.

 

But still, I am not quite sure which way should be preferred.

It make sense to assigned fan sensors to the Fan category.

But at the same time if they are only detected by the “percent” unit they might be confused with another type of sensors.

 

Is there another way to identify a type of sensors that could be used to confirm that this is a fan ?

 

Best regards,

Louis

 

 

 

 

Louis Bailleul
Computer Systems Engineer
Imaging & Engineering | Imaging
 
Telephone: +44 1932 376000
Direct: +44 1932 376842
VOIP: 74416842
Mobile: +44 7786 525307
Email: louis.bailleul@pgs.com
 
A Clearer Image | www.pgs.com
 


 

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans
Sent: Thursday, February 18, 2016 16:43
To: Observium Network Observation System
Subject: Re: [Observium] IPMI fan speed as percent

 

Hi Louis,

Try "capacity" instead of "fanspeed" and let me know how that works for you. :-)

They won't show up as fan sensors though. At least not yet.

Tom

On 2016-02-18 14:25, Louis Bailleul wrote:

Hi all,

 

I have some devices for which the fan speed reported over IPMI is in percent.

As the current ipmi_unit is “RPM” they were ignored.

 

Thinking that it could be an easy tweak I just added a definition for percent in includes/definitions/sensors.inc.php

$config['ipmi_unit']['percent']       = 'fanspeed';

 

This makes the detection and polling work but the graphs are messed up as they expect RPMs (kind of make sense eh).

I believe that the fan sensors code is not designed to accommodate different units.

So I come for advice on how to tackle this one.

Is there a sensors that already work with percent ?

 

Below is the output of the ipmi sensors.

Yes it shit, and you need to thanks HP for that (especially things like the temperature limit for CPU or reporting the nominal Wattage of a PSU instead of the power consumption …)

 

UID Light        | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na

Sys. Health LED  | 0x0        | discrete   | 0x0180| na        | na        | na        | na        | na        | na

01-Front Ambient | 24.000     | degrees C  | ok    | na        | na        | na        | na        | 42.000    | 46.000

02-CPU 1         | 59.000     | degrees C  | ok    | na        | na        | na        | na        | -116.000  | na

03-CPU 2         | 53.000     | degrees C  | ok    | na        | na        | na        | na        | -116.000  | na

04-P1 DIMM 1-4   | 64.000     | degrees C  | ok    | na        | na        | na        | na        | 87.000    | na

05-P1 DIMM 5-8   | 69.000     | degrees C  | ok    | na        | na        | na        | na        | 87.000    | na

06-P2 DIMM 1-4   | 58.000     | degrees C  | ok    | na        | na        | na        | na        | 87.000    | na

07-P2 DIMM 5-8   | 57.000     | degrees C  | ok    | na        | na        | na        | na        | 87.000    | na

08-HD Max        | na         |            | na    | na        | na        | na        | na        | 60.000    | na

09-HD Zone       | 24.000     | degrees C  | ok    | na        | na        | na        | na        | 80.000    | na

10-Chipset       | 81.000     | degrees C  | ok    | na        | na        | na        | na        | 105.000   | na

11-VR P1         | 80.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

12-VR P2         | 55.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

13-VR P1 MEM1    | 66.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

14-VR P1 MEM2    | 71.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

15-VR P2 Mem1    | 43.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

16-VR P2 Mem2    | 69.000     | degrees C  | ok    | na        | na        | na        | na        | 115.000   | 120.000

17-LOM           | na         |            | na    | na        | na        | na        | na        | 100.000   | na

18-PCI 1         | na         |            | na    | na        | na        | na        | na        | 100.000   | na

19-PCI 2         | na         |            | na    | na        | na        | na        | na        | 100.000   | na

20-PCI 3         | na         |            | na    | na        | na        | na        | na        | 100.000   | na

21-LOM Card      | na         |            | na    | na        | na        | na        | na        | 100.000   | na

22-PCI 1 Zone    | 59.000     | degrees C  | ok    | na        | na        | na        | na        | 70.000    | 75.000

23-LOM Zone      | 72.000     | degrees C  | ok    | na        | na        | na        | na        | 75.000    | 80.000

24-Battery Zone  | 65.000     | degrees C  | ok    | na        | na        | na        | na        | 75.000    | 80.000

25-PSU Intake    | 40.000     | degrees C  | ok    | na        | na        | na        | na        | 80.000    | 85.000

26-Sys Exhaust   | 64.000     | degrees C  | ok    | na        | na        | na        | na        | 80.000    | 85.000

Fan 1            | 67.816     | percent    | ok    | na        | na        | na        | na        | na        | na

Fan 2            | 67.816     | percent    | ok    | na        | na        | na        | na        | na        | na

Power Supply 1   | 1275       | Watts      | ok    | na        | na        | na        | na        | na        | na

Power Supply 2   | 1275       | Watts      | ok    | na        | na        | na        | na        | na        | na

Memory           | 0x0        | discrete   | 0x4080| na        | na        | na        | na        | na        | na

 

Best regards,

Louis

 

Louis Bailleul
Computer Systems Engineer
Imaging & Engineering | Imaging
 
Telephone: +44 1932 376000
Direct: +44 1932 376842
VOIP: 74416842
Mobile: +44 7786 525307
Email: louis.bailleul@pgs.com
 
A Clearer Image | www.pgs.com
 


 


 
Address: 4 The Heights, Brooklands, Weybridge, Surrey, KT13 0NY, United Kingdom
 
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.





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

 




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